docs: Enforce strict atomic per-task commits for Tier 2 agents

This commit is contained in:
2026-03-02 12:52:04 -05:00
parent ff7f18b2ef
commit b4de62f2e7
2 changed files with 2 additions and 0 deletions

View File

@@ -20,6 +20,7 @@ When implementing tracks, consult these docs for threading, data flow, and modul
- Break down tasks into specific technical steps for Tier 3 Workers.
- 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.
## Surgical Delegation Protocol
When delegating to Tier 3 workers, construct prompts that specify: