How do I install the Doc Driven Spec Workflow skill?

Run npx skillmds@latest add adol1111/doc-driven-spec-workflow in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Doc Driven Spec Workflow safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Doc Driven Spec Workflow?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Doc Driven Spec Workflow free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Doc Driven Spec Workflow?

adol1111 (@adol1111) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Doc Driven Spec Workflow by adol1111

Name: Doc Driven Spec Workflow
Author: adol1111

Doc Driven Spec Workflow

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.

adol1111 dee0a62 2 files · 3.5 KB Updated Sep 17, 2026

File contents

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.md
docs/tasks/planning-inbox.md
docs/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, and Stop point

Must not own

scaffold creation details
roadmap decomposition details
task-local spec.md or plan.md authoring
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-bootstrap when any minimum scaffold file is missing:
- docs/index.md
- docs/architecture/index.md
- docs/tasks/index.md
- docs/tasks/planning-inbox.md
- docs/tasks/backlog.md
- docs/context/index.md
Route to planning-clarification only for positive ambiguity evidence. Missing or stale docs alone are not enough.
Route to task-preparation only when all are true:
- the milestone has Roadmap confirmed: yes
- previous milestone closure is resolved when crossing milestones
- task status is planned or in_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

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 stage
Why
Decided
Undecided
Next skill
Stop point

---name: doc-driven-spec-workflowdescription: 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## PurposeChoose 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 first1. `docs/tasks/index.md`2. `docs/tasks/planning-inbox.md`3. `docs/tasks/backlog.md`4. relevant milestone, module, and task docs under `docs/tasks/`5. `docs/architecture/`6. `docs/context/`7. the current user promptMissing 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`, and `Stop point`## Must not own- scaffold creation details- roadmap decomposition details- task-local `spec.md` or `plan.md` authoring- 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-bootstrap` when any minimum scaffold file is missing: - `docs/index.md` - `docs/architecture/index.md` - `docs/tasks/index.md` - `docs/tasks/planning-inbox.md` - `docs/tasks/backlog.md` - `docs/context/index.md`- Route to `planning-clarification` only for positive ambiguity evidence. Missing or stale docs alone are not enough.- Route to `task-preparation` only when all are true: - the milestone has `Roadmap confirmed: yes` - previous milestone closure is resolved when crossing milestones - task status is `planned` or `in_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## Default flow1. Read docs in evidence order and identify the strongest routing signal.2. Choose exactly one next stage skill.3. If evidence is insufficient, ask one minimal routing question instead of guessing.4. 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 stage`- `Why`- `Decided`- `Undecided`- `Next skill`- `Stop point`

Frequently asked questions