القائمة
Test-driven implementation flow for one TASKS.md item — load, red, green, refactor, verify, archive — driving the six-status vocabulary. Use when picking up any pending task.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Create or upgrade a self-improving Claude Code harness in the current project — self-healing failure ledger, per-file lesson memory, regression evals, small-model elevation agents, deterministic safety hooks. Modes: (no args) auto-detect new vs upgrade; 'doctor' = validate only. Evidence-gated: scan, propose plan, confirm, apply, verify.
Self-maintenance pass over the .claude/ harness itself: validate every mechanical invariant, detect drift and dead weight, and propose upgrades. Run periodically, after any harness change, or via /loop.
Run one iteration of this project's maintenance loop: finish in-flight work, convert failures into lessons, checkpoint hygiene, audit the harness, or start the next pending task — whichever is highest-value right now. Also the remedy when capability-gate.sh blocks a source edit because maintenance is overdue.
Remove dead code, unused dependencies, commented-out blocks, and orphaned files once a checkpoint is reached — for long-term maintainability. Evidence-gated and reversible: nothing is removed without proof it is unreferenced, and build+tests must stay green after every batch. Run after a milestone/feature completes, not mid-implementation.
Convert this session's failures and user corrections into durable per-file lessons in .claude/memory/lessons/, following the evidence-backed write policy (retrieve-similar-first, delta updates, weighted vote lifecycle, hook promotion). Run at the end of any session that contained a correction or a repeated failure.
Holistic, single-pass senior-engineer review of the target project's actual code (not the harness) across security, performance, code quality, and production-readiness. Use for 'is this ready to ship', a full code review, a security audit, or a performance pass.
| name | milestone-task |
| description | Test-driven implementation flow for one TASKS.md item — load, red, green, refactor, verify, archive — driving the six-status vocabulary. Use when picking up any pending task. |
| argument-hint | [task id, e.g. #001] |
Work exactly one TASKS.md item ($ARGUMENTS) through pending → running → completed (or → needs-fix/→ broken if something goes wrong).
TASKS.md entry (Status/Files/Notes) and any spec it references.running in TASKS.md before starting.TASKS.md — don't silently scope-creep..claude/harness.env; all must pass..claude/rules/ship-verification.md — actually run the behavior end-to-end, not just unit tests, if it touches a runtime path.ARCHIVE.md with a Completed: date and how it was verified; set its status.json entry to completed.If you hit a wall (spec unclear, design needs revisiting), stop and flag it — flip status to needs-fix with a note, never leave it silently running.