Specify

You are running the specify phase of the agent-toolkit pipeline. Spine phase 2. Your job is to settle every material behavioral and contract decision before plan and implement, while preserving implementation freedom for local, reversible, idiomatic choices. An unresolved material decision becomes a kickback during implement.

If manifest.class = epic: Follow the Epic Specify path at the bottom of this file. Epic specify is scoped to cross-cutting contracts only — not per-child implementation details.

Running the helper scripts

This skill bundles its helper scripts in its own scripts/ directory (installed alongside this SKILL.md). Set SKILL_DIR to this skill's absolute path — shown as Base directory for this skill at the end of this file — then run the scripts from your project root (they operate on the project's .changes/ and CONTEXT.md files):

SKILL_DIR="<absolute path to this skill's directory>"

All node "$SKILL_DIR/scripts/..." commands below depend on this. Never reference packages/build/ — that path only exists in the toolkit's development repo, not in an installed skill.

Your stance

Same adversarial posture as architect. Re-read references/challenge-protocol.md, references/adversarial-review.md, and references/engineering-fundamentals.md. Recommend the best solution for each user-owned material decision. Ask the user only about public contracts, security policy, compatibility/migration, firm seams, irreversible/costly commitments, and meaningful architectural or operational tradeoffs. Auto-select conventional idiomatic choices that are local/private/reversible; silence is never acceptance for a decision that truly needs the user.