Menü
Write change-set specifications for change
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Fast-track bug investigation and fix initialization
Create high-quality git commits with clear Conventional Commit messages
Continue an SDD change set in a fresh chat using CLI status only
Critique proposal, specs, or plan for gaps and contradictions
Discover high-level architectural requirements for change-set specs
Explain SDD concepts, workflow, and CLI-first usage
| name | ae-sdd-specs |
| description | Write change-set specifications for change |
Write change-set specifications for the change set.
spec-driven-development (state management, phase gates)spec-formatresearch[!IMPORTANT] Resolve the change set by running
ls changes/ | grep -v archive/. If exactly one directory exists, use it. Only prompt the user when multiple change sets are present.
Load spec-driven-development, spec-format, and research skills. Read state from changes/<name>/state.toml and proposal.md. Apply state entry check per skill guidelines.
Lane check: If lane is not full, redirect to appropriate command per skill guidelines.
Spec writing is collaborative. Don't start writing immediately. First, summarize the goal, actors, workflows, and constraints in your own words. Explain how the change maps to the existing capability hierarchy. Present concrete statements and decisions. Offer options for open decisions. Pause and wait for user confirmation.
After confirmation, run ae sdd spec list (no flag by default) to discover canonical spec paths, then use research skill to understand related capabilities, naming conventions, and build context for spec writing. If the canonical specs directory does not exist yet, treat this as greenfield and proceed.
With approval, create specs in changes/<name>/specs/ using spec-format skill:
Suggest ae-sdd-critique specs when complete for review.
Do not update phase status in this command. When the user wants to proceed, suggest ae-sdd-next <name>.
Writing specs with collaborative discovery:
Input: None (change: "password-reset")
Output: "Your goal is to allow users to reset passwords via email.
Actors: user, admin. Workflow: request email → click link → set new password. Correct?"
User confirms.
Output: "This maps to auth/password spec boundary.
Writing delta spec at changes/password-reset/specs/auth/password.md..."
Lane check redirects:
Input: "vibe-lane" (not full lane)
Output: "Vibe lane should skip specs—redirecting to ae-sdd-plan."