docs-workflow-bootstrap

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

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.
  • 触发场景:通常在仓库缺少最小化文档脚手架时,从
    doc-driven-spec-workflow
    进入本流程。
  • 负责内容:最小化文档入口点和精简的搭建内容。
  • 不负责内容:路线图分解、任务创建、任务专属规格说明、计划、实施或分支关闭。
  • 交接流程:在报告已创建或修改的文件后,返回至
    doc-driven-spec-workflow
    ,除非用户明确要求继续进行规划。

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 unless the user provides an actual milestone/task.
  • 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.
  • 必须始终处于文档治理模式下完成搭建工作。
  • 除非用户明确要求更多内容,否则仅创建最小化的文档入口点。
  • 除非用户提供实际的里程碑/任务,否则不得创建实施任务。
  • 默认不得创建
    docs/specs/
    docs/plans/
    目录。
  • 不得编写任务专属的
    spec.md
    plan.md
    文件。
  • 必须报告已创建或修改的文件,然后停止操作。

Bootstrap Layout

搭建布局

Create these files when missing:
  • docs/index.md
  • docs/architecture/index.md
  • docs/tasks/index.md
  • docs/context/index.md
Use the repository's documentation language instructions when available. Otherwise follow the user's current language request.
当以下文件缺失时创建它们:
  • docs/index.md
  • docs/architecture/index.md
  • docs/tasks/index.md
  • docs/context/index.md
如果仓库有指定的文档语言要求,则遵循该要求;否则按照用户当前的语言请求执行。

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 and include
    Open Milestones
    and
    Completed Milestones
  • docs/context/index.md
    : explain research notes and supporting context
Do not create roadmap details during bootstrap unless the user supplies actual roadmap content.
生成的文件需保持精简:
  • docs/index.md
    :说明文档入口点,并链接至架构、任务和上下文文档
  • docs/architecture/index.md
    :说明稳定的设计和行为边界
  • docs/tasks/index.md
    :说明路线图/任务跟踪方式,并包含“开放里程碑”和“已完成里程碑”板块
  • docs/context/index.md
    :说明研究笔记和支持性上下文内容
除非用户提供实际的路线图内容,否则在搭建阶段不得创建路线图细节。

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-spec-execution
    only when the user explicitly asks and a concrete task already exists or is selected.
Stop after reporting the bootstrap result unless the user explicitly asks to continue.
搭建完成后:
  • 返回至
    doc-driven-spec-workflow
    ,由其选择下一阶段。
  • 仅当用户明确要求规划里程碑、模块和任务时,直接进入
    milestone-planning
    流程。
  • 仅当用户明确要求且已有具体任务存在或已选定任务时,直接进入
    task-spec-execution
    流程。
除非用户明确要求继续操作,否则在报告搭建结果后停止。