/erpaval

name: erpaval
description: >
  Workflow for autonomous software development with Claude Code.
  Classifiers route scope, complexity, directory state, and spec readiness
  before committing to Explore / Research / Plan / Act / Validate, then
  close the loop with a Compound step that persists lessons to
  `.erpaval/solutions/` for future sessions. Optional HMW reframing and EARS
  specification add structured rigor — Claude judges when to run them. Each
  Act subagent edits its own Markdown task packet section-by-section per the
  write protocol, and the orchestrator monitors with `wc -l`. Use when the
  user asks to implement a feature autonomously, build with agents, use
  ERPAVal, plan and execute a coding task, delegate to subagents, do
  agent-driven development, extract lessons, recall prior lessons, or
  mentions autonomous coding workflow or compound engineering.

Contents

| Reference | When to load | | ----------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- | | `references/flow.md` | The graph — intake, build loop, validate/compound, cycles | | `references/classifiers.md` | Prompt text for each `CL-*` classifier | | `references/fan-out.md` | Per-phase subagent counts + the one-message parallel-launch rule | | `references/glossary.md` | `CP-*`, `CL-*`, gates, cycles, zones, placeholder tokens | | `${CLAUDE_PLUGIN_ROOT}/skills/product-discovery/references/roles/hmw-framer.md` | HMW substep (hard-dep on `product-discovery`; run when `CL-RIGOR` asks for HMW) | | `${CLAUDE_PLUGIN_ROOT}/skills/product-discovery/references/roles/ears-specifier.md` | EARS substep (hard-dep on `product-discovery`; run when `CL-RIGOR` asks for EARS) | | `references/orchestrator.md` | Per-phase runbook — Task-tool lifecycle, Agent patterns | | `references/context-packets.md` | Per-packet YAML schemas + two-gate review + auto-merge rules | | `references/write-protocol.md` | Canonical write-protocol block (copied into every Act prompt) | | `references/validation-playbook.md` | 3-layer validation + closed-loop toolchain | | `references/compound.md` | Dual-track lesson schema + recall retrieval algorithm | | `templates/session/worklog-skeleton.md` | Per-task packet skeleton with embedded write protocol | | `templates/session/` | YAML schemas the orchestrator seeds into `.erpaval/sessions/<id>/` at runtime | | `templates/specs/` | EARS spec and task-list skeletons for the Framing substep | | `templates/solutions/` | Lesson templates (bug, knowledge) the Compound phase writes from | | `templates/brainstorms/` | HMW requirement skeletons for the Framing substep | | `templates/INDEX.md` | Recall-phase index of lessons by category, read at session start |

ERPAVal — adaptive autonomous software development

A six-phase workflow with two framing substeps and a compounding tail. The orchestrator (main Claude Code session) runs classifiers to decide which phases apply, delegates implementation to subagents, and persists Markdown + YAML packets under `.erpaval/` so future sessions start smarter than this one.

The graph at a glance

flowchart LR
  IN[Intake + Recall bootstrap] --> SCOPE{Scope?}
  SCOPE -->|coding| COMPLEX{Complexity?}
  SCOPE -->|non-coding| ROUTE[Upstream skill]
  COMPLEX -->|1-file fix| DIRECT[Direct fix]
  COMPLEX -->|multi-module or rebuild| RESUME{New or resume?}
  RESUME -->|new| NEW[erpaval-new.py]
  RESUME -->|resume| PRIOR[Load prior session]
  NEW --> DIR{Dir state?}
  PRIOR --> DIR
  DIR --> RIGOR{Rigor?}
  RIGOR -.->|fuzzy| HMW[HMW frame]
  RIGOR -.->|contract unclear| EARS[EARS spec]
  HMW --> EARS
  EARS --> ER[Explore + Research]
  RIGOR -->|crisp| ER
  ER --> PLAN[Plan]
  PLAN --> G1{Gate 1}
  G1 -.->|revise| PLAN
  G1 -->|approved| ACT[Act · waves]
  ACT --> VAL[Validate]
  VAL -.->|fail| ACT
  VAL -->|pass| G2{Gate 2}
  G2 --> MERGE[Merge]
  MERGE --> COMP[Compound · extract lessons]
  COMP --> DONE([Done])

Full three-view graph with every cycle is in `references/flow.md`. Dashed edges are named cycles.

Strict phase gating via TaskCreate / TaskUpdate / TaskList

Each phase has a completion gate enforced by the `TaskCreate` / `TaskUpdate` / `TaskList` todo-list tool family (distinct from the `Agent` subagent-launcher). Every implementation task is wired with `addBlockedBy` so the task system itself prevents out-of-order execution. No skipping, no parallel execution across gates, no early starts.

The todo-list tools hold authoritative state. YAML packets under `.erpaval/sessions/` are read-onl