Developer: Code Implementation

Router command for implementing planned work.

Routing

Input	Strategy
story <path>	Story Implementation
<path> (auto-detect)	Detect entity type
(future)	bug, chore strategies

Currently supports: story

---

Strategy: Story Implementation

Trigger: dev:code story <path> or auto-detected story path

Prerequisites

• Story must have status planned
• Plan exists at {story_path}/plan.md
• All dependency stories must be at least coded

Process

Phase 1: Validation

1. Load plan from {story_path}/plan.md
2. Verify dependencies complete
3. Check for conflicts (files changed since plan)
4. If conflicts, recommend re-planning

Phase 2: Implementation

Execute plan systematically:

1. Follow the plan exactly:

   • Implement each step as specified
   • Don't add unplanned functionality
   • Don't skip steps

2. For each phase:

   • Announce phase start
   • Execute steps in order
   • Validate before proceeding

3. Code quality:

   • Follow project conventions
   • Write clean, readable code
   • Appropriate error handling

4. Tests alongside code:

   • Write unit tests for new functions
   • Update tests if behavior changes
   • Follow project testing patterns

Phase 3: Validation

Run validations:

# Detect and run tests
npm test / pytest / go test

# Run linter
npm run lint / flake8 / golint

# Run build
npm run build / go build

Check acceptance criteria verifiable at this stage.

Phase 4: Status Update

Update user-story.md status → coded

Create {story_path}/implementation-notes.md:

# Implementation Notes: {Story Title}

## Summary
{Brief description of what was implemented}

## Files Changed

| File | Action | Description |
|------|--------|-------------|
| src/auth.ts | Created | Auth service |
| src/Login.tsx | Created | Login component |

## Tests Added

| Test File | Coverage |
|-----------|----------|
| auth.test.ts | Login, logout, session |

## Deviations from Plan
{Any necessary changes, with reasoning}

## Known Issues
{Issues discovered during implementation}

## Validation Status
- [x] Tests passing
- [x] Linter passing
- [x] Build successful
- [ ] Manual verification needed for AC-3

## Notes
{Additional context}

Update feature.json progress.

Phase 5: Next Steps

Recommend dev:test story {story_path}

Output

✅ Implementation Complete

Story: {title}
Path: {story_path}

Work Summary:
- Files created: 3
- Files modified: 2
- Tests added: 5

Validation:
  ✅ Tests passing (12/12)
  ✅ Linter: no issues
  ✅ Build: successful

Feature Progress: ████████░░░░ 60% (3/5 coded)

→ Next (DEV): dev:test story {story_path}

With Issues

⚠️ Implementation Complete with Issues

Story: {title}

Validation:
  ⚠️ Tests: 10/12 passing
  ✅ Linter: no issues

Failing Tests:
  - auth.test.ts:45 - Token validation
  - auth.test.ts:67 - Session timeout

Action Required:
  Fix failing tests before proceeding.

---

Operational Guidelines

1. Follow the plan literally
2. Atomic changes: Each logical change committable
3. Validate before completion
4. Document issues: Record in implementation-notes.md
5. Stay in scope: Note unplanned work, don't implement it

---

Future Strategies

Bug Fix (future)

• Reproduce bug first
• Minimal fix scope
• Add regression test
• Verify fix works

Chore (future)

• No behavioral changes
• Run full test suite
• Performance benchmarks
• Refactoring safety