project-init

Project Init

Initialize a project into the ProjectGovernor workflow system.

Overview

Collects project metadata (name, type A/B, description), creates the docs/governor/ directory structure, and writes project.yaml. This is the mandatory entry point — all other governor skills require a completed init.

Hard Gate

This skill has no prerequisites. It IS the prerequisite for everything else.

Required Plugins

ProjectGovernor delegates actual work to existing skills. All three plugins must be installed before using governor skills:

Plugin	Install	Required Skills
Superpowers	claude install-plugin superpowers	brainstorming, writing-plans, verification-before-completion, requesting-code-review, dispatching-parallel-agents, subagent-driven-development
Frontend Design	claude install-plugin frontend-design	frontend-design (Type B only)
Everything Claude Code	claude install-plugin everything-claude-code	continuous-learning-v2, architecture-decision-records

Type A projects do NOT require Frontend Design plugin. All projects require Superpowers + ECC.

PDCA Cycle

digraph init_pdca {
    rankdir=LR;
    node [shape=box, style=filled];
    "P: Define goals" [fillcolor="#E3F2FD"];
    "D: Create structure" [fillcolor="#E8F5E9"];
    "C: Verify init" [fillcolor="#FFF3E0"];
    "A: Handoff" [fillcolor="#F3E5F5"];

    "P: Define goals" -> "D: Create structure" -> "C: Verify init" -> "A: Handoff";
    "C: Verify init" -> "D: Create structure" [label="fail", style=dashed];
}

Plan

• 目标：建立项目治理基座，明确项目类型和阶段路线图
• 输入：用户口述的项目信息
• 产出：docs/governor/project.yaml + 目录结构
• 验收标准：project.yaml 合法，所有目录存在

Do

1. Verify dependencies — 依次检查所有依赖插件是否已安装。Try invoking each dependency skill with the Skill tool. 收集所有缺失的依赖后一次性报告：

   • 列出所有缺失的插件及其影响
   • 提供一条合并的安装命令（用 && 连接所有 claude install-plugin 命令）
   • 提示用户安装完成后重新运行 project-governor:project-init
   • Do NOT proceed with init until all required plugins for the project type are available

   报告格式示例（有缺失时）：

   ⚠️ 以下插件未安装：
   
     1. superpowers — 所有治理阶段将无法运行
     2. everything-claude-code — 回顾阶段将无法运行
   
   请执行以下命令一键安装：
     claude install-plugin superpowers && claude install-plugin everything-claude-code
   
   安装完成后，重新运行 /project-governor:project-init 即可。
   

   B 型项目额外检查 frontend-design。 所有依赖已安装时，静默通过，无需输出。

2. Detect existing project — Scan the current working directory for indicators of an existing project:

   • Project config files: package.json, Cargo.toml, pyproject.toml, go.mod, build.gradle, pom.xml, etc.
   • Source code directories: src/, lib/, app/, cmd/, internal/, etc.
   • Documentation: README.md, docs/, CLAUDE.md, etc.

   If existing project detected:

   • Check if docs/governor/INDEX.md already exists (governance previously completed)
   • If INDEX.md exists: 读取索引了解项目治理全貌，向用户展示已完成阶段摘要，询问"要继续哪个阶段还是开启新周期？"
   • If INDEX.md does NOT exist: Analyze the codebase: directory structure, tech stack, key modules, architecture patterns
   • Write a 现状分析 document to docs/governor/specs/YYYY-MM-DD-<project-name>-现状分析.md（中文）, covering:
     • 技术栈：检测到的语言、框架、主要依赖
     • 项目结构：目录布局和各模块职责
     • 核心功能：从代码和文档中提取的主要功能
     • 架构模式：检测到的设计模式、分层结构
     • 改进空间：用户口述或从代码中观察到的待改进点
   • Set existing_project: true in project.yaml
   • Auto-detect project type from codebase（has UI components → suggest Type B, else Type A）and confirm with user: "检测到这是一个已有项目。根据代码结构判断为 Type ，确认吗？"

   If greenfield project:

   • Set existing_project: false in project.yaml
   • Proceed to next step

3. Ask the user: "Is this a Type A project (CLI/Agent, no UI) or Type B (UI product)?" (Skip if auto-detected in step 2)

4. Ask the user: "Auto mode? (true = automatically chain to next phase after each gate passes, false = stop and prompt after each phase)"

5. Collect metadata: project name, brief description, team size (optional)

6. Create directory structure under docs/governor/

7. Write project.yaml with metadata + cycle: 1 + auto: true|false

8. Create docs/governor/INDEX.md — 治理产物索引，初始内容：

   # 治理产物索引
   
   > 自动生成。每个阶段 PASS 后更新。Claude 按需读取此文件了解项目治理全貌。
   
   **项目**: <name> | **类型**: A/B | **当前周期**: 1 | **当前阶段**: init
   
   | 日期 | 阶段 | 产物路径 | 说明 |
   |------|------|---------|------|
   

9. Print phase roadmap for the project type

Check (阶段门禁)

Verify init completion:

• docs/governor/project.yaml exists and is valid YAML
• type field is A or B (not empty)
• All artifact directories exist (specs/, flows/, states/, ui/, plans/, gates/, retros/)
• current_phase is set to init

If any check fails → fix and re-verify.

Act

• PASS: Set current_phase: init, append init to phases_completed.
  • If auto: true: Automatically invoke project-governor:requirements-freeze.
  • If auto: false: Tell user: "Init complete. Next: invoke project-governor:requirements-freeze"
• FAIL: Fix the issue, re-run Check.

project.yaml Schema

name: <project-name>
type: A | B
description: <one-line description>
team_size: <number or omit>
existing_project: true | false  # true = 基于已有项目改进
auto: true | false       # true = auto-chain to next phase after PASS
cycle: 1
current_phase: init
created: YYYY-MM-DD
updated: YYYY-MM-DD
phases_completed: []

Directory Creation

docs/governor/
├── project.yaml
├── specs/
├── flows/
├── states/
├── ui/          # created even for type A (empty, skipped)
├── plans/
├── gates/
└── retros/

Roadmap Output

After init, print a roadmap showing the phase sequence. Each phase runs its own internal PDCA:

Type A:

[1] Requirements Freeze [PDCA] → [2] Flow Design [PDCA] → [3] State Design [PDCA] → [5] Implementation Plan [PDCA] → [6] Stage Gate (cross-phase) → [7] Retrospective

Type B:

[1] Requirements Freeze [PDCA] → [2] Flow Design [PDCA] → [3] State Design [PDCA] → [4] UI Design [PDCA] → [5] Implementation Plan [PDCA] → [6] Stage Gate (cross-phase) → [7] Retrospective