Mission Spec

Own requirement discussion and the draft -> approved spec transition. Do not implement the work and do not write a separate implementation plan.

Declare: 使用 mission-spec skill，讨论并生成可批准的 canonical spec。

Workflow

Read the request and the relevant repository context.
If lite-arch-recall is installed, run it before an architecture-bearing decision against applicable docs/adr/ records. Otherwise record that architecture recall was unavailable and continue.
Ask one question at a time only while a material goal, constraint, scope boundary, or acceptance condition remains unresolved.
Present alternatives only when real alternatives exist. Recommend one and state concrete tradeoffs.
Once the design is determined, write a draft to docs/specs/<YYYY-MM-DD>-<topic>.md.
Run python scripts/validate_spec.py <spec> --allow-uncommitted-approved and fix every error.
Show the final draft and require explicit user approval of that exact content. Do not implement before approval.
After approval, set status: approved and add the current RFC 3339 approved_at timestamp with timezone. Do not change the approved body in the same edit.
If lite-arch is installed, run its record decision gate and print the required three-line block before creating, amending, superseding, or skipping an ADR. Without lite-arch, state that the optional ADR gate was skipped.
Commit the approved spec and any draft ADR created by the optional gate before execution. Then run validate_spec.py without the allow flag to prove the approved file is committed and unchanged from HEAD.
Route the committed spec to mission-approved-doc, unless the user explicitly chooses ordinary direct implementation.