Back to Details

doc-driven-spec-workflow

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Using Doc-Driven Spec Workflow

使用文档驱动的规范工作流

Use this root skill to select and coordinate the right docs-driven workflow skill.
This skill is the entry protocol for the workflow. It does not own bootstrap, planning, specs, plans, implementation, templates, or branch-closing details. Those belong to the stage-specific skills.
This is analogous to 
using-superpowers
: it makes the agent choose and respect the right composable skill instead of improvising the whole workflow from memory.
使用这个根skill来选择并协调合适的文档驱动工作流skill。
此skill是工作流的入口协议。它不负责引导启动、规划、规范、计划、实现、模板或分支关闭的细节。这些属于特定阶段的skill。
这类似于
using-superpowers
：它让agent选择并遵循正确的可组合skill，而非仅凭记忆即兴完成整个工作流。

Mandatory Rules

强制规则

  • MUST start docs-driven repository work by identifying the current workflow stage.
  • MUST load exactly one stage skill next unless the user explicitly asks for a comparison or audit.
  • MUST delegate stage behavior to the selected skill instead of restating or bypassing that skill's rules.
  • MUST treat roadmap planning and task reshaping as docs governance. They do not authorize spec writing or implementation by themselves.
  • MUST stop at approval gates. 
    continue
    is not approval for roadmap structure, spec, plan, branch closing, or destructive cleanup.
  • MUST preserve handoff context when switching skills: what is decided, what is undecided, and why the next skill applies.
  • 必须通过识别当前工作流阶段来启动文档驱动型仓库工作。
  • 除非用户明确要求进行比较或审计，否则下一步必须加载恰好一个阶段skill。
  • 必须将阶段行为委托给所选skill，而非重述或绕过该skill的规则。
  • 必须将路线图规划和任务重塑视为文档治理。它们本身不授权规范编写或实现工作。
  • 必须在审批节点处停止。
    continue
    并不代表对路线图结构、规范、计划、分支关闭或破坏性清理的审批。
  • 切换skill时必须保留交接上下文：已确定的内容、未确定的内容，以及选择下一个skill的原因。

Workflow Chain

工作流链

Default chain:
docs-workflow-bootstrap -> superpowers:brainstorming -> milestone-planning -> task-spec-execution
Not every request uses every stage. Skip stages only when their decision is already settled.
默认链：
docs-workflow-bootstrap -> superpowers:brainstorming -> milestone-planning -> task-spec-execution
并非每个请求都会用到所有阶段。仅当某阶段的决策已确定时才可跳过该阶段。

Routing Rules

路由规则

Choose the next skill by the user's current uncertainty:
  • "We need the minimum docs scaffold first." -> 
    docs-workflow-bootstrap
  • "We still do not understand what we are building." -> 
    superpowers:brainstorming
  • "We understand the request, but not the milestone/module/task shape." -> 
    milestone-planning
  • "We know the current concrete task and need spec-first execution." -> 
    task-spec-execution
Use 
docs-workflow-bootstrap
when the repository lacks:
  • docs/index.md
  • docs/architecture/index.md
  • docs/tasks/index.md
  • docs/context/index.md
Use 
superpowers:brainstorming
when goals, constraints, success criteria, or "now versus later" boundaries are still ambiguous.
Use 
milestone-planning
when the user needs milestone count, module grouping, task breakdown, delivery order, or stage boundaries.
Use 
task-spec-execution
only after a concrete task exists or is selected and the user wants task-local 
spec.md
, optional 
plan.md
, readiness, implementation, verification, or branch closing.
Do not skip directly from ambiguous scope to spec writing. Do not use 
task-spec-execution
to invent roadmap structure. Do not keep using 
milestone-planning
after the question becomes current-task execution.
根据用户当前的不确定性选择下一个skill：
  • “我们首先需要最小化的文档脚手架。” -> 
    docs-workflow-bootstrap
  • “我们仍然不清楚要构建什么。” -> 
    superpowers:brainstorming
  • “我们理解需求，但不清楚里程碑/模块/任务的具体形态。” -> 
    milestone-planning
  • “我们明确当前的具体任务，需要先执行规范编写。” -> 
    task-spec-execution
当仓库缺少以下文件时，使用
docs-workflow-bootstrap
：
  • docs/index.md
  • docs/architecture/index.md
  • docs/tasks/index.md
  • docs/context/index.md
当目标、约束、成功标准或“当前与后续”边界仍不明确时，使用
superpowers:brainstorming
。
当用户需要确定里程碑数量、模块分组、任务拆解、交付顺序或阶段边界时，使用
milestone-planning
。
仅当存在或已选定具体任务，且用户需要针对该任务的本地
spec.md
、可选的
plan.md
、就绪检查、实现、验证或分支关闭时，才可使用
task-spec-execution
。
不得从模糊范围直接跳到规范编写。 不得使用
task-spec-execution
来创建路线图结构。 当问题变为当前任务执行时，不得继续使用
milestone-planning
。

Handoff Rules

交接规则

  • docs-workflow-bootstrap -> superpowers:brainstorming or milestone-planning
    : after the minimum docs scaffold exists
  • superpowers:brainstorming -> milestone-planning
    : after scope, boundaries, and success criteria are clear enough to plan delivery structure
  • milestone-planning -> task-spec-execution
    : after the current concrete task is selected and the user wants to enter spec-first execution
At each handoff, briefly restate:
  • what has already been decided
  • what remains undecided
  • what the next skill is responsible for
  • which explicit approval gate, if any, remains outstanding
Treat a user message such as 
continue
as permission to advance to the next workflow stage only when the current stage is complete and no explicit approval gate is outstanding.
Do not treat 
continue
as automatic approval for:
  • roadmap structure that still needs confirmation
  • spec approval
  • plan approval
  • branch closing or destructive cleanup decisions
  • docs-workflow-bootstrap -> superpowers:brainstorming 或 milestone-planning
    ：在最小化文档脚手架搭建完成后
  • superpowers:brainstorming -> milestone-planning
    ：在范围、边界和成功标准足够清晰，可规划交付结构后
  • milestone-planning -> task-spec-execution
    ：在选定当前具体任务，且用户希望进入先规范后执行的阶段后
每次交接时，简要说明：
  • 已确定的内容
  • 仍未确定的内容
  • 下一个skill的职责
  • （如有）尚未完成的明确审批节点
仅当当前阶段已完成且无未完成的明确审批节点时，才将用户的
continue
等消息视为推进到下一工作流阶段的许可。
不得将
continue
视为对以下内容的自动审批：
  • 仍需确认的路线图结构
  • 规范审批
  • 计划审批
  • 分支关闭或破坏性清理决策

Response Shape

响应格式

Keep orchestration responses compact:
  1. Current stage
  2. Why this stage applies
  3. Next skill to use
  4. Expected stop point
协调类响应需简洁：
  1. 当前阶段
  2. 此阶段适用的原因
  3. 下一步要使用的skill
  4. 预期停止点