docs-workflow-bootstrap
Docs Workflow Bootstrap
Initialize the minimum docs-driven workflow scaffold for a repository. This skill is only for bootstrap docs governance; 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
- MUST keep bootstrap work in docs governance mode.
- MUST create only the minimum docs entry points unless the user explicitly asks for more.
- MUST NOT create implementation tasks during bootstrap.
- If the user provides actual roadmap or task content during bootstrap, record it only as compact
planning-inbox.mdcandidate context when explicitly requested, then hand off tomilestone-planning. - MUST NOT create
docs/specs/,docs/plans/, or task-localspec.md/plan.mdby default. - MUST report created or changed files and stop.
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.
35task-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.
10doc-driven:task-spec-execution
Use when a docs-driven repository has a selected or selectable concrete docs/tasks task and needs task-local spec or implementation governance before code changes.
1