Agent Skills
› NeverSight/learn-skills.dev
› doc-driven-spec-workflow
doc-driven-spec-workflow
GitHub根据文档状态路由至工作流下一阶段，识别当前阶段并传递上下文。适用于流程中断、阶段不明或需恢复状态的场景，确保严格按表跳转至引导、澄清、规划或任务准备技能。
Trigger Scenarios
用户想继续开发但当前阶段不明确
新对话需从文档恢复工作流状态
需在引导、澄清、规划、任务准备等阶段间切换
Install
npx skills add NeverSight/learn-skills.dev --skill doc-driven-spec-workflow -g -y
SKILL.md
Frontmatter
{
"name": "doc-driven-spec-workflow",
"description": "Routes docs-driven repository work to the correct workflow stage and preserves handoff context. Use when the next step is unclear between bootstrap, clarification, roadmap planning, task preparation, or execution."
}
Doc-Driven Spec Workflow
Purpose
Choose exactly one next stage skill. Do not do stage work here.
Use when
- the repository follows this docs-driven workflow
- the user wants to continue work but the current stage is not explicit
- a fresh conversation must recover workflow state from docs and the prompt
Read first
docs/tasks/index.mddocs/tasks/planning-inbox.mddocs/tasks/backlog.md- relevant milestone, module, and task docs under
docs/tasks/ docs/architecture/docs/context/- the current user prompt
Missing docs are routing signals, not proof that goals are unclear.
Owns
- identify the current workflow stage
- choose the next stage skill
- ask the smallest routing question when evidence is insufficient
- hand off
Decided,Undecided,Next skill, andStop point
Must not own
- scaffold creation details
- roadmap decomposition details
- task-local
spec.mdorplan.mdauthoring - execution isolation, implementation, verification, or branch closing
- local decisions that belong to the selected stage skill
Routing table
| Situation | Next skill |
|---|---|
| Minimum docs scaffold is missing | docs-workflow-bootstrap |
| Docs or prompt show unresolved goals, constraints, success criteria, or now-vs-later boundaries | planning-clarification |
| Milestone shape, module grouping, task breakdown, or delivery order is unclear | milestone-planning |
| A concrete task is selected or clearly selectable from confirmed roadmap state | task-preparation |
Entry checks
- Route to
docs-workflow-bootstrapwhen any minimum scaffold file is missing:docs/index.mddocs/architecture/index.mddocs/tasks/index.mddocs/tasks/planning-inbox.mddocs/tasks/backlog.mddocs/context/index.md
- Route to
planning-clarificationonly for positive ambiguity evidence. Missing or stale docs alone are not enough. - Route to
task-preparationonly when all are true:- the milestone has
Roadmap confirmed: yes - previous milestone closure is resolved when crossing milestones
- task status is
plannedorin_progress - dependencies are satisfied or explicitly waived
- no unresolved hard gate blocks progress
- the user selected the task, or docs clearly identify it as next
- the milestone has
Default flow
- Read docs in evidence order and identify the strongest routing signal.
- Choose exactly one next stage skill.
- If evidence is insufficient, ask one minimal routing question instead of guessing.
- Hand off only stage context, not stage-specific decisions.
Stop point
- handoff to one stage skill
- or one minimal routing question
If blocked
- ask one routing question when evidence does not identify the next stage
- do not answer the routing question on the user's behalf
- do not bypass uncertainty by drafting specs or inventing roadmap structure
Handoff
Current stageWhyDecidedUndecidedNext skillStop point
Version History
- e0220ca Current 2026-07-05 23:26
