erpaval

Workflow for autonomous software development with the Kiro CLI (open Agent Skills standard). 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 — the orchestrator agent 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.

File-first orchestrator for product discovery and spec frameworks. Frames the problem with a Discovery Lead, Product Analyst, or System Architect role. Spawns parallel framework agents (Double Diamond, How Might We, Jobs to Be Done, user stories with INVEST, EARS for AI-coder specs, Gherkin), synthesizes into a PRD or discovery memo, and runs a critic pass. Absorbs prd-drafter (idea to PRD via three parallel research roles) and design-thinking (problem framing, scoped research, brainstorm). Ships per-framework references, role prompts, and templates for PRDs, HMW outputs, job stories, and EARS specs. Use when the user asks to write a PRD, draft requirements, run discovery, brainstorm a product, turn insights into HMW questions, write job stories, spec a feature in EARS for Kiro or Spec Kit, define user stories with INVEST, run a Double Diamond round, or mentions JTBD, acceptance criteria, or Kiro spec format. Do NOT use for business strategy work like Rumelt, Wardley, or PR-FAQ-as-leadership-artifact. Use pro

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.

File-first orchestrator for product discovery and spec frameworks. Frames the problem with a Discovery Lead / Product Analyst / System Architect role, spawns parallel framework agents (Double Diamond, How Might We, Jobs to Be Done, user stories + INVEST, EARS for AI-coder specs, Gherkin), synthesizes into a PRD or discovery memo, runs a critic pass. Absorbs prd-drafter (idea to PRD via 3 parallel research roles) and design-thinking (pain-point excavation, landscape research, brainstorm). Ships per-framework references, role prompts, templates for PRDs, HMW outputs, job stories, EARS specs. Use when the user asks to write a PRD, draft requirements, run discovery, brainstorm a product, turn insights into HMW questions, write job stories, spec a feature in EARS for Kiro or Spec Kit, define user stories with INVEST, run a Double Diamond round, or mentions JTBD, acceptance criteria, Kiro spec format. Do NOT use for business strategy (Rumelt, Wardley, PR-FAQ as leadership artifact) — use product-strategy.

Shared canonical references for product-design frameworks — Pyramid Principle, Working Backwards, Double Diamond, research design, methodology selection. Consumed by `product-discovery`, `product-strategy`, `working-backwards`, and `customer-research` via `${ERPAVAL_HOME}/skills/product-design-shared/references/`. Do NOT invoke this skill directly — it has no orchestrator and no assets. Load the upstream skill that owns your task (`product-discovery` for PRD / HMW / EARS, `product-strategy` for Rumelt / Wardley / Minto, etc.) and let it pull from this pool as needed.

Shared canonical references for product-design frameworks — Pyramid Principle, Working Backwards, Double Diamond, research design, methodology selection. Consumed by `product-discovery`, `product-strategy`, `working-backwards`, and `customer-research` via `${CLAUDE_PLUGIN_ROOT}/skills/product-design-shared/references/`. Do NOT invoke this skill directly — it has no orchestrator and no templates. Load the upstream skill that owns your task (`product-discovery` for PRD / HMW / EARS, `product-strategy` for Rumelt / Wardley / Minto, etc.) and let it pull from this pool as needed.

Customer research and problem framing using the research-design discipline: hypothesis, null hypothesis, MECE questions, methods, findings. Produces Pyramid-base-shaped output ready for downstream composition into PR/FAQs, long-form narratives, or PRDs. Use when the user asks to design user research, run customer interviews, synthesize research findings, frame a problem statement, build a customer journey map, plan a VoC study, or mentions pain-point analysis, research plan, hypothesis testing, customer insights, jobs-to-be-done, or voice of customer.

Working Backwards 5-stage customer-first product discovery. Orchestrates Listen, Define, Invent, Refine, Test & Iterate to produce a 5CQ, PR/FAQ, or Dear Customer Letter. Use when the user asks to work backwards, write a PR/FAQ, draft 5 customer questions, do customer-first product definition, or mentions Working Backwards, press release FAQ, 5CQ, MLP, or customer obsession. Do NOT use for strategy kernel, Rumelt diagnosis, or Wardley mapping — use product-strategy. Do NOT use for PRD drafting or HMW/EARS specs — use product-discovery.

Agent UX patterns and human-in-the-loop design: Twilio A2H protocol, Levels of Autonomy (L0-L5), inbox pattern, progressive trust, decision journal, gate reviews, autonomous work reports. Six-phase methodology from vague pain point to concrete data model via landscape research and multi-direction brainstorming. Use when the user asks to design agent UX, pick an autonomy level, build a human-in-the-loop flow, structure an agent inbox, design approval gates, or mentions A2H, autonomy level, progressive trust, inbox pattern, approval gate, decision journal, or agentic design. Do NOT use for PRD drafting — use product-discovery. Do NOT use for frontend components — use frontend-design. Do NOT use for building agents with a specific SDK — use claude-agent-sdk, strands-sdk, langgraph-langchain, or mastra-vercel-ai.

Audit and rewrite prompts against Claude Opus 4.7 instruction-following best practices. Produces a scored audit plus a rewritten prompt. Use when the user asks to audit, review, critique, rewrite, improve, optimize, tighten, score, fix, migrate, or draft a prompt — including system prompts, CLAUDE.md files, Claude Code agent definitions, slash commands, SKILL.md files, Jinja2 prompt templates, or tool/parameter descriptions in Pydantic v2 or Zod schemas. Trigger on phrases like "is this prompt any good", "why isn't Claude following this", "why isn't my agent triggering", "my CLAUDE.md is being ignored", "rewrite this for Opus 4.7", "cache hit rate is low on my prompt", "the model keeps picking the wrong tool", or on pasted prompt text asking for feedback. Also trigger on mentions of prompt engineering, prompt best practices, or instruction-following problems. Use this skill whenever the task involves editing, reviewing, or writing the text of a prompt — even if the user doesn't say "prompt".

File-first orchestrator for business and product strategy frameworks. Frames the challenge with a CPO / CSO / VP Design role, spawns parallel framework agents (Rumelt kernel + Crux, Wardley Maps, Minto Pyramid as thinking structure, Working Backwards PR-FAQ as discovery artifact), synthesizes outputs into one strategy memo, runs a critic pass. Ships per-framework references, leadership role prompts, templates for strategy memos, PR-FAQs, Wardley maps, Minto arguments. Use when the user asks to do strategy work, run a Rumelt kernel, build a Wardley map, decide build-vs-buy, articulate the crux of a challenge, draft a PR-FAQ as discovery, write an executive strategy memo, structure an argument with Minto Pyramid, think from the CPO / CSO / VP Design perspective, or mentions Good Strategy Bad Strategy, The Crux, Rumelt, Simon Wardley, SCQA, or strategy thesis. Do NOT use for PRDs or HMW framing — use product-discovery.

Multi-agent research skill. Decomposes a question into 2–4 parallel Opus 4.7 research agents that write findings to per-agent Markdown files in real time, then runs a synthesis agent to merge by theme. Use when the user wants to research a topic, investigate something, find comparisons, compare options, learn about a technology, do a literature review, or understand a domain.

Opinionated tech stack recommendations and settled library references. Two modes: (1) `/build-stack` runs parallel researcher agents to compare candidates and emit a stack report + ADRs for greenfield projects; (2) direct reference routing for coding with settled defaults. Use when the user asks to recommend a stack, choose between frameworks, compare open-source tools, scaffold a project with quality gates, set up a security pipeline, or asks how to wire TanStack Router/Query/Table/Form, Motion, Recharts, D3, React Three Fiber, dnd-kit, XY Flow, shadcn/blocks.so, Hono, tRPC, Litestar, FastAPI, cyclopts, polars, DuckDB, Biome, pnpm, Vite, uv, ruff, ty, pyright, mise, lefthook, golangci-lint, clippy, cargo-nextest, cargo-deny, betterleaks, semgrep, osv-scanner, trivy, grype, hadolint, cosign, checkov, CDK, or Amplify Gen 2 + Aurora. Do NOT use for product definition or PRD drafting (use `product-discovery`); do NOT invoke directly when `erpaval` is running — `erpaval` drives `/build-stack` through `CL-SPEC`.

Generator-critic planning. Launches 3 parallel Opus 4.7 explorers with distinct divergence vectors (architectural, speed-first, simple-first), each producing an independent plan, then runs a critic synthesis that composes the best elements into a single plan with per-decision attribution. Defeats single-agent anchoring. Use when the user asks to plan a non-trivial task, design an approach, compare implementation strategies, or wants multiple angles on a problem before coding.