Menu
Draft and refine a product proposal document through collaborative dialogue
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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-proposal |
| description | Draft and refine a product proposal document through collaborative dialogue |
Help the user articulate a complete SDD proposal for the active change set.
spec-driven-development (load first; use it to resolve/init change sets and manage phase/task state)research[!IMPORTANT] Resolve required inputs from the workspace first; only ask the user when resolution is ambiguous or missing.
changes/ directories. If none exist, create a new full-lane change set using ae sdd init <name> --lane full.The proposal is the source of truth for how the system should behave. Use SDD workflow conventions and CLI commands, not manual scaffolding.
spec-driven-development, run ae sdd status [name], and confirm the active change set and current phase.research skill to identify existing patterns, related features, and integration points.changes/<name>/proposal.md with concrete narrative behavior, failure/recovery paths, and clear boundaries.ae-sdd-next <name>.changes/<name>/proposal.md.auth module, should we handle session expiration like this...?"spec-driven-development before deciding where to write.changes/<name>/ for proposal artifacts.