spec-flow
Spec-driven development workflow. Interactive phase-by-phase confirmation from proposal to implementation. Trigger: 'spec-flow', 'spec mode', 'need a plan', 'structured development', 'write a spec', 'feature spec', 'technical spec', '需求文档', '技术方案', '任务拆解', '规格驱动', '写个方案', '做个规划', '结构化开发', 'plan this feature', 'break this down', 'design doc'. Creates .spec-flow/ directory with proposal, requirements, design, and tasks.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/echovic/spec-flowSpec-Flow - Structured Development Workflow
Structured workflow for complex feature development. Creates living documentation that guides implementation and serves as team reference.
Core Principles
- One phase at a time — NEVER generate documents for subsequent phases in advance
- Mandatory confirmation — After each phase, STOP and wait for user confirmation
- User-driven progression — Only proceed when user says "continue"/"ok"/"next"/"继续"/"好"
Parameters
| 参数 | 说明 |
|---|---|
--fast | 跳过逐阶段确认,一次性生成所有文档(最后整体确认) |
--skip-design | 跳过 Design 阶段(简单功能,架构显而易见时) |
Language Rule
所有生成的 .md 文件必须使用中文。
Interaction Rules
Load references/interaction-rules.md for detailed confirmation templates and prohibited behaviors.
Five-Phase Workflow
Copy this checklist and check off items as you complete them:
Spec-Flow Progress:
-
Phase 0: Initialize ⚠️ REQUIRED
- 0.1 Run
scripts/init-spec-flow.sh <feature-name>or create.spec-flow/active/<feature>/ - 0.2 Check if
.spec-flow/steering/exists — if so, read for project context - 0.3 问自己:这个功能的核心价值是什么?用一句话能说清吗?
- 0.1 Run
-
Phase 1: Proposal ⚠️ REQUIRED
- 1.1 Create
.spec-flow/active/<feature>/proposal.mdusingtemplates/proposal.md.template - 1.2 包含:Background, Goals, Non-Goals, Scope, Risks, Open Questions
- 1.3 问自己:有没有隐含的需求没写出来?
- 1.4 问自己:Non-Goals 是否足够明确?能防止 scope creep 吗?
- 1.5 ⏸️ 确认节点 — 等待用户确认后继续
- 1.1 Create
-
Phase 2: Requirements
- 2.1 Create
.spec-flow/active/<feature>/requirements.mdusingtemplates/requirements.md.template - 2.2 Load
references/ears-format.md— 使用 EARS 格式编写需求 - 2.3 包含:FR-xxx 功能需求, NFR-xxx 非功能需求, AC-xxx 验收标准
- 2.4 问自己:每条需求都是可测试的吗?
- 2.5 问自己:边界情况覆盖了吗?错误场景呢?
- 2.6 ⏸️ 确认节点 — 等待用户确认后继续
- 2.1 Create
-
Phase 3: Design(除非
--skip-design)- 3.1 Create
.spec-flow/active/<feature>/design.mdusingtemplates/design.md.template - 3.2 包含:Architecture (Mermaid), Components, API, Data Model, Error Handling
- 3.3 问自己:这个设计能满足所有 requirements 吗?逐条对照
- 3.4 问自己:有没有更简单的方案?过度设计了吗?
- 3.5 ⏸️ 确认节点 — 等待用户确认后继续
- 3.1 Create
-
Phase 4: Tasks
- 4.1 Create
.spec-flow/active/<feature>/tasks.mdusingtemplates/tasks.md.template - 4.2 Load
references/task-decomposition.md— 遵循任务拆解规范 - 4.3 每个任务:1-2 tool calls 可完成,标注复杂度 Low/Medium/High
- 4.4 分组:Setup → Implementation → Testing → Documentation
- 4.5 问自己:任务之间的依赖关系对吗?有没有可以并行的?
- 4.6 ⏸️ 确认节点 — 等待用户确认后继续
- 4.1 Create
-
Phase 5: Implementation
- 5.1 Load
references/execution-modes.md— 确认执行模式 - 5.2 默认 Step Mode(逐任务确认),用户可切换 Batch/Phase Mode
- 5.3 每个任务执行前:读 tasks.md → 检查依赖 → 读 design.md
- 5.4 每个任务执行后:更新 tasks.md 状态(
- [ ]→- [x]) - 5.5 全部完成后:归档到
.spec-flow/archive/
- 5.1 Load
Directory Structure
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-echovic-spec-flow": {
"enabled": true,
"auto_update": true
}
}
}Related Skills
learning-system
AI 领域系统学习体系。管理知识图谱、深度学习笔记、实战复盘和关联网络。触发场景:学习计划、知识图谱更新、深度研究某个 AI 主题、实战复盘总结、调研后沉淀知识、每周学习回顾。当用户说'学了什么'、'总结一下'、'沉淀知识'、'复盘'、'更新图谱'、'深入研究'、'写笔记'、'学习回顾'、'review what I learned'、'update knowledge map'、'deep dive'、'recap'、'what did I learn' 时使用。当改完代码/读完论文/做完调研后需要提炼和归纳时使用。
boss
BMAD 全自动项目编排 Skill。从需求到部署的完整研发流水线,编排多个专业 Agent(PM、架构师、UI 设计师、Tech Lead、Scrum Master、开发者、QA、DevOps)自动完成完整研发周期。当用户说 'boss mode'、'/boss'、'全自动开发'、'从需求到部署'、'帮我做一个'、'build this'、'ship it'、'全流程'、'自动化开发'、'一键开发'、'start a project'、'new feature' 时使用。适用于新项目搭建或现有代码库添加功能。