arch-pipeline

Architecture Documentation Pipeline

Run the complete ADR → HLD(s) → LLD(s) pipeline with context isolation, state persistence, quality audits, and context-clearing prompts. Each phase (discuss, research, gather, generate, audit) runs in its own forked context. The orchestrator tracks file paths, decisions, and verdicts — it never reads document content.

One ADR can produce multiple HLDs (one per subsystem), and each HLD can produce multiple LLDs (one per component). Single-document is the default — fan-out is opt-in.

Input

$ARGUMENTS — the decision topic (e.g., "migrate from REST to GraphQL") or --resume to continue from saved state.

Pipeline Overview

Phase 1:   ADR Discuss     → decisions file
Phase 2:   ADR Research    → RESEARCH.md
Phase 3:   ADR Gather      → context file (compiles from 1+2)
Phase 4:   ADR Generate    → ADR document
Phase 5:   ADR Audit       → audit report

CHECKPOINT — HLD Scoping + Context Clear Prompt

FOR EACH HLD [i]:
  Phase 6-i:  HLD Discuss   → decisions file
  Phase 7-i:  HLD Research  → RESEARCH.md
  Phase 8-i:  HLD Gather    → context file
  Phase 9-i:  HLD Generate  → HLD document
  Phase 10-i: HLD Audit     → audit report

  CHECKPOINT — LLD Scoping + Context Clear Prompt

  FOR EACH LLD [j]:
    Phase 11-i-j: LLD Discuss   → decisions file
    Phase 12-i-j: LLD Research  → RESEARCH.md
    Phase 13-i-j: LLD Gather    → context file
    Phase 14-i-j: LLD Generate  → LLD document
    Phase 15-i-j: LLD Audit     → audit report

Pipeline Complete — tree summary + implement option

Every phase skill runs with context: fork — the orchestrator stays lean, tracking only file paths, decisions, and verdicts.

Process

State Tracking

Maintain these variables throughout the pipeline:

ADR (single):

• $ADR_DECISIONS_PATH — decisions file from discuss
• $ADR_RESEARCH_PATH — research file
• $ADR_CONTEXT_PATH — compiled context file
• $ADR_PATH — generated ADR document
• $ADR_AUDIT_VERDICT — PASS / PASS WITH WARNINGS / FAIL