feat(agents): add analysis paralysis guard, exhaustive cross-check, and task-level TDD (#736)
- gsd-executor: Add <analysis_paralysis_guard> block after deviation_rules. If executor makes 5+ consecutive Read/Grep/Glob calls without any Edit/Write/Bash action, it must stop and either write or report blocked. Prevents infinite analysis loops that stall execution. - gsd-plan-checker: Add exhaustive cross-check in Step 4 requirement coverage. Checker now also reads PROJECT.md requirements (not just phase goal) to verify no relevant requirement is silently dropped. Unmapped requirements become automatic blockers listed explicitly in issues. - gsd-planner: Add task-level TDD guidance alongside existing TDD Detection. For code-producing tasks in standard plans, tdd="true" + <behavior> block makes test expectations explicit before implementation. Complements the existing dedicated TDD plan approach — both can coexist. Co-authored-by: CyPack <GITHUB_EMAIL_ADRESIN> Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -171,6 +171,16 @@ Track auto-fix attempts per task. After 3 auto-fix attempts on a single task:
|
||||
- Do NOT restart the build to find more issues
|
||||
</deviation_rules>
|
||||
|
||||
<analysis_paralysis_guard>
|
||||
**During task execution, if you make 5+ consecutive Read/Grep/Glob calls without any Edit/Write/Bash action:**
|
||||
|
||||
STOP. State in one sentence why you haven't written anything yet. Then either:
|
||||
1. Write code (you have enough context), or
|
||||
2. Report "blocked" with the specific missing information.
|
||||
|
||||
Do NOT continue reading. Analysis without action is a stuck signal.
|
||||
</analysis_paralysis_guard>
|
||||
|
||||
<authentication_gates>
|
||||
**Auth errors during `type="auto"` execution are gates, not failures.**
|
||||
|
||||
|
||||
Reference in New Issue
Block a user