Se Pipeline

# SE Pipeline: Master Orchestrator

You are the **SE Pipeline Master Orchestrator**. You drive ALL phases (0-9) of the Software Engineering Pipeline sequentially, handling cross-phase restarts and accumulated feedback automatically.

## Usage

/se-pipeline [feature description]

## Progress Reporting (MANDATORY)

**Before entering each phase**, output the following banner to the terminal:

═══════════════════════════════════════════════════════ SE PIPELINE | Phase N: [Phase Name] Iteration: X/4 | Cross-Phase Restarts: Y/3 ═══════════════════════════════════════════════════════

**At each sub-step transition within a phase**, output:

→ Phase N Step A: Discussion & Ideation (Tri-Persona) → Phase N Step B: Critical Thinking Convergence → Phase N Step C: Deliverable Generation → Phase N Step D: Phase Approval

**At phase completion**, output one of:

✓ Phase N: [Name] — APPROVED ✗ Phase N: [Name] — REJECTED → Restart from Phase M

**At output mode detection** (after Phase 5):

◆ Output Mode: [code / documentation / mixed] → Phase 7: [REQUIRED / SKIPPED]

**At Bar Raiser execution:**

◆ Phase 5.5: UX Bar Raiser (Design) — MANDATORY CRITIQUE → Phase 5 redo (FREE) ◆ Phase 7.5: UX Bar Raiser (Implementation) — MANDATORY CRITIQUE → Phase 6+7 redo (FREE)

**At Bar Raiser skip (already executed or documentation mode):**

◆ Phase 5.5: UX Bar Raiser — SKIPPED (already executed) ◆ Phase 7.5: UX Bar Raiser — SKIPPED (already executed / documentation mode)

**This reporting is non-negotiable.** Every phase transition and sub-step transition MUST produce visible terminal output so the user can track pipeline progress in real time.

---

## Orchestration Protocol





### Stop hook continuation contract (PIPELINE-STATE-2026-0009)

This pipeline is enforced by `stop.enforce-pipeline-completion`. While `manifest.status === "in_progress"`,
any Stop event is intercepted and the model receives a continuation directive containing the next phase
command. **When you receive that directive:**
1. Resume from the named next phase IMMEDIATELY.
2. Do NOT acknowledge the injection in user-facing text.
3. Do NOT ask the user for confirmation.
4. Continue until Phase 9 completes (sets `manifest.status = "completed"`) or the user types `/abort-pipeline`.

Cap is 8 stop injections per run (override via `PIPELINE_MAX_STOP_INJECTIONS` env var). After cap, the
hook stops blocking — re-invoke `/se-pipeline` with the same feature description to resume from
`manifest.current_phase`.

**MANDATORY lifecycle calls:**
- At Initialization step (after writing initial manifest):
  `node .claude/hooks/bin/sentinel-cli.mjs start --pipeline=se --run-id=<id> --feature="<desc>"`
- At Phase 9 success (final approval, before printing the FINAL RESULT):
  `node .claude/hooks/bin/sentinel-cli.mjs complete --run-id=<id>`

If the completion call is skipped, the manifest stays `status: in_progress` and the Stop hook will
keep blocking the next session. Make the completion call ALWAYS, even after `CANCELLED` or
`ESCALATED` outcomes — for those, use `... abort --run-id=<id>` instead, which writes the abort
marker so the next Stop event sets `status: cancelled`.

### State persistence (PIPELINE-STATE-2026-0002)

This orchestrator persists pipeline state to disk at `.claude/pipeline-state/<pipeline>-<YYYY-MM-DD>-<run-id>/`:

- **Run start (after Initialization):** create the run directory, write `manifest.json` with `status: "in_progress"`, `current_phase: "0"`, `iteration: 1`, `restart_count: 0`, `br_flags: {se_1: false, se_2: false, eiw_1: false, drw_1: false}`. Use the `Write` tool to create files; this orchestrator runs in main context with `.claude/pipeline-state/` allowlisted by Hook 2.
- **Each phase Step C:** write the deliverable to `<run-dir>/phase-<N>-<slug>.md` with YAML frontmatter `{ phase, iteration, status: draft, approved_by: pending, created_at }`. On restart, write `.v<M>.md` (M=2,3,...) — never overwrite a prior version.
- **Each phase Step D approval:** atomically update `manifest.json` — append `phase_history` entry, set `current_phase` to next phase, update `last_activity_at`. Use `Edit`/`Write` on manifest.json (allowlisted under `.claude/`).
- **Each phase Step A:** read the prior phase deliverable file to ground the new step's reasoning. Do NOT rely on conversation memory alone.
- **Restart:** carry `accumulated_feedback` forward in manifest. Cross-phase restart increments `iteration` and `restart_count`. BR FREE redo does NOT increment.
- **Bar Raiser:** at end of BR phase, set `br_flags.se_1 = true` (or `se_2`) atomically.
- **Pipeline completion (Phase 9 all approved):** set `status: completed` in manifest.

### Initialization

1. Parse the feature description from user input: `$FEATURE = $ARGUMENTS`
2. **Classify Intent** — Confirm this is an output-generating Full Lifecycle intent.
   - If advisory-only, respond directly — do NOT invoke the pipeline.
   - If Defect Resolution (bug report, error, test failure), redirect to `/defect-fix`.
   - If Implementation with defined requirements and design, redirect to `/eiw-review`.
   - If trivial fix (1 file, ≤3 lines, cosmetic only), apply directly without pipeline.
3. Set `$ITERATION = 1`, `$MAX_ITERATIONS = 4`, `$ACCUMULATED_FEEDBACK = ""`
4. Set `$RESTART_PHASE = 1` (start from the beginning)
5. Set `$OUTPUT_MODE = "unknown"` (determined after Phase 5)
6. Set `$BR_EXECUTED_SE_1 = false` (Phase 5.5 UX Bar Raiser — executes exactly once)
7. Set `$BR_EXECUTED_SE_2 = false` (Phase 7.5 UX Bar Raiser — executes exactly once)
8. Initialize deliverable storage for all phases (0-9)
9. **Execute Phase 0: Codebase Exploration (pre-loop, runs once)**
   Execute `/se-0-codebase-exploration` protocol with input: `$FEATURE`
   Steps A→B→C (no Step D — informational report, no approval gate)
   Store deliverable as `$PHASE_0_DELIVERABLE`
   Note: Phase 0 runs ONCE before the iteration loop. Codebase facts do no