singularity/singularity-forge
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

sf snapshot: pre-dispatch, uncommitted changes after 35m inactivity

Browse source
This commit is contained in:
Mikael Hugo 2026-05-06 15:24:04 +02:00
parent d8570d059e
commit a7f245ef1b
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
src/resources/extensions/sf/prompts/validate-milestone.md
View file

@ -57,7 +57,7 @@ Prompt: "Review milestone {{milestoneId}} cross-slice integration. Working direc
**Reviewer C — Assessment & Acceptance Criteria**
Agent: `reviewer`
Prompt: "Review milestone {{milestoneId}} assessment evidence and acceptance criteria. Working directory: {{workingDirectory}}. Read `.sf/milestones/{{milestoneId}}/{{milestoneId}}-CONTEXT.md` for acceptance criteria. Check for ASSESSMENT files in each slice directory. Verify each acceptance criterion maps to either a passing assessment result or clear SUMMARY evidence. Then review the inlined milestone verification classes from planning. For each non-empty planned class, output a markdown table: Class | Planned Check | Evidence | Verdict. Use the exact class names `Contract`, `Integration`, `Operational`, and `UAT` whenever those classes are present. If no verification classes were planned, say that explicitly. Output two sections: `Acceptance Criteria` with a checklist `[ ] Criterion | Evidence`, and `Verification Classes` with the table. End with a one-line verdict: PASS if all criteria and verification classes are covered, NEEDS-ATTENTION if gaps exist."
Prompt: "Review milestone {{milestoneId}} assessment evidence and acceptance criteria. Working directory: {{workingDirectory}}. Read `.sf/milestones/{{milestoneId}}/{{milestoneId}}-CONTEXT.md` for acceptance criteria. Check for ASSESSMENT files in each slice directory. Verify each acceptance criterion maps to either a passing assessment result or clear SUMMARY evidence. Rubric: CRITERION = stated success goal from milestone roadmap (e.g., 'distributed lock passes all race tests'). IMPLEMENTATION GAP = missing internal behavior or test that doesn't block the criterion (e.g., 'missing internal error-rate histogram' when the criterion only requires 'no false negatives'). A criterion is COVERED if: the milestone's slice SUMMARYs provide end-to-end evidence that the stated goal is achieved. A criterion is PARTIAL if: some evidence exists but boundary cases or integration gaps remain. A criterion is MISSING if: no slice SUMMARY addresses it. Then review the inlined milestone verification classes from planning. For each non-empty planned class, output a markdown table: Class | Planned Check | Evidence | Verdict. Use the exact class names `Contract`, `Integration`, `Operational`, and `UAT` whenever those classes are present. If no verification classes were planned, say that explicitly. Output two sections: `Acceptance Criteria` with a checklist `[ ] Criterion | Coverage | Evidence`, and `Verification Classes` with the table. For any PARTIAL criterion, note whether remediation is blocking (fails the criterion itself) or hardening (improves beyond criterion scope). End with a one-line verdict: PASS if all criteria are COVERED and no blocking gaps, NEEDS-ATTENTION if coverage gaps exist."
### Step 2 — Synthesize Findings