spec
The spec command initiates specification-driven development by gathering requirements through targeted clarification questions about project objectives, features, technical constraints, and boundaries. It then generates a comprehensive SPEC.md document covering objective, commands, project structure, code style, testing strategy, and operational boundaries. Use this when starting new projects to establish clear requirements and development guidelines before implementation begins.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/addyosmani/agent-skills/HEAD/.claude/commands/spec.md -o ~/.claude/commands/spec.mdspec.md
Invoke the agent-skills:spec-driven-development skill. Begin by understanding what the user wants to build. Ask clarifying questions about: 1. The objective and target users 2. Core features and acceptance criteria 3. Tech stack preferences and constraints 4. Known boundaries (what to always do, ask first about, and never do) Then generate a structured spec covering all six core areas: objective, commands, project structure, code style, testing strategy, and boundaries. Save the spec as SPEC.md in the project root and confirm with the user before proceeding.
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
Simplify code for clarity and maintainability — reduce complexity without changing behavior
Break work into small verifiable tasks with acceptance criteria and dependency ordering
Conduct a five-axis code review — correctness, readability, architecture, security, performance
Run the pre-launch checklist via parallel fan-out to specialist personas, then synthesize a go/no-go decision
Run TDD workflow — write failing tests, implement, verify. For bugs, use the Prove-It pattern.
Senior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.
Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.