プロジェクトの統合分析を担当するエージェント。 コンテキスト(CLAUDE.md、ディレクトリ構造、技術スタック)・コードパターン(API、DB、コンポーネント)・Git履歴を 一体的に理解し、「プロジェクトの全体像 + この機能に関する洞察」を1つの統合レポートで返す。 Use PROACTIVELY at the start of spec generation to gather project context and code patterns. 構造化された要約を返し、メインコンテキストに大量のコードを展開しない。
以下の形式で統合レポートを返すこと:
- {何を探索したかったか}
- {API/パターン}: {このバージョンでの正しい使い方}({出典URL})
- {何を決めるための調査か}
Implements features based on plan.md. Handles feature branch creation, task-by-task coding with dependency order, and build verification. Supports pause/resume via progress.md state tracking. Use when starting implementation.
Verifies implementation code matches plan.md specifications. Reports PASS / PARTIAL / NEEDS_FIX. On NEEDS_FIX, guides user back to spec update or build fix. Use after /build completion or before PR merge.
Investigates root causes of runtime issues by tracing actual execution flows. Prohibits speculative fixes until cause is identified. Operates in feature mode (with plan.md) or standalone mode (without). Use when encountering bugs, errors, or unexpected behavior.
Displays all plans under docs/plans/ with status information and lets the user select a plan to edit, build, research, or check. Use as a hub for navigating existing plans.
Investigates technical topics through codebase analysis and web research. Outputs research-{date}-{topic}.md with findings, comparisons, and recommendations. Use when exploring options, comparing libraries, or investigating architecture decisions.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A lightweight spec-driven development plugin for Claude Code.
Guides you from requirements hearing through design, implementation, and verification with 5 skills centered around plan.md.
/plugin marketplace add 884js/spec-flow
/plugin install spec-flow@884js-spec-flow
(research) → spec → build → check → done
^ |
| (NEEDS_FIX) |
+----------------+
fix can be invoked independently at any time
list can be invoked at any time as a navigation hub
| Step | Skill | Role |
|---|---|---|
| - | /spec-flow:list | Displays all plans with status and lets you navigate to any skill |
| 0 | /spec-flow:research | Technical investigation → research.md generation. Supports codebase analysis and web research |
| 1 | /spec-flow:spec | Requirements hearing → integrated analysis → direction confirmation → plan.md generation → browser review (Annotation Cycle) → progress.md generation |
| 2 | /spec-flow:build | Branch creation → task-by-task implementation → build verification → PR creation, all guided by plan.md |
| 3 | /spec-flow:check | Compares implementation code against plan.md and reports PASS / PARTIAL / NEEDS_FIX |
| - | /spec-flow:fix | Root cause investigation with no speculative fixes allowed. Supports feature mode and standalone mode |
Displays all plans under docs/plans/ with status (in progress / not started / spec only / completed / verified) and lets you select a plan to edit, build, research, or check. Plans are sorted by priority — in-progress and not-started plans appear first. Supports pagination for large plan lists.
/spec-flow:list
Completes everything from requirements hearing to technical design and implementation planning in a single command. Supports new mode (plan.md generation) and update mode (plan.md update from check results or additional requirements). Also generates progress.md for task tracking (single mode for small/medium, multi-pr mode for large features).
(research) → hearing → analysis → direction confirmation → plan.md generation
→ Annotation Cycle (browser review) → progress.md generation
After plan.md generation, offers an Annotation Cycle — a browser-based review loop:
/spec-flow:spec add user notification feature
Output: docs/plans/{feature-name}/plan.md + progress.md
Implements features guided by plan.md. Covers branch creation → task-by-task coding → build verification → PR creation. Supports pause/resume via progress.md state tracking. Detects spec gaps during implementation and prompts for spec update.
/spec-flow:build
Reads implementation code directly and detects deviations from plan.md bidirectionally. Reports results as PASS (all conditions met) / PARTIAL (minor mismatches) / NEEDS_FIX (significant mismatches), generating result.md. On NEEDS_FIX, proposes spec update to close the loop.
/spec-flow:check
Prohibits speculative fixes and traces actual execution flows to identify root causes before proposing a fix. Operates in feature mode (with plan.md for spec correlation) or standalone mode (without plan.md).
/spec-flow:fix describe the error symptoms
Investigates technical topics through codebase analysis and web research.
Outputs research.md with findings, comparisons, and recommendations.
Results are automatically detected by /spec when creating a new spec.
/spec-flow:research authentication patterns for this project
Output: docs/plans/{feature-name}/research.md
skills/ ← User-facing entry points (orchestration)
list/spec/build/check/fix/research
agents/ ← Backend agents invoked via Task()
analyzer/ ← Project-wide integrated analysis
writer/ ← plan.md / progress.md / result.md generation
verifier/ ← Spec vs implementation comparison
researcher/ ← Technical investigation
scripts/ ← Utility scripts
annotation-viewer/ ← Browser-based plan.md review server
docs/plans/ ← All artifacts per feature
{feature-name}/
├── plan.md
├── progress.md
├── result.md
├── research.md
└── debug-*.md
This plugin is published on the Claude Code Plugin Marketplace.
/plugin marketplace add 884js/spec-flow
MIT
npx claudepluginhub 884js/spec-flow --plugin spec-flowAI変更前に自動セーブポイントを作成し、/rejectで戻せるプラグイン
Spec Driven Development toolkit - structured specification, planning, and implementation workflows for systematic feature development
Specification-Driven Development with Process Discipline for Claude Code
Specification-driven development workflow: specify → plan → tasks → implement
Spec-driven development methodology for Claude Code. Provides skills for requirements engineering (EARS format), design documentation, task breakdown, AI prompting strategies, quality assurance, and troubleshooting.
Spec-driven development with search, conflict detection, and reporting
Spec-driven development with task-by-task execution. Research, requirements, design, tasks, autonomous implementation, and epic triage for multi-spec feature decomposition.