873 B
873 B
Logging Patterns
Agent Output Standards
Subagents must return actionable results, not status recaps:
| Agent | Expected Output |
|---|---|
| Explorer | File maps, edit points, dependency chains |
| Researcher | Specific findings, code patterns, API details |
| Tester | Test results with pass/fail counts and specific failures |
| Reviewer | Structured verdict with findings and resolution status |
Recording Discipline
Memory files preserve knowledge, not activity logs:
- ✅ Record: outcomes, decisions, discoveries, patterns
- ❌ Don't record: phase transitions, status changes, ceremony checkpoints
Verdict Tracking
All reviewer/tester findings must be tracked to resolution:
- Status flow:
OPEN → ASSIGNED → RESOLVED | WONTFIX - Findings must not be silently dropped
- Include unresolved findings in coder re-dispatch