Feature Spec

Feature Spec

Capture agreed behavior once so every Task consumes the same contract.

Establish the Feature boundary

1. Resolve one exact Feature before editing:
   • prefer an ID, link, path, or name from the request;
   • otherwise resolve the actor from the request, .waypoint/local.yaml, or external tracker, then filter active Features by owner;
   • continue only when exactly one candidate remains; otherwise ask. Never fall back to another owner's Feature, list order, recency, Git history, or the current branch. An explicit target does not transfer ownership.
2. Read repository instructions, that Feature record, relevant product context, existing behavior, and local specification conventions.
3. Identify the stable Feature ID, owner, intended outcome, scope, non-goals, and observable completion proof. Reuse the owner from the Feature record or configured external tracker, then an explicit current request. If still missing, read .waypoint/local.yaml directly when it exists and use its actor_id as the current actor; if that does not establish the Feature owner, ask the user. Never guess from Git author metadata, harness, machine, branch, or window identity.
4. Synthesize decisions already established by the user and repository. Do not interview again, widen scope, add technical choices, or silently settle future intent while writing.
5. Stop and return the unresolved decision when behavior is still ambiguous enough to change Acceptance or Task boundaries.

A Feature split across executors must have one durable behavioral contract before Task planning. A small unsplit Feature may keep a compact contract in feature.md when its outcome, scope, rules, and Acceptance are already reviewable; do not create a separate file solely to satisfy a layout.

Write behavior, not implementation

Include only the smallest useful set of:

• problem, motivation, outcome, and actors;
• included behavior and meaningful non-goals;
• observable inputs, outputs, rules, and state transitions;
• failure, compatibility, security, or operational behavior visible at the contract boundary;
• representative scenarios when they clarify a material edge;
• externally imposed constraints;
• authoritative Feature Acceptance when no stronger Feature record owns it.

Do not include architecture, module seams, schemas, algorithms, file paths, Task decomposition, execution order, test-writing steps, rollout mechanics, or commit instructions. Link an existing design rather than summarizing it.

Update an existing repository-native specification when one fits. Otherwise use references/spec-template.md. Keep canonical Acceptance in feature.md when that Feature record exists; the spec explains the behavior that makes those checks meaningful without copying the checklist.

Finish after the agreed behavior is durable. Approval authorizes this specification only; do not continue into design, Task planning, implementation planning, or code unless the current request explicitly names that separate planning outcome. Planning never authorizes implementation.

Companion skills

Use grilling for unresolved product intent and research for material external facts when installed. These companions come from mattpocock/skills and remain optional.

Install only the needed companion with npx skills add mattpocock/skills --skill <name>.