Add new agents and skills for enhanced project orchestration and review processes

- 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.
This commit is contained in:
john kevin asprec
2026-08-08 16:49:07 +08:00
parent 6aee260533
commit 444060c3eb
85 changed files with 2717 additions and 171 deletions

View File

@@ -0,0 +1,13 @@
---
name: self-model-audit
description: Compare what the harness believes about the operator and project (docs/SELF_MODEL.md, CLAUDE.md, role memory) against what recent work and corrections actually reveal, and propose edits that close the gap. Use periodically or after repeated "that's not what I meant" signals.
allowed-tools: Read Grep Glob
---
Find where the harness is modeling a stale, aspirational, or simply wrong version of the operator or the project — then propose the smallest edits that make the model match reality. Read-only: propose changes, don't apply them without approval.
1. **Read the belief set.** `docs/SELF_MODEL.md`, `docs/PROJECT_BRIEF.md`, the operator/project instructions in `CLAUDE.md`, active `## Lessons`, and relevant role memory. Note every claim the system holds about who the operator is, what they want, and how they work.
2. **Read the evidence.** Recent handoffs (`docs/HANDOFF.md`), recorded decisions (`docs/DECISIONS.md`), corrections captured in `LESSONS_LEARNED.md`, and the shape of recent tasks. Infer what the operator's actual behavior and choices reveal.
3. **Find the gaps.** Flag each place the stated model conflicts with revealed behavior: preferences that changed, aspirational goals the system optimizes for but recent work contradicts, assumptions never re-confirmed, and voice/style drift. Distinguish "genuinely stale" from "reasonable disagreement" — do not pathologize a deliberate choice.
4. **Propose edits.** For each gap, give the exact `SELF_MODEL.md` (or `CLAUDE.md` instruction) change that closes it, tied to the evidence that justifies it. Prefer removing an over-specific belief over adding more.
5. **Return** the gap list (belief → contradicting evidence → proposed edit), and route any accepted change through the operator or `system-steward`. Never infer a sensitive attribute, and never store credentials, financial/health data, or anything the operator hasn't agreed to persist.