# Sdd Implement

> SDD step 4. Read plan.md and implement the feature step by step, then verify all acceptance criteria are met. Use after /sdd-plan has produced plan.md.

- Skill: `sivaprasadreddy/sdd-implement` (Agent Skill)
- Install (CLI): `npx skillmds@latest add sivaprasadreddy/sdd-implement`
- Raw SKILL.md: https://api.skillmd.com/api/skills/sivaprasadreddy/sdd-implement/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: sivaprasadreddy (https://skillmd.com/u/sivaprasadreddy)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/sivaprasadreddy/sdd-implement

---


# SDD: Implementation

You are a senior software engineer executing the implementation plan precisely.

## Pre-conditions
Verify these files exist:
- `plan.md` — the implementation plan
- `feature.md` — the feature spec (for acceptance criteria)
- `docs/project.md` — project context

## Process

### 1. Read Everything
Read `plan.md`, `feature.md`, and `docs/project.md` before writing a single line of code.

### 2. Execute Steps in Order
Work through each step in `plan.md` sequentially. For each step:
- Announce which step you're starting
- Create or modify the specified files
- Follow the architectural patterns from `docs/project.md` strictly
- Do not skip steps or reorder without explaining why
- **As soon as a step is complete and verified, mark it done in `plan.md`** by changing `- [ ]` to `- [x]` on that step's line (or prepending `✅` if the plan does not use checkboxes)

### 3. Code Quality Rules
- Follow the conventions already present in the codebase (read existing similar files first)
- Write clean, idiomatic code for the tech stack
- Add documentation to public APIs
- Do not introduce new dependencies without flagging it to the user

### 4. Run Verification After Each Layer
After completing each step, run the relevant build/test command from `docs/project.md`:
- After schema changes: check migration applies cleanly
- After each new source file: compile (use the project's compile command)
- After tests are written: run them (use the project's test command)
- Fix any failures before proceeding to the next step

### 5. Final Acceptance Criteria Check
Once all steps are complete, go through every acceptance criterion in `feature.md`:
- For each AC, identify and run the test that covers it
- Report pass/fail for each AC
- Do NOT update acceptance criterion status in `feature.md`

### 6. Summary Report
Write a file named `impl-summary.md` in the project root with the following content:

```markdown
## Implementation Complete

### Files Created
- ...

### Files Modified
- ...

### Acceptance Criteria
- [x] AC-01: Passed — `FooServiceTest#test_something`
- [x] AC-02: Passed — `FooControllerTest#test_endpoint`

### Notes
Any deviations from the plan and why.
```

Keep each entry a single concise bullet — this file is a quick reference, not prose.

After writing the file, tell the user: "`impl-summary.md` created." Then prompt them to run `/sdd-review` before archiving.