project-hub
Interactive project hub — workflows, agent pipelines, and architecture graphs
Agent Pipeline
Agents own the process (decisions, planning, review, maintenance). Claude Code plan mode owns execution (implementing tickets).
Architect
Asks clarifying questions and explores alternatives before any code is written. Produces Architecture Decision Records (ADRs) and detailed specs.
System Architect
Identifies components, connections, protocols, and tiers. Produces a structured architecture.yaml that documents how the system fits together.
Planner
Takes ADRs and specs as input. Decomposes work into discrete tickets scoped for a single Claude Code plan mode session.
Plan Mode
Not a custom agent — this is Claude Code's native plan mode (shift+tab). It explores the codebase, proposes a plan, gets approval, then implements. Each ticket from the Planner is executed as a separate plan mode session.
Executor (fallback)
Fallback for when plan mode is unavailable or when enforced verification discipline is needed. Most tickets should use plan mode instead.
QA Tester
Writes automated tests after implementation. Covers acceptance criteria, edge cases, and regression scenarios.
Reviewer
Validates code and tests against the original acceptance criteria. Flags issues back for fixing and provides final approval.
Custodian
Maintains the project's CLAUDE.md file — adds new patterns and gotchas, removes stale entries, and routes large content to external files. Enforces a 150–200 line limit.
Summarizer
Reads tickets, ADRs, specs, git history, and test results to produce concise, non-technical executive summaries.
System Architecture
One-line description of the system
Component Name
clientWhat this component does
Main technology used