plan-forge status-reporting.instructions.md

Status Reporting Templates

When to use: During forge_run_plan execution, multi-agent orchestration, autonomous runs, slice monitoring, and session handoffs. Use the template that matches the moment — don't force every message into a template.

---

Template 1: Progress Update

Use during long-running operations to report current state. Send every 2–3 slices or every 5 minutes, whichever comes first.

## Progress Update

**Run:** <plan name>
**Current:** Slice <N> — <slice title>
**Status:** <Running | Waiting for gate | Queued>
**Completed:** <N>/<total> slices passed
**Failed:** <N> (if any)
**Next:** Slice <N+1> — <title>
**ETA:** ~<X> minutes remaining

Example:

## Progress Update

**Run:** Phase-22-COPILOT-PLATFORM-v2.15
**Current:** Slice 3 — `forge_export_plan`
**Status:** Running (~10 min so far)
**Completed:** 2/8 slices passed
**Failed:** 0
**Next:** Slice 4 — `forge_sync_memories`
**ETA:** ~35 minutes remaining

---

Template 2: Slice Complete

Use immediately after a slice passes its validation gate.

## Slice Complete

**Slice:** <N> — <title>
**Result:** <Passed | Passed with warnings>
**Duration:** <X> min
**Gate:** <gate evidence summary>
**Files changed:** <count>
**Key outputs:** <1–2 line summary of what was built>
**Next:** Slice <N+1> — <title>

---

Template 3: Blocker Report

Use when execution is stalled and needs human input or a fix.

## ⚠ Blocker

**Slice:** <N> — <title>
**Problem:** <what failed>
**Cause:** <root cause or best guess>
**Impact:** <what's blocked downstream>
**Attempted:** <what was tried, if anything>
**Next action:** <specific fix or question for human>

---

Template 4: Failure / Recovery Report

Use when a slice fails its gate and the system is retrying or escalating.

## ❌ Slice Failed

**Slice:** <N> — <title>
**Attempt:** <N> of <max>
**Error:** <error message or gate output>
**Model:** <model used>
**Recovery:** <Retrying | Escalating to <model> | Awaiting human input>
**Files affected:** <list>