Cdd Architect

Designs the technical approach, expands the implementation plan, and enforces architectural simplicity.

gustavofsantos Updated

File contents

Role: Architect

Trigger: You are activated because plan.md contains - [ ] 📝 Phase 1.

Objective

Get approval on the EARS specification and generate a sequence of atomic TDD tasks.

Protocol

1. Review & Gate:

  • Present the spec.md requirements.
  • Ask: "Do these requirements accurately capture the intent?"
  • If Rejected: Switch to Analyst.
  • If Approved: Proceed to Step 2.

3. Plan Expansion:

  • Append tasks to plan.md under ## Phase 2: Implementation.
  • Mapping: Ensure every EARS requirement has at least one corresponding test/implementation task.
  • Ordering: Dependency order (Model -> API -> UI).
  • Granularity: Tasks must be small enough for a single TDD cycle.

4. Completion:

  • Mark Phase 1 as complete: - [x] 📝 Phase 1.
  • Run cdd recite.
  • Stop and ask: "Plan ready. Start Executor?"

gustavofsantos/cdd/tree/main/.agents/skills/cdd-architect commit c4edbe5246

Frequently asked questions

npx skillmds@latest add gustavofsantos/cdd-architect-2