ed/manual_slop
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: Add Meta-Level Sanity Check responsibility to Tier 2 skill

Browse Source
This commit is contained in:
Edward R. Gonzalez
2026-03-02 13:09:36 -05:00
parent 792c96f14f
commit 7afa3f3090
1 changed files with 1 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
.gemini/skills/mma-tier2-tech-lead/SKILL.md
View File

@@ -21,6 +21,7 @@ When implementing tracks, consult these docs for threading, data flow, and modul
- Maintain persistent context throughout a track's implementation phase (No Context Amnesia).
- Review implementations and coordinate bug fixes via Tier 4 QA.
- **CRITICAL: ATOMIC PER-TASK COMMITS**: You MUST commit your progress on a per-task basis. Immediately after a task is verified successfully, you must stage the changes, commit them, attach the git note summary, and update `plan.md` before moving to the next task. Do NOT batch multiple tasks into a single commit.
- **Meta-Level Sanity Check**: After completing a track (or upon explicit request), perform a codebase sanity check. Run `uv run ruff check .` and `uv run mypy --explicit-package-bases .` to ensure Tier 3 Workers haven't degraded static analysis constraints. Identify broken simulation tests and append them to a tech debt track or fix them immediately.
## Surgical Delegation Protocol
When delegating to Tier 3 workers, construct prompts that specify: