doc-driven:docs-workflow-bootstrap
Docs Workflow Bootstrap
Initialize the minimum docs-driven workflow scaffold for a repository.
This skill is only for repository documentation bootstrap. It does not plan milestones, create implementation tasks, write specs, or authorize code changes.
Composition
- Entry: normally reached from
doc-driven-spec-workflowwhen the repository lacks the minimum docs scaffold. - Owns: minimum docs entry points and compact bootstrap content.
- Does not own: roadmap decomposition, task creation, task-local specs, plans, implementation, or branch closing.
- Handoff: return to
doc-driven-spec-workflowafter reporting created or changed files, unless the user explicitly asks to continue to planning.
Mandatory Rules
More from adol1111/doc-driven-spec-workflow
doc-driven-spec-workflow
Use when a docs-driven repository request is unclear about whether the next step is scaffold initialization, clarification, roadmap decomposition, or current-task execution.
36milestone-planning
Use when a request or repository needs roadmap decomposition before spec writing because milestone boundaries, module grouping, or independently reviewable tasks are unclear.
35task-spec-execution
Use when older prompts, installed workflows, or tests still refer to task-spec-execution and need a compatibility redirect into the split task-preparation or task-execution-simple stages.
35docs-workflow-bootstrap
Use when initializing, bootstrapping, creating, or scaffolding the minimum docs-driven workflow layout for a repository before roadmap planning, specs, or implementation tasks exist.
33task-execution-simple
Use when task-local spec or plan work is complete and a concrete docs/tasks task should be implemented through the repository's simple direct execution path.
11task-preparation
Use when a docs-driven repository has a selected or selectable concrete docs/tasks task and needs task-local spec or plan governance before code execution.
10