원클릭으로 Manus에서 모든 스킬 실행

$pwd:

sdd-implement

Name: Sdd Implement
Author: sivaprasadreddy

// 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.

Manus에서 실행

$ git log --oneline --stat

stars:27

forks:7

updated:2026년 4월 27일 13:29

SKILL.md

readonly

name	sdd-implement
description	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.

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:

## 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.

related-skills.json

같은 저장소

sdd-feature.md

from "sivaprasadreddy/sdd-skills"

SDD step 1. Analyse a feature request and produce a detailed feature.md spec. Use when the user describes a new feature they want to build. Asks for missing details before writing the spec.

2026-04-2727

sdd-init.md

from "sivaprasadreddy/sdd-skills"

SDD step 0. Analyse the project codebase and create docs/project.md with tech stack, architecture, and conventions. Run once before starting SDD in a new project. If docs/project.md already exists, asks whether to regenerate it.

2026-04-2727

sdd-plan.md

from "sivaprasadreddy/sdd-skills"

SDD step 3. Read feature.md and produce a detailed implementation plan.md tailored to the project's tech stack and architecture. Use after /sdd-feature has produced feature.md.

2026-04-2727

sdd-refine.md

from "sivaprasadreddy/sdd-skills"

SDD step 2 (optional, repeatable). Read an existing feature.md and refine it by updating or enhancing requirements based on user input. Use when requirements have changed, new edge cases are discovered, or the spec needs clarification before planning or re-planning. Run before /sdd-plan if plan.md already exists.

2026-04-2727

sdd-yolo.md

from "sivaprasadreddy/sdd-skills"

SDD fast path. Runs the full pipeline — analyse → plan → implement → review → archive — with a single confirmation gate before implementation begins. Stops automatically if Critical or Major issues are found in review. Use when you want to ship a well-understood feature with minimal interruptions.

2026-04-2727

sdd-archive.md

from "sivaprasadreddy/sdd-skills"

SDD step 7. Archive feature.md and plan.md into docs/specs-archive/<yyyymmddHHMM>-<feature-name>/ directory, then update docs/project.md with the new feature, and any architecture decisions made. Use after /sdd-review is complete and the feature is ready to merge.

2026-04-2727

package.json

"author": "sivaprasadreddy"

"repository": "sivaprasadreddy/sdd-skills"

GitHub 저장소 열기 Creator 저장소 보기

$ install --global

$ download --local

Manus에서 실행

$ useful --forSOC

소프트웨어 개발자컴퓨터 및 수학직15-1252L4

name	sdd-implement
description	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.

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:

## 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.

sdd-implement

SDD: Implementation

Pre-conditions

Process

1. Read Everything

2. Execute Steps in Order

3. Code Quality Rules

4. Run Verification After Each Layer

5. Final Acceptance Criteria Check

6. Summary Report

이 저장소의 다른 Skills

이 저장소의 다른 Skills

SDD: Implementation

Pre-conditions

Process

1. Read Everything

2. Execute Steps in Order

3. Code Quality Rules

4. Run Verification After Each Layer

5. Final Acceptance Criteria Check

6. Summary Report