north-star
Make sure the project has a written goal in docs/north-star.md, then state how the current unit moves toward it. Use after a brainstorm and before a plan, or when substantial work is requested in a repo with no docs/north-star.md. North-star step of the methodical loop. Not to rewrite an existing one unasked.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- north-star
- description
- Make sure the project has a written goal in docs/north-star.md, then state how the current unit moves toward it. Use after a brainstorm and before a plan, or when substantial work is requested in a repo with no docs/north-star.md. North-star step of the methodical loop. Not to rewrite an existing one unasked.
03 SKILL.md 正文
North Star
Say Step: north-star before anything else.
Use the North Star at the start of every unit, not only at review. Why: units judged only against their own goal can each pass while the project drifts; stating the goal up front steers each plan before work is spent on it.
Mode 1 — the project has no docs/north-star.md
Write it with the user, before any plan.
- Start from
${METHODICAL_ROOT}/templates/north-star.md. - Draft only what the repo and the conversation already show, mark every guess as a guess, and ask the user to rule on who it serves, what they receive and the bar. Batch the questions into one AskUserQuestion call (at most 4; the rest in a second call), with a recommended answer first for each. Why: a goal the user did not choose will be overruled later, after work has been built on it.
- Write
docs/north-star.mdonce the user has ruled, link it from the repo'sCLAUDE.md(create a one-line one if there is none), and commit. Why: a North Star nobody's session can find does not steer anything.
This is a stop for the user's ruling, by design. If they decline to write one now: record that in the plan's "Left short, on purpose" and continue.
Mode 2 — docs/north-star.md exists
Write the unit's statement in the shape of the plan template's North Star section. Do not interrupt: ask with AskUserQuestion only if the statement would change what the North Star means. Why: that is their goal to change, not the unit's.
When a design choice comes up anywhere in the loop, prefer the option that moves toward the North Star, and say so. A unit that meets its own goal but not the North Star is not done; say that plainly rather than reporting success.
When it hands on
Say Step: plan and continue with the plan skill in the same turn, carrying the statement into
the plan.
04 同仓库更多 Skills
phrase-outside
暂无简介
named-only
暂无简介
work
Build an approved plan from docs/plans/ on its own short-lived branch, or a change the user said to make without a plan. Use when a plan reads state: approved and the user wants it built, when resuming such a build, or when the user has waived the plan for a named change. Work step of the methodical loop. Not when no approved plan exists and the user has not waived one (run the plan step), and not for reviewing finished work.
work-review
Review a finished build on its branch against its plan, with reviewer seats matched to the code's language, before it merges. Use when the work step's tests pass and the plan's approach is done, or when the user asks for a review of a branch's changes. Work-review step of the methodical loop. Not for reviewing a plan.
plan
Write the plan file in docs/plans/ that code changes get before building, unless the user has said to build without one. Use when the user asks to build, fix, edit or change code and docs/plans/ has no approved plan for it, or when a plan must be revised after review. Plan step of the methodical loop. Not for questions or reading code, and not when the user has waived the plan for this change (go to work).
plan-review
Review a plan in docs/plans/ with reviewer seats matched to the project's language, before the user approves it. Use when a plan has just been written or deepened, when a plan was revised after review, or when the user asks for a plan review. Plan-review step of the methodical loop. Not for reviewing built code.