/spec-tasks#

Generate implementation-ready tasks from your approved design.

Usage#

Claude Code:

/spec-tasks user-authentication
/spec-tasks user-authentication -y

Antigravity:

/spec-tasks user-authentication
/spec-tasks user-authentication -y
# or
@spec-tasks user-authentication

Description#

/spec-tasks reads:

• .specs/[feature-name]/spec.json
• .specs/[feature-name]/requirements.md
• .specs/[feature-name]/design.md

Then it writes:

• .specs/[feature-name]/tasks.md

Tasks are ordered, requirement-mapped, and ready for /code execution.

Task Format#

Typical format in tasks.md:

- [ ] 1. Set up authentication module
- [ ] 1.1 Create auth service interface
  - Define login/logout/session methods
  - _Requirements: 1, 2_

- [ ] 2. Add login endpoint
- [ ] 2.1 Implement POST /api/auth/login
  - Validate input and return token/session
  - _Requirements: 1, 3_

Notes#

• Tasks should be small, clear, and sequential
• Every requirement should be covered by at least one task
• -y can auto-approve prerequisites before generation

Next Steps#

• /code - Implement the next pending task
• /test - Validate implementation
• /review - Review quality and regressions