spec-driven-development

Name: spec-driven-development
Availability: InStock
Author: moonklabs

Generate specifications, plans, and task files for new features.

1|Updated Jun 21, 2025

Search Tags:#Claude Code #계획 #명세 #명세 기반 개발 #태스크 #워크플로우

Ready to run

npx skills add https://github.com/moonklabs/aiwf --skill spec-driven-development-moonklabs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/moonklabs/aiwf/tree/main/claude-code/aiwf/ko/.claude/skills/spec-driven-development
Command: npx skills add https://github.com/moonklabs/aiwf --skill spec-driven-development-moonklabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

이 한국어 버전은 외부 의존 없이 독립 실행 가능한 명세 기반 개발 워크플로우를 제공하여 명세서로부터 계획, 태스크, 구현까지의 흐름을 자동으로 생성합니다. Superpowers와의 연계 실행도 지원합니다.

Core Features & Use Cases

Standalone SD 워크플로우: specify, plan, tasks, implement 단계
생성 산출물: .sdd/specs, plan.md, data-model.md, tasks.md
Superpowers 연동: 선택적 실행 지원

Quick Start

specify: [기능 설명]으로 명세 생성, plan: [기술 스택]으로 계획 생성, tasks, implement 예시: specify: 사진 앨범 정리 앱 plan: React + SQLite

Frequently Asked Questions about spec-driven-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate a specification and development plan from feature requirements?▼

Spec-driven development generates structured specifications and implementation plans from feature descriptions. Use the specify command with your feature description, then plan to define technology stack, producing spec.md, plan.md, data-model.md, and tasks.md artifacts that guide development from requirements through execution.

Can I create independent, testable user stories and task decomposition without external tools?▼

Yes. This workflow generates independently executable user stories and decomposes features into granular tasks within a standalone environment. It produces task.md with actionable items and corresponding implementation scaffolds, enabling development without external dependency management.

What's the workflow for going from feature concept to implementation scaffolds?▼

The four-stage workflow moves from specify (WHAT/WHY) through plan (technology stack and architecture), tasks (decomposition), to implement (starter code). Each stage generates documented artifacts, creating a traceable path from initial concept to ready-to-develop implementation templates.

Does this approach work for planning technology stacks and data models?▼

Yes. The plan stage accepts technology stack input and generates architecture decisions, data-model.md, and structured implementation guidance. It supports defining frameworks, databases, and component relationships before writing production code.

Can I use this for new projects or only feature additions?▼

Spec-driven development applies to both new projects and incremental features. It generates complete specification and planning artifacts independently, making it suitable for greenfield projects, feature branches, or architectural planning at any project stage.

What outputs does the workflow produce?▼

The specification-first workflow produces spec.md (requirements), plan.md (architecture), data-model.md (schema and entities), tasks.md (decomposed work items), and implementation starter scaffolds—all generated without external dependencies.

jeffss00

prd

Generates detailed product requirements documents (PRDs) for specified features and scenarios, automating workflows and improving consistency for teams who rely on them to guide development.

Community

Advanced