Define Goals
Before scope or design, name the outcome, and how you will know you reached it.
When to use
- Starting a new project, product, or substantial initiative with a fuzzy "why".
- Skip for a single feature or task. Use
clarifying-intentonly for genuine ambiguity about which initiative or procedure is intended;writing-specsowns settled, detailed feature requirements. - Skip when a drafted goal or brief is awaiting a direct answer. If the
reply informs but does not answer, handle it with
clarifying-intent, not with a new goal pass.
Step 1: Find the objective
Open assets/goals-section.md before starting. Fill a section only with
what this work has; the template says what an empty one carries.
- Ask "why this, why now?" until the answer is what the world does differently afterward, not code that exists.
- If goals compete, give each its own metric, never one averaged metric.
- Record one accountable decision owner, or else the approvers, the conflict
resolver, and the decision rule. If the user is the only stakeholder (a
solo owner), write the user as the decision owner in
Decision rule:and name no approvers or conflict resolver. - If an outcome has no source or date, it cannot be checked, so it is not a
goal. Write a baseline never measured as
unmeasured, with who takes the first reading and by when; never a recalled number.
Step 2: Write and present
Write the
## Goalssection, which is never edited once its identity is issued, to.sdlc-skills/briefs/{{YYYY-MM-DD}}-{{topic}}.mdor the user-set path, leaving the approved sections around it untouched. When the work came from a captured ticket, fillSourcewith the capture's path and identity.Present:
Goals {{path}} — version {{identity (per template)}} Objective: {{one line}} Measure: {{baseline}} → {{target}} by {{horizon}}, source {{source}} Guardrails: {{list}} 1. Approve the goals 2. Request changes 3. Reject the objective 4. Cancel Recommendation: {{option the measure and guardrails support}} — {{one sentence}}.Ask this and end the turn;
clarifying-intentowns what closes it.REQUIRED SUB-SKILL: on option 1, invoke
feasibility-checkunless an existing feasibility section already fills every dimension row from evidence and no killer risk's confidence is unknown; then, if the boundary is next, invokescoping. Never impose a phase that is already complete.
Gotchas
- A guardrail can look complete just because it is written down while no
observation could ever show it broken.
scopingtreats every goal guardrail as a non-negotiable constraint on each cut, so a guardrail with no observable threshold lets a cut violate it with nothing in place to catch that. - Naming several approvers for the objective without also naming a conflict resolver and a decision rule leaves no way to settle it when they disagree about what the goal actually is; the brief then stalls on a tie nobody is placed to break.