Add plan format validator hook to detect malformed task labels

- Strengthen Prometheus plan template with FORMAT constraint
- Add task label format check to Oracle phase-2 (N/6 → N/7)
- Add format checks to self-review checklist
- New plan-format-validator hook: compares raw checkbox count
  against getPlanProgress() after plan writes, warns agent when
  labels are malformed (0/0 or partial skip scenarios)
This commit is contained in:
heunghingwan
2026-05-21 05:17:54 +08:00
parent a6e4691fcc
commit 73b5a7eb0e
8 changed files with 153 additions and 1 deletions
+5 -1
View File
@@ -95,7 +95,9 @@ task(
4. Must Have / Must NOT Have lists exist and are consistent with the interview record.
5. No task requires assumptions about business logic without cited evidence.
6. Plan path is .omo/plans/, not docs/ or plans/.
Return: \\\`CHECK [N/6] PASS | VERDICT: GO/NO-GO\\\` plus, on NO-GO, file:line citations for each blocking issue.\`
7. All TODO task labels use bare-number format ("1. xxx"), NOT "T1.", "Phase 1:", "Task-1." etc.
All Final Wave labels use "FN. xxx" format, NOT "T-F1.", "F-1.", "Final-1." etc.
Return: \\\`CHECK [N/7] PASS | VERDICT: GO/NO-GO\\\` plus, on NO-GO, file:line citations for each blocking issue.\`
)
\`\`\`
@@ -201,6 +203,8 @@ Before presenting summary, verify:
□ QA scenarios include BOTH happy-path AND negative/error scenarios?
□ Zero acceptance criteria require human intervention?
□ QA scenarios use specific selectors/data, not vague descriptions?
□ All TODO labels use bare-number format ("1. ", "2. ")? NO T1./Phase 1:/Task-1. etc.
□ All Final Wave labels use "FN. " format? NO T-F1./F-1./Final-1. etc.
\`\`\`
### Gap Handling Protocol
+3
View File
@@ -163,6 +163,9 @@ Max Concurrent: 7 (Waves 1 & 2)
> Implementation + Test = ONE Task. Never separate.
> EVERY task MUST have: Recommended Agent Profile + Parallelization info + QA Scenarios.
> **A task WITHOUT QA Scenarios is INCOMPLETE. No exceptions.**
> **FORMAT**: Task labels MUST use bare numbers: \`1.\`, \`2.\`, \`3.\` — NOT \`T1.\`, \`Task 1.\`, \`Phase 1:\`.
> The /start-work progress counter requires exact format. Deviation = progress shows 0/0.
> Final Verification Wave labels MUST use \`F1.\`, \`F2.\`, etc. — NOT \`T-F1.\`, \`F-1.\`, \`Final 1.\`.
- [ ] 1. [Task Title]