</purpose>

<context>
```bash
$quality-retrospective
$quality-retrospective "3"
$quality-retrospective "2..4"
$quality-retrospective "--all"
$quality-retrospective "3 --lens technical --no-route"
$quality-retrospective "3 --compare 2 -y"

Flags:

No phase argument -> scan mode: report unreviewed completed phases, prompt selection
<N> -> single mode: retrospect phase N
<N>..<M> -> range mode: retrospect phases N through M (inclusive)
--all -> batch mode: re-run for every completed phase
--lens <name> -- restrict to one lens (repeatable): technical|process|quality|decision
--no-route -- produce retrospective.{md,json} only; skip auto-creation of spec/note/issue
--compare <M> -- emit a delta section vs phase M's prior retrospective
-y -- accept all routing recommendations without prompting

When -y: Accept all routing recommendations without prompting. Route all insights automatically.

Storage written:

{target_dir}/retrospective.md -- human-readable record (target_dir resolved via state.json artifact registry to .workflow/scratch/{YYYYMMDD}-{type}-{slug}/)
{target_dir}/retrospective.json -- structured record
.workflow/specs/{category-file}.md -- <spec-entry> entries appended to matching category files (one per spec-routed insight)
.workflow/issues/issues.jsonl -- appended issue rows (source: "retrospective")
.workflow/knowhow/TIP-*.md -- knowhow tips (via manage-knowhow-capture skill)
.workflow/specs/learnings.md -- append-only insight log
Index auto-maintained by WikiIndexer

Storage read (never modified) — all resolved via state.json.artifacts[]:

# D-007 milestone reverse lookup — phase N may belong to a milestone different from current
target_milestone = resolve_milestone(target_phase)  # see below
related = artifacts.filter(a =>
  a.phase === target_phase && a.milestone === target_milestone
).sort_by(completed_at asc)

resolve_milestone(phase_number):
  for ms in state.json.milestones[]:
    if str(phase_number) in ms.phase_slugs: return ms.id
  return state.json.current_milestone   # fallback

Each artifact's type determines its outputs at .workflow/{a.path}/:

execute → index.json, plan.json, .task/TASK-.json, .summaries/TASK--summary.md
verify → verification.json
review → review.json (findings, verdict, severity distribution)
debug → understanding.md, evidence.ndjson (root causes, fix directions)
test → uat.md, .tests/ (UAT results, gaps, coverage)
Also reads: .workflow/issues/issues.jsonl, .workflow/state.json

Output boundary: ALL file writes MUST target the phase's retrospective directory (.workflow/scratch/{YYYYMMDD}-retrospective-P{N}/), .workflow/state.json, .workflow/issues.jsonl, or .workflow/specs/ (append-only). NEVER modify source code, verification.json, review.json, plan.json, or other existing artifacts.

Agent Registry

Agent	task_name	fork_turns	Responsibility
Context Agent	`ctx`	"none"	Load all phase artifacts: index.json, plan.json, verification.json, review.json, uat.md, issues.jsonl, task summaries
Technical Lens	`lens-tech`	"all"	Technical debt, architecture decisions, code quality gaps, performance issues
Process Lens	`lens-proc`	"all"	Workflow efficiency, collaboration patterns, planning accuracy, bottlenecks
Quality Lens	`lens-qual`	"all"	Test coverage gaps, verification failures, UAT issues, quality gate outcomes
Decision Lens	`lens-dec`	"all"	Key decisions made, tradeoffs accepted, ADR candidates, reversibility
Synthesizer	`synthesizer`	"none"	Merge lens results, deduplicate insights, classify routing targets

Fork Turns Strategy

Agent	task_name	fork_turns	fork_from	Rationale
Context Agent	`ctx`	"none"	--	Independent artifact loader; clean start
Technical Lens	`lens-tech`	"all"	`ctx`	Inherits loaded artifacts -- no redundant file reads
Process Lens	`lens-proc`	"all"	`ctx`	Inherits loaded artifacts -- no redundant file reads
Quality Lens	`lens-qual`	"all"	`ctx`	Inherits loaded artifacts -- no redundant file reads
Decision Lens	`lens-dec`	"all"	`ctx`	Inherits loaded artifacts -- no redundant file reads
Synthesizer	`synthesizer`	"none"	--	Clean context; receives lens results via message

Context-Agent Lifecycle: Spawn ctx first -> wait_agent -> spawn all lens agents (fork_turns: "all") -> wait_agent batch for lenses -> close_agent lenses -> close_agent ctx LAST.

fork_turns semantics: fork_turns: "all" means the spawned agent inherits the orchestrator's current conversation context -- not the ctx agent's own context. When wait_agent for ctx returns, the ctx agent's completed artifact summaries are visible in the orchestrator's context. Lens agents forked after that point therefore inherit those summaries. Lens agents do not fork directly from ctx; the fork_from: ctx column above is conceptual shorthand for this sequencing.

Session Initialization

Update plan: Stages 1-3 → in_progress; Stages 4-8 → pending.

Stages 1-3: Parse Mode and Validate Artifacts

Stage 1: Parse mode from $ARGUMENTS:

First non-flag token	Mode
(empty)	scan
`<N>` (single digit/number)	single
`<N>..<M>`	range
`--all` flag present	all

Validate --lens values. If --compare <M> present, require single mode.

Stage 2: Validate phase artifacts. For each target phase:

Phase directory must exist (resolved via state.json artifact registry to .workflow/scratch/{YYYYMMDD}-{type}-{slug}/)
index.json must show status: "completed"
.task/ directory must exist with at least one TASK-*.json
If existing retrospective.json found and not --all: emit W002, prompt overwrite

Stage 3: Scan mode -- list all completed phases without retrospective.json. Prompt user to select.

Update plan: Stages 1-3 → completed; Stage 4 → in_progress.

Stage 4: Context-Agent Fork + Parallel Lens Analysis

Step 4a: Spawn context agent

spawn_agent({
  task_name: "ctx",
  fork_turns: "none",
  message: `Load and summarize all phase ${targetPhase} artifacts for retrospective.
    1. Query state.json artifacts[] for phase === ${targetPhase} && milestone === resolve_milestone(${targetPhase}) [D-007 reverse lookup via state.json.milestones[].phase_slugs; fallback to current_milestone if phase unmatched]
    2. Load per-artifact outputs (execute→index/plan/tasks/summaries, verify→verification.json, review→review.json, debug→understanding/evidence, test→uat/tests)
    3. Filter issues.jsonl for this phase; read state.json for project context
    EXPECTED: Goals vs outcomes, completion rates, verification/review/UAT results, issue counts, key metrics`
})
wait_agent({ timeout_ms: 1800000 })

Step 4b: Fork 4 lens agents (only active lenses based on --lens flag; default: all 4)

All lenses use fork_turns: "all" and return the same JSON array schema:

[{ "title": "<80 chars>", "summary": "...", "category": "pattern|antipattern|decision|tool|gotcha|technique",
   "routing": "spec|issue|knowhow|none", "severity": "critical|high|medium|low", "evidence": "<file:line>" }]

Agent	task_name	Focus
Technical	`lens-tech`	Tech debt, architecture decisions, code quality, performance, security, dependencies
Process	`lens-proc`	Planning accuracy, collaboration, workflow efficiency, communication, process improvements
Quality	`lens-qual`	Test coverage gaps, quality gates, UAT failures, review blockers, missing scenarios
Decision	`lens-dec`	Key decisions, tradeoffs, ADR candidates, reversibility, retrospective judgment

// Spawn all 4 lenses in parallel
["lens-tech", "lens-proc", "lens-qual", "lens-dec"].forEach(name =>
  spawn_agent({ task_name: name, fork_turns: "all", message: `<lens-specific prompt>` })
)
const lensResults = wait_agent({ timeout_ms: 1800000 })

// Close lenses first, then context agent LAST
["lens-tech", "lens-proc", "lens-qual", "lens-dec"].forEach(n => close_agent({ target: n }))
close_agent({ target: "ctx" })

If lensResults.timed_out for any agent: emit W001, continue with partial coverage.

Stage 5: Synthesize Insights

spawn_agent({
  task_name: "synthesizer",
  fork_turns: "none",
  message: `Merge and distill insights from 4 lens analyses.
    Input: ${JSON.stringify(lensResults.status)}
    1. Merge all insights, deduplicate (same issue across lenses → keep higher severity, combine evidence)
    2. Generate stable INS-{8hex} id: hash(phase_num + lens + title)
    3. Classify routing: spec | issue | knowhow | none
    4. Produce phase-level metrics summary
    EXPECTED JSON: { insights: [{id,title,summary,category,lens,routing,severity,evidence}],
      metrics: {tasks_completed,tasks_failed,test_pass_rate,review_issues_count,uat_scenarios_passed},
      routing_summary: {spec:N, issue:N, knowhow:N, none:N} }`
})
const synthResult = wait_agent({ timeout_ms: 1800000 })
close_agent({ target: "synthesizer" })

Update plan: Stages 1-5 → completed; Stage 6 → in_progress.

Stage 6: Route Outputs

If --no-route: skip this stage.

For each insight in synthResult.insights, route based on routing field:

Spec routing (routing: "spec"): Map category (pattern/convention → coding, architecture → arch, quality → quality). Append <spec-entry> with category, auto-extracted keywords, date, title, description, source="retrospective", evidence, phase/lens/INS-id.

Issue routing (routing: "issue", severity critical/high): Append to .workflow/issues/issues.jsonl with ISS-<date>-<seq> id, source="retrospective", phase/INS-id context, and history entry.

Memory routing (routing: "knowhow"): Invoke manage-knowhow-capture skill with tip content and --tag retrospective,phase-{N}.

If !AUTO_YES: present routing table and ask confirmation before routing each group.

Stage 7: Write Artifacts

Archive if overwriting: If existing retrospective.{md,json} present, move to {artifact_dir}/.history/ with timestamp suffix before writing new ones.

Write two files to {target_dir}/:

retrospective.json: phase, slug, timestamp, lenses_run, metrics, findings_by_lens, distilled_insights, routing_summary
retrospective.md: Header with phase/slug/timestamp, metrics table (tasks completed, test pass rate, review issues, UAT scenarios), findings by lens, distilled insights, routing summary

Append each insight to .workflow/specs/learnings.md.

If .workflow/specs/learnings.md does not exist, create it with a # Learnings header. Append each insight as <spec-entry> (category=learning, auto-extract keywords, date=today, source=retrospective).

Update plan: Stages 1-7 → completed; Stage 8 → in_progress.

Stage 8: Report

Display summary: phase, lenses run, insight counts (new vs merged duplicates), routing breakdown (spec/issue/knowhow/lesson counts with target paths), key metrics (task completion, test pass rate, review issues).

Next steps: $manage-status, $manage-issue "list --source retrospective", $manage-learn "list --phase <N>", $manage-wiki health, $wiki-digest "<phase-topic>".

<error_codes>

Code	Severity	Description	Stage
E001	error	`.workflow/` not initialized	parse_input
E002	error	Unknown `--lens` name	parse_input
E003	error	`--compare` requires single phase mode	parse_input
E004	error	Phase has no execution artifacts (no .task/)	load_artifacts
E005	error	Phase directory not found or phase not completed	scan_unreviewed
W001	warning	One or more lens agents timed out -- partial coverage	multi_lens_analysis
W002	warning	Existing retrospective.json found -- prompted to overwrite	scan_unreviewed
W003	warning	`manage-knowhow-capture` did not return parseable TIP id; fell back to direct write	route_outputs
W004	warning	`--compare` target phase has no retrospective.json; delta omitted	load_artifacts
</error_codes>

<success_criteria>