governor-run

Governor Run

Automatically chain through all remaining governance phases from the current project state. One command to run the full pipeline.

Overview

Reads docs/governor/project.yaml to determine the current phase, then sequentially invokes each remaining governor skill. When auto: true is set in project.yaml, each phase's Act step auto-invokes the next phase instead of stopping to prompt.

Hard Gate

Prerequisite: project-governor:project-init must be complete.

• Verify: docs/governor/project.yaml exists with valid state.

Usage Patterns

Pattern 1: Start from scratch

/project-governor:governor-run

If no project.yaml exists, this first runs project-init automatically, then proceeds through all phases.

Pattern 2: Resume from current state

If some phases are already complete (e.g., requirements and flow done), this picks up from the next incomplete phase and runs the rest.

Flow

digraph governor_run {
    rankdir=TB;
    node [shape=box, style=filled];
    "Read project.yaml" [fillcolor="#E3F2FD"];
    "Determine current phase" [fillcolor="#E3F2FD"];
    "Invoke next phase skill" [fillcolor="#E8F5E9"];
    "Phase completes" [fillcolor="#FFF3E0"];
    "More phases?" [shape=diamond, fillcolor="#FFF3E0"];
    "Done" [shape=doublecircle, fillcolor="#F3E5F5"];

    "Read project.yaml" -> "Determine current phase" -> "Invoke next phase skill" -> "Phase completes" -> "More phases?";
    "More phases?" -> "Invoke next phase skill" [label="yes"];
    "More phases?" -> "Done" [label="no"];
}

Execution Logic

Step 1: Verify or Init

1. Check if docs/governor/project.yaml exists
2. If NOT: invoke project-governor:project-init to create it. After init completes, continue to Step 2.
3. If YES: read current state. If docs/governor/INDEX.md exists, 读取索引了解项目治理全貌以恢复上下文。

Step 2: Determine Phase Order

Based on project type, build the phase sequence:

Type A:

requirements-freeze → flow-design → state-design → implementation-plan → stage-gate → retrospective

Type B:

requirements-freeze → flow-design → state-design → ui-design → implementation-plan → stage-gate → retrospective

Step 3: Find Resume Point

Read phases_completed from project.yaml. Find the first phase in the sequence that is NOT in phases_completed.

Step 4: Sequential Execution

语言要求：整个治理流程产出的所有文档必须使用中文。每个阶段 skill 的委托过程中都应包含中文输出指令。

Starting from the resume point, invoke each phase skill in order:

1. Invoke project-governor:<phase-name>
2. Wait for the phase to complete (its internal PDCA runs, gate check passes)
3. Move to the next phase
4. Repeat until retrospective completes

Step 5: Done

When retrospective finishes:

• If decision is ITERATE: print cycle summary and ask user if they want to auto-run the next cycle
• If decision is CLOSE: print final summary

Auto Mode

When auto: true in project.yaml:

• Each phase's Act step auto-invokes the next skill without waiting for user input
• Brainstorming-delegated phases (requirements, flow, state) will still ask essential clarifying questions — auto mode does NOT suppress questions that are necessary for the spec quality
• Gate failures still cause rework loops within the phase, but the phase doesn't stop after PASS

When auto: false (default):

• Each phase stops after PASS and prints the "Next: invoke ..." prompt
• User must manually invoke each subsequent phase

Output

After each phase completes, print a one-line status:

[Governor] Phase "requirements-freeze" complete ✓
[Governor] Phase "flow-design" complete ✓
[Governor] Phase "state-design" complete ✓
...

After all phases complete, print a summary:

[Governor] All phases complete. Cycle <N> finished.
- Requirements: docs/governor/specs/YYYY-MM-DD-*-requirements.md
- Flows:       docs/governor/flows/YYYY-MM-DD-*-flows.md
- States:      docs/governor/states/YYYY-MM-DD-*-states.md
- Plan:        docs/governor/plans/YYYY-MM-DD-*-plan.md
- Gate:        docs/governor/gates/gate-cross-phase-cycle-N.md
- Retro:       docs/governor/retros/YYYY-MM-DD-*-retro-cycle-N.md

Important Notes

• Brainstorming phases remain interactive — requirements-freeze, flow-design, state-design delegate to superpowers:brainstorming which asks clarifying questions. Auto mode chains phases together but does not skip user interaction within a phase.
• Gate failures are handled within each phase — if a gate-check fails, the phase loops back to Do internally. governor-run does not interfere with inner PDCA loops.
• Stage gate runs 3 parallel agents — this phase takes longer but runs automatically.
• Retrospective decides ITERATE or CLOSE — if ITERATE, governor-run asks whether to auto-start the next cycle.

PDCA Context

This skill is the outer orchestrator. It does not replace any phase's internal PDCA — it simply chains them together so the user doesn't need to manually invoke each one.