mcpField
S
sdd-plan

sdd-plan

github.com/sivaprasadreddyDevelopment3459 installsUpdated 28w ago
Repository

About sdd-plan

sdd-plan is a skill for turning a feature specification and project context into an actionable implementation plan. It identifies the project’s technology stack and asks for approval before implementation proceeds.

Key features

  1. 01Checks feature and project documentation
  2. 02Identifies the project technology stack
  3. 03Creates a structured implementation plan
  4. 04Records design choices and rationale
  5. 05Requests approval before implementation

Use cases

  1. 01Planning work from a feature specification
  2. 02Aligning implementation steps with project architecture
  3. 03Reviewing an implementation approach before coding

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sivaprasadreddy/sdd-skills --skill sdd-plan

After installing, type/sdd-planin Claude Code to confirm it loaded.

Details

From the project README

SDD: Implementation Planning

You are acting as a senior software engineer creating a precise, actionable implementation plan.

Pre-conditions

Verify both files exist before proceeding:

  • feature.md — the feature spec (if missing, tell the user to run /sdd-feature first)
  • docs/project.md — project context

Process

1. Read Both Files

Read feature.md and docs/project.md in full.

2. Identify the Tech Stack

From docs/project.md, note:

  • Primary language and framework
  • Build tool and compile/test commands
  • Database and data access layer
  • Messaging systems
  • Testing frameworks
  • Any architecture patterns (e.g., Hexagonal, DDD, Layered)
3. Produce plan.md

Create plan.md in the project root with this structure:

# Implementation Plan: <Feature Name>

## Overview
Brief description of the implementation approach.

## Architecture Decisions
- Key design choices and their rationale
- Patterns to follow (aligned with docs/project.md)

## Implementation Steps

### Step 1: <Database/Schema Changes>
- [ ] Create/alter table: `...`
- [ ] Add migration file: `...`
- Files to create/modify: ...

### Step 2: <Domain Layer>
- [ ] Create entity / model: `...`
- [ ] Create value objects: `...`
- [ ] Define repository / data access interface: `...`
- Files: ...

### Step 3: <Application/Service Layer>
- [ ] Create use case / service: `...`
- [ ] Define request/response objects / command objects: `...`
- Files: ...

### Step 4: <Infrastructure/Adapter Layer>
- [ ] Implement repository / data access: `...`
- [ ] External integrations: `...`
- Files: ...

### Step 5: <API / Presentation Layer>
- [ ] Controller / handler / route: `...`
- [ ] Request/response models: `...`
- [ ] API documentation annotations: `...`
- Files: ...

### Step 6: <Tests>
- [ ] Unit tests: `...`
- [ ] Integration tests: `...`
- [ ] API / end-to-end tests: `...`
- Files: ...

## Acceptance Criteria Mapping
| AC | Verified By |
|----|-------------|
| AC-01: ... | `<TestClass#testMethod>` |
| AC-02: ... | `<TestClass#testMethod>` |

## Risks & Mitigations
- Risk: ... → Mitigation: ...

## Estimated Complexity
Low / Medium / High — brief justification

After writing the file, present a summary of the plan and ask the user to approve before proceeding to /sdd-implement.

Comments

Markdown supported