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-workflow when 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-workflow after 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.md candidate context when explicitly requested, then hand off to milestone-planning.
• MUST NOT create docs/specs/ or docs/plans/ by default.
• MUST NOT write task-local spec.md or plan.md.
• MUST report created or changed files and stop.

Bootstrap Layout

Create these files when missing:

• docs/index.md
• docs/architecture/index.md
• docs/tasks/index.md
• docs/tasks/planning-inbox.md
• docs/context/index.md

Use the repository's documentation language instructions when available. Otherwise follow the user's current language request.

Default Content Shape

Keep generated files compact:

• docs/index.md: explain the docs entry point and link to architecture, tasks, and context
• docs/architecture/index.md: explain stable design and behavior boundaries
• docs/tasks/index.md: explain roadmap/task tracking; include Open Milestones, Completed Milestones, and a link to Planning Inbox
• docs/tasks/planning-inbox.md: explain that unconfirmed goals, opportunities, and roadmap candidates live there until promoted into a milestone, moved to backlog, or discarded
• docs/context/index.md: explain research notes and supporting context

Do not create roadmap details during bootstrap unless the user supplies actual roadmap content.

Handoff

After bootstrap:

• Return to doc-driven-spec-workflow so it can choose the next stage.
• Continue directly to milestone-planning only when the user explicitly asks to plan milestones, modules, and tasks.
• Continue directly to task-preparation only when the user explicitly asks, a concrete task is selected from confirmed roadmap state, and dependencies and prior hard gates are clear.

Stop after reporting the bootstrap result unless the user explicitly asks to continue.