444060c3eb
- Introduced `critic`, an independent adversarial reviewer for security and correctness. - Added `fable-orchestrator` to manage task routing and verification. - Implemented `gauntlet-critic` for fresh-context evaluation of gauntlet rounds. - Created `planner` for generating executable implementation plans with dependencies. - Developed `security-auditor` for application security reviews and audits. - Established `system-steward` to improve agent prompts and skills based on verified failures. - Added `dev-loop` skill for autonomous development loops over repositories. - Implemented `gauntlet-loop` skill for iterative quality benchmarking against reference standards. - Updated project settings to utilize the new orchestrator agent. - Created documentation for `GAUNTLET.md`, `PROGRESS.md`, and `REFERENCE_BAR.md` to track project status and quality benchmarks. - Added detailed prompting style guide to enhance understanding of prompt patterns and agentic loops.
5.1 KiB
Project subagents
The project-level Claude Code subagents live in ./agents/. They are intentionally few and have distinct ownership:
| Agent | Purpose | Write access | Default model |
|---|---|---|---|
fable-orchestrator |
frames, routes, and accepts verified work | no | Fable |
scout |
maps code and constraints | no | Haiku |
planner |
produces a minimal testable plan | no | Opus |
builder |
implements a named, scoped change | yes | Sonnet |
lexai-extension-dev |
LexAI-specific implementation (entrypoints, LLM proxy, key handling, selection/replace, Gitea/CWS release) | yes | Sonnet |
ux-ui-designer |
design specs before user-facing builds; reviews after | docs/DESIGN_SYSTEM.md + docs/design/** only |
Sonnet |
ux-psychologist |
behavioral-psychology audit of implemented flows; dark-pattern screen | no (findings only) | Sonnet |
verifier |
independently checks acceptance tests | no direct file tools | Haiku |
critic |
adversarial review for high-risk work | no direct file tools | Opus |
gauntlet-critic |
referees gauntlet rounds: real artifact vs reference bar, fresh eyes every round | no (verdict and gap only) | Opus |
security-auditor |
authn/authz, secrets, injection, deps, attack surface | docs/attacksurface.md only |
Opus |
learning-steward |
turns proven mistakes into guardrails/evals | only lesson and eval artifacts | Haiku |
system-steward |
improves agents, skills, and role memory from evidence | operating artifacts only | Opus |
integrator |
combines independent named changes | yes | Sonnet |
Use
Run Fable as the main session when the work needs coordination:
claude --agent fable-orchestrator
fable, opus, sonnet, and haiku are version-flexible Claude Code aliases. They resolve to the newest enabled version for the current provider and account; this avoids leaving the project pinned to an obsolete model ID.
For a one-off specialist, invoke it in a normal Claude Code session, for example:
@scout Map the code paths and tests relevant to [task]. Do not modify files.
@builder Implement the approved task contract for [task] in [paths].
@lexai-extension-dev Implement [task] in entrypoints/ respecting the message contract and key-handling rules.
@verifier Verify [task] against these acceptance tests: [tests].
@security-auditor Audit [change/component] for authz, injection, secrets, and attack-surface exposure.
@gauntlet-critic Referee [part] against docs/REFERENCE_BAR.md. Inspect the artifact only; return verdict, biggest gap, evidence, stop signal.
@learning-steward Review this verified failure and decide the smallest durable prevention.
@system-steward Improve the relevant project agent or skill only from this evidence: [evidence].
For LexAI code (anything under entrypoints/ or src/), prefer lexai-extension-dev over the generic builder — it knows the message contract, snapshot pattern, and key-handling rules. Use builder for repo-agnostic changes (config, tooling, docs). Use no more than one implementer on the same files. For low-risk, isolated work, use a normal Claude Code session instead of adding coordination overhead. When a unit waits on an owner decision, park only that unit (docs/PROGRESS.md → Waiting on you) and keep independent lanes moving — at most one agent idles on an answer.
Memory and skills
Fable, Planner, Builder, UX/UI Designer, UX Psychologist, Verifier, Critic, Learning Steward, Integrator, and System Steward use project-scoped role memory. It is committed under .claude/agent-memory/ when Claude Code creates it, so the team can review it. Fable also uses Claude Code Auto Memory for session continuity. Shared durable knowledge lives in docs/MEMORY.md (see the memory protocol in CLAUDE.md); role memory stays role-specific. gauntlet-critic is deliberately stateless — no role memory — so every round gets genuinely fresh eyes; durable gauntlet lessons belong to the Learning Steward and docs/GAUNTLET.md, never to the referee.
/resume-projectrebuilds verified working state after a new session, interruption, or compaction./memory-syncconsolidates durable knowledge intodocs/MEMORY.md, dedupes, and enforces context caps (owner: Learning Steward)./design-specand/design-reviewbracket every user-facing change (owner: UX/UI Designer)./ux-psych-auditevaluates implemented journeys through behavioral-psychology lenses — friction, motivation, framing, trust (owner: UX Psychologist)./continuous-improvementevaluates a proven workflow failure and sends agent/skill improvements to System Steward only when justified./dev-loopruns a bounded autonomous maintenance loop (triage → one bounded task → full landing gates → clean stop)./gauntlet-loopruns reference-benchmarked improvement rounds (concrete bar → build → fresh-eyes referee → close the single biggest gap → repeat until parity, diminishing returns, or budget)./attack-surfaceand/prompt-injection-auditkeep security coverage current;/self-model-auditkeeps the operator/project model honest.