Agent Skills › madebyaris/chaca-scanner › sdd-implementation

sdd-implementation

GitHub

根据SDD计划、规范和待办列表系统性地执行代码生成和特性构建，遵循特定协议确保依赖顺序、进度追踪及问题记录。

.cursor/skills/sdd-implementation/SKILL.md madebyaris/chaca-scanner

Trigger Scenarios

执行预定义的SDD实现计划根据规格说明生成代码按计划构建新功能

Install

npx skills add madebyaris/chaca-scanner --skill sdd-implementation -g -y

More Options

Use without installing

npx skills use madebyaris/chaca-scanner@sdd-implementation

指定 Agent (Claude Code)

npx skills add madebyaris/chaca-scanner --skill sdd-implementation -a claude-code -g -y

安装 repo 全部 skill

npx skills add madebyaris/chaca-scanner --all -g -y

预览 repo 内 skill

npx skills add madebyaris/chaca-scanner --list

SKILL.md

Frontmatter

{
    "name": "sdd-implementation",
    "description": "Execute planned implementations following todo-lists systematically. Use for code generation, building features, and executing SDD plans."
}

SDD Implementation Skill

Build what has been planned, following specs and todo-lists precisely.

When to Use

Executing planned implementations
Code generation from specifications
Building features according to plan

Protocol

Step 1: Load the Plan

Read: plan.md → spec.md → tasks.md → todo-list.md

Step 2: Execute Systematically

Read entire list before starting
Execute in order — respect dependency chains
Mark completion — - [ ] → - [x] immediately
Document blockers — never skip silently, use [BLOCKED: reason]

Step 3: Follow Patterns

Reference references/patterns.md for project conventions and implementation patterns.

Step 4: Track Progress

Use scripts/progress.sh to visualize completion status.

Step 5: Report

## Implementation Summary

### Completed
- [x] Task 1: description

### Files Created/Modified
- `path/to/file.ts`: [purpose]

### Blockers Encountered
- [blocker and resolution]

### Discoveries
- [anything that should update specs]

Anti-Patterns

Skipping tasks without explanation
Marking items done without completing them
Implementing differently than planned without noting why
Ignoring blockers instead of documenting them

Integration

After completion, sdd-verifier subagent validates work (spawned as child subagent in 2.5+)
Discoveries trigger sdd-evolve skill for spec updates
Use the ask question tool for ambiguous requirements