Skip to content

Adds Phase 5: Implementation to the Skill; Adds TDD section. Connects… #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
infews wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Adds Phase 5: Implementation to the Skill; Adds TDD section. Connects… #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 11 additions & 3 deletions skills/design-driven-dev/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
name: design-driven-dev
description: Guide for design-driven development. Consult for ALL code changes. New features use full workflow (HLD → LLD → EARS → Plan). Bug fixes skip doc creation but still verify intent coherence—check that existing specs, tests, and code align before changing anything.
name: linked-intent-driven-dev
description: Guide for linked-intent-driven development. Consult for ALL code changes. New features use full workflow (HLD → LLD → EARS → Plan). Bug fixes skip doc creation but still verify intent coherence—check that existing specs, tests, and code align before changing anything.
---

# Design-Driven Development
Expand Down Expand Up @@ -145,7 +145,15 @@ Before implementing (or resuming implementation), verify coherence:
- Do the tests trace to current EARS?
- If drift is detected, fix the docs first—then implement.

## Code Annotation Pattern
## Phase 5: Implementation

Proceed through each implementation phase, one EARS spec at a time.

### Test-Driven Development

For each EARS spec, use a test-driven development approach. Write the tests and then stop and get user approval before proceeding. Then write the implementation so that the tests pass. Stop and get user approval before proceeding to the next EARS spec.

### Code Annotation Pattern

Annotate code with `@spec` comments linking to EARS IDs:

Expand Down