spec
Use when turning a rough idea or feature request into a written specification with requirements, acceptance criteria and open questions. Do NOT use for breaking an agreed spec into tasks (use `plan`).
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-09
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- spec
- description
- Use when turning a rough idea or feature request into a written specification with requirements, acceptance criteria and open questions. Do NOT use for breaking an agreed spec into tasks (use `plan`).
03 SKILL.md 正文
Spec
Fixture skill for anneal eval routing tests.
04 同仓库更多 Skills
write-skill
Use to write or change a skill test-first, even if the change looks like a wording fix; watch a case fail with no guidance, then pass Tiers 0 to 3 before merge. Do NOT use for turning a correction into a check (use `correct`) or building code (use `build`).
verify
Use when asked "is it fixed?", "tested?" or "can we close it?", or to check a claim, and before calling work done or fixed, even if told to skip tests; prove it fresh, failing before the fix and passing after, and doubt it. Do NOT use for an unknown failure (use `diagnose`) or the PR (use `ship`).
spec
Use when requirements are agreed, even if the spec seems obvious; write the spec or its acceptance criteria (EARS, SHALL), Out of Scope and the constitution check of its gates. Do NOT use for a new or vague request (use `grill`) or splitting a spec into tasks (use `plan`).
ship
Use when a change needs a pull request, review verdict or depth, merge, schema migration, rollout, canary or rollback, even if it looks safe; decide GO or NO-GO only with a rollback ready. Do NOT use for proving work done or passing (use `verify`) or a failure with an unknown cause (use `diagnose`).
plan
Use when a spec is ready, even if the work seems obvious; split it into tasks, each with its files, one test command and which tasks block it, then get the plan approved. Do NOT use for writing the spec (use `spec`), a new or vague request (use `grill`) or building an approved task (use `build`).
orchestrate
Use to run an approved plan's ready tickets across subagents, even when fanning out looks obvious; park one-way calls in weigh-in and rule on the rest. Do NOT use for one task (use `build`) or splitting work into tickets (use `plan`).