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,11 @@
---
name: resume-project
description: Rebuild verified project state after a fresh session, compaction, interruption, agent handoff, or a request to continue or resume work. Use proactively before planning or editing when conversation history may be incomplete.
allowed-tools: Read Grep Glob
---
1. Read `CLAUDE.md`, `docs/MEMORY.md`, `docs/HANDOFF.md`, `docs/PROJECT_BRIEF.md` when present, and the active rules under `## Lessons`.
2. Inspect the current git status and only the files named by the handoff or current task.
3. Separate verified facts from stale or unverified handoff claims. Re-run the smallest relevant check if the status is uncertain.
4. Return a state snapshot: objective, verified progress, changed paths, verification status, open risks, and one next smallest action.
5. Update `docs/HANDOFF.md` only when new evidence changes the state. Do not implement the next action unless the user or task explicitly asks.