Aphelion Wiki
Language: English | 日本語 Last updated: 2026-05-16 Update history:
- 2026-05-16: Bump agent count 40 → 42 for analyst split (analyst-intake + analyst-core) (#139)
- 2026-05-12: Bump rule count 13 → 14 for document-locations rule (#117)
- 2026-05-01: Add Hooks-Reference link, bump rule count 12 → 13 (#107)
- 2026-05-01: Bump agent count 39 → 40 for visual-designer (#109)
- 2026-04-30: Bump rule count 9 → 12 (#103)
- 2026-04-30: Add Agents-Doc.md to Agents Reference (5→6 pages), Doc Flow to glossary (#54)
- 2026-04-25: link targets refreshed for Architecture / Agents-Reference page splits, #42 Audience: All users
Welcome to the Aphelion Wiki — the detailed reference for the Aphelion Claude Code agent workflow.
Not sure where to start? → Getting Started
What is This Wiki?
Section titled “What is This Wiki?”Aphelion’s README covers the quick start and an overview. This wiki provides the in-depth reference material that the README intentionally omits:
| README | Wiki |
|---|---|
| Project overview and motivation | Architecture: Domain Model: 3-domain model and session isolation |
| Quick Start commands | Getting Started: Claude Code setup, first-run walkthrough, scenarios, troubleshooting |
| Triage plan table (summary) | Triage System: selection logic, conditions, and agent matrices |
| Agent list (names only) | Agents Reference (split by domain): Orchestrators & Cross-Cutting, Discovery, Delivery, Operations, Maintenance, Doc — all 42 agents with inputs, outputs, NEXT conditions |
| — | Rules Reference: 14 behavior rules with scope and customization notes |
| — | Hooks Reference: Claude Code hooks distributed by Aphelion (MVP 3 hooks) |
| — | Contributing: how to add agents, rules, and maintain the wiki |
Table of Contents
Section titled “Table of Contents”Core Pages
Section titled “Core Pages”| Page | Description | Primary Audience |
|---|---|---|
| Getting Started | Claude Code setup, first run, usage scenarios, command reference | New users |
| Architecture (3 pages) | Domain Model, Protocols, Operational Rules — 3-domain model, handoff files, AGENT_RESULT protocol, runtime rules | Agent developers |
| Triage System | 4-tier plan selection logic, per-domain agent matrices, mandatory agents | All users |
| Agents Reference (6 pages) | Orchestrators & Cross-Cutting, Discovery, Delivery, Operations, Maintenance, Doc — all 42 agents | Agent developers |
| Rules Reference | All 14 behavior rules: scope, auto-load, interactions | Agent developers |
| Hooks Reference | Aphelion hooks: usage, bypass, disable, customisation | All users |
| Contributing | Adding agents, rules; bilingual sync workflow | Agent developers |
Persona-Based Entry Points
Section titled “Persona-Based Entry Points””I want to use Aphelion for the first time”
Section titled “”I want to use Aphelion for the first time””- Read Getting Started — Quick Start for your platform
- Run
/discovery-flow - Read Triage System to understand which agents will be launched
”I want to understand how Aphelion works internally”
Section titled “”I want to understand how Aphelion works internally””- Read Architecture → Domain Model — domain model and session isolation
- Read Architecture → Protocols — handoff files and AGENT_RESULT
- Read Agents Reference → Orchestrators and the 5 domain pages — each agent’s responsibility and connections
- Read Rules Reference — behavioral constraints applied to all agents
”I want to add a new agent or rule”
Section titled “”I want to add a new agent or rule””- Read Contributing — file templates and AGENT_RESULT contract
- Read Architecture → Domain Model — understand where the new agent fits
- Read Rules Reference — understand which rules apply automatically
”I need to fix a bug or add a small feature to an existing project”
Section titled “”I need to fix a bug or add a small feature to an existing project””- Ensure your project has
SPEC.mdandARCHITECTURE.md(if missing, run/codebase-analyzerfirst) - Run
/maintenance-flow {trigger description}— the orchestrator will triage into Patch / Minor / Major - Read Triage System → Maintenance Flow Triage for details on what each plan includes
Glossary
Section titled “Glossary”| Term | Definition |
|---|---|
| Domain | One of the three primary workflow scopes (Discovery, Delivery, Operations). Maintenance is a fourth independent flow; Doc is a fifth, on-demand flow for customer-deliverable document generation |
| Flow orchestrator | An agent that manages an entire flow (discovery-flow, delivery-flow, operations-flow, maintenance-flow, doc-flow) |
| Triage | The process of assessing project scale at flow start and selecting a plan tier |
| Plan | One of four execution tiers: Minimal / Light / Standard / Full |
| Handoff file | A .md file used to pass information between domains (DISCOVERY_RESULT.md, DELIVERY_RESULT.md) |
| AGENT_RESULT | The structured output block every agent emits upon completion |
| NEXT | The field in AGENT_RESULT that specifies which agent runs next |
| STATUS | The completion status field: success / error / failure / suspended / blocked |
| blocked | STATUS used when an agent cannot continue due to design ambiguity |
| Canonical source | .claude/ — the authoritative definition files for Claude Code |
| PRODUCT_TYPE | Classification of the project artifact: service / tool / library / cli |
| HAS_UI | Whether the project includes a user interface (affects which agents run) |
| Auto-approve mode | Mode activated by .aphelion-auto-approve file; skips approval gates for automated evaluation |
| Maintenance Flow | Fourth flow independent from the 3-domain pipeline; invoked via /maintenance-flow for existing-project maintenance (bugs, CVEs, refactors, small features). Triage: Patch / Minor / Major |
| MAINTENANCE_RESULT.md | Handoff file generated only on Major plan; passed to Delivery Flow as a pre-processing stage |
| Doc Flow | Fifth flow, on-demand; invoked via /doc-flow to generate customer-deliverable documents (HLD, LLD, API reference, ops manual, user manual, handover). Triage: doc-type count (1–2 → Minimal, 3–4 → Light, 5–6 → Standard, all 6 + verify → Full). No automatic chaining |
| DOC_FLOW_RESULT.md | Final output of Doc Flow; lists generated deliverables, skipped types, and next steps |
Related Pages
Section titled “Related Pages”Canonical Sources
Section titled “Canonical Sources”- .claude/rules/aphelion-overview.md — Aphelion workflow overview (auto-loaded)
- README.md — Project entry point