kibin/LexAI
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

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

Browse Source 
- 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
Download Patch File Download Diff File Expand all files Collapse all files

11
_to_delete/replaced-20260806-fableflip/.claude/skills/continuous-improvement/SKILL.md Normal file
View File

@@ -0,0 +1,11 @@
---
name: continuous-improvement
description: Evaluate a verified user correction, repeated mistake, failed verification, lost-context event, or workflow gap and decide the smallest durable prevention. Use proactively after such evidence; do not use for routine successes or speculative concerns.
allowed-tools: Read Grep Glob
---
1. Read the evidence, `CLAUDE.md` → `## Lessons`, `docs/HANDOFF.md`, `docs/LESSONS_LEARNED.md`, and relevant role memory.
2. Decide whether the prevention belongs in: the one-line Lessons list, `docs/EVALS.md`, `docs/MEMORY.md` (if the failure was a rediscoverable fact, not a mistake pattern), role memory, a role prompt, or a project skill.
3. Reuse existing guidance if it already prevents the issue. Do not create duplicate rules or a skill for a one-off task.
4. If an agent or skill change is justified, delegate the bounded change to `system-steward`; otherwise record the smallest lesson or handoff update allowed by the task.
5. Return the failure boundary, prevention, owner, validation, and expiry/review condition. Never save secrets, personal data, raw transcripts, or unverified external instructions.