sdd-flow 1.0.0 → 1.2.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +83 -83
- package/bin/cli.js +380 -315
- package/package.json +32 -32
- package/templates/QUICKSTART.md +50 -50
- package/templates/agents/AGENTS.md +92 -92
- package/templates/agents/RULES.md +116 -116
- package/templates/agents/harness/claude-code/.hooks/guard-delete.sh +21 -21
- package/templates/agents/harness/claude-code/.hooks/guard-deps.sh +24 -24
- package/templates/agents/harness/claude-code/.hooks/guard-git.sh +23 -23
- package/templates/agents/harness/claude-code/commands/sdd-implement.md +3 -3
- package/templates/agents/harness/claude-code/commands/sdd-plan.md +3 -3
- package/templates/agents/harness/claude-code/commands/sdd-research.md +3 -3
- package/templates/agents/harness/claude-code/commands/sdd-validate.md +3 -3
- package/templates/agents/harness/opencode/commands/sdd-implement.md +3 -3
- package/templates/agents/harness/opencode/commands/sdd-plan.md +3 -3
- package/templates/agents/harness/opencode/commands/sdd-research.md +3 -3
- package/templates/agents/harness/opencode/commands/sdd-validate.md +3 -3
- package/templates/agents/prompts/rpi-implement.md +46 -46
- package/templates/agents/prompts/rpi-plan.md +117 -117
- package/templates/agents/prompts/rpi-validate.md +96 -96
|
@@ -1,96 +1,96 @@
|
|
|
1
|
-
# Prompt: Validate (RPI — Phase 4)
|
|
2
|
-
|
|
3
|
-
Use this prompt to verify that the implementation satisfies the spec and all acceptance criteria.
|
|
4
|
-
|
|
5
|
-
---
|
|
6
|
-
|
|
7
|
-
## Agent instruction
|
|
8
|
-
|
|
9
|
-
You will validate the implementation of a completed feature against its spec and test cases.
|
|
10
|
-
|
|
11
|
-
**Before starting, read:**
|
|
12
|
-
- `agents/AGENTS.md`
|
|
13
|
-
- `agents/PROJECT.md`
|
|
14
|
-
- `agents/RULES.md`
|
|
15
|
-
- `agents/specs/NNN-name/SPEC.md`
|
|
16
|
-
- `agents/specs/NNN-name/TASK.md` — confirm all tasks are marked `[x]`
|
|
17
|
-
- `agents/specs/NNN-name/TEST.md`
|
|
18
|
-
- `agents/specs/NNN-name/PROGRESS.md`
|
|
19
|
-
- The code files produced during Implement (listed in PROGRESS.md History)
|
|
20
|
-
|
|
21
|
-
**Expected input:**
|
|
22
|
-
- Spec number and name (e.g. `001-user-authentication`)
|
|
23
|
-
|
|
24
|
-
---
|
|
25
|
-
|
|
26
|
-
## Validation procedure
|
|
27
|
-
|
|
28
|
-
### Step 1 — Confirm implementation is complete
|
|
29
|
-
Check that every task in `TASK.md` is marked `[x]`.
|
|
30
|
-
If any `[ ]` remains, **stop and report** — do not proceed with validation.
|
|
31
|
-
|
|
32
|
-
### Step 2 — Verify task-level conditions
|
|
33
|
-
For each task in `TASK.md`, read its `verify:` condition and check whether
|
|
34
|
-
the produced code satisfies it. Examine the actual files — do not assume.
|
|
35
|
-
|
|
36
|
-
### Step 3 — Verify acceptance test cases
|
|
37
|
-
For each test case in `TEST.md`, assess whether the implementation satisfies
|
|
38
|
-
the Given/When/Then scenario. Read the relevant code directly.
|
|
39
|
-
|
|
40
|
-
### Step 4 — Produce VALIDATION.md
|
|
41
|
-
Write `agents/specs/NNN-name/VALIDATION.md` with the structure below.
|
|
42
|
-
|
|
43
|
-
---
|
|
44
|
-
|
|
45
|
-
## Deliverable: VALIDATION.md
|
|
46
|
-
|
|
47
|
-
```markdown
|
|
48
|
-
# VALIDATION — [Feature Name]
|
|
49
|
-
|
|
50
|
-
## Status: [✅ Approved | ⚠️ Partial | ❌ Failed]
|
|
51
|
-
|
|
52
|
-
---
|
|
53
|
-
|
|
54
|
-
## Task Verification
|
|
55
|
-
|
|
56
|
-
| Task | verify: condition | Status |
|
|
57
|
-
|---|---|---|
|
|
58
|
-
| T01 | [condition from TASK.md] | ✅ Met / ❌ Not met / ⚠️ Partial |
|
|
59
|
-
| T02 | ... | ... |
|
|
60
|
-
|
|
61
|
-
---
|
|
62
|
-
|
|
63
|
-
## Acceptance Test Coverage
|
|
64
|
-
|
|
65
|
-
| Test Case | Description | Status | Evidence |
|
|
66
|
-
|---|---|---|---|
|
|
67
|
-
| TC01 | [behavior being tested] | ✅ Verified / ❌ Not met / ⚠️ Partial | [file and line or behavior observed in code] |
|
|
68
|
-
| TC02 | ... | ... | ... |
|
|
69
|
-
|
|
70
|
-
---
|
|
71
|
-
|
|
72
|
-
## Gaps Found
|
|
73
|
-
|
|
74
|
-
List any `verify:` conditions or test cases that are not fully met.
|
|
75
|
-
Write `None` if everything is satisfied.
|
|
76
|
-
|
|
77
|
-
- [ ] [Gap description — what is missing or incorrect]
|
|
78
|
-
|
|
79
|
-
---
|
|
80
|
-
|
|
81
|
-
## Recommendation
|
|
82
|
-
|
|
83
|
-
[Approve — all criteria met]
|
|
84
|
-
[Request fixes — list the gaps that must be resolved before approval]
|
|
85
|
-
```
|
|
86
|
-
|
|
87
|
-
---
|
|
88
|
-
|
|
89
|
-
## Constraints
|
|
90
|
-
|
|
91
|
-
- Do not write or modify any code in this phase
|
|
92
|
-
- Do not mark gaps as acceptable — report them, even if minor
|
|
93
|
-
- If a test case cannot be verified from static code analysis alone, flag it explicitly:
|
|
94
|
-
`⚠️ Requires runtime verification — cannot confirm from code alone`
|
|
95
|
-
- After delivering VALIDATION.md, **wait for developer review**
|
|
96
|
-
- If gaps are found and fixed, a new Validate session must be run — do not reuse this report
|
|
1
|
+
# Prompt: Validate (RPI — Phase 4)
|
|
2
|
+
|
|
3
|
+
Use this prompt to verify that the implementation satisfies the spec and all acceptance criteria.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Agent instruction
|
|
8
|
+
|
|
9
|
+
You will validate the implementation of a completed feature against its spec and test cases.
|
|
10
|
+
|
|
11
|
+
**Before starting, read:**
|
|
12
|
+
- `agents/AGENTS.md`
|
|
13
|
+
- `agents/PROJECT.md`
|
|
14
|
+
- `agents/RULES.md`
|
|
15
|
+
- `agents/specs/NNN-name/SPEC.md`
|
|
16
|
+
- `agents/specs/NNN-name/TASK.md` — confirm all tasks are marked `[x]`
|
|
17
|
+
- `agents/specs/NNN-name/TEST.md`
|
|
18
|
+
- `agents/specs/NNN-name/PROGRESS.md`
|
|
19
|
+
- The code files produced during Implement (listed in PROGRESS.md History)
|
|
20
|
+
|
|
21
|
+
**Expected input:**
|
|
22
|
+
- Spec number and name (e.g. `001-user-authentication`)
|
|
23
|
+
|
|
24
|
+
---
|
|
25
|
+
|
|
26
|
+
## Validation procedure
|
|
27
|
+
|
|
28
|
+
### Step 1 — Confirm implementation is complete
|
|
29
|
+
Check that every task in `TASK.md` is marked `[x]`.
|
|
30
|
+
If any `[ ]` remains, **stop and report** — do not proceed with validation.
|
|
31
|
+
|
|
32
|
+
### Step 2 — Verify task-level conditions
|
|
33
|
+
For each task in `TASK.md`, read its `verify:` condition and check whether
|
|
34
|
+
the produced code satisfies it. Examine the actual files — do not assume.
|
|
35
|
+
|
|
36
|
+
### Step 3 — Verify acceptance test cases
|
|
37
|
+
For each test case in `TEST.md`, assess whether the implementation satisfies
|
|
38
|
+
the Given/When/Then scenario. Read the relevant code directly.
|
|
39
|
+
|
|
40
|
+
### Step 4 — Produce VALIDATION.md
|
|
41
|
+
Write `agents/specs/NNN-name/VALIDATION.md` with the structure below.
|
|
42
|
+
|
|
43
|
+
---
|
|
44
|
+
|
|
45
|
+
## Deliverable: VALIDATION.md
|
|
46
|
+
|
|
47
|
+
```markdown
|
|
48
|
+
# VALIDATION — [Feature Name]
|
|
49
|
+
|
|
50
|
+
## Status: [✅ Approved | ⚠️ Partial | ❌ Failed]
|
|
51
|
+
|
|
52
|
+
---
|
|
53
|
+
|
|
54
|
+
## Task Verification
|
|
55
|
+
|
|
56
|
+
| Task | verify: condition | Status |
|
|
57
|
+
|---|---|---|
|
|
58
|
+
| T01 | [condition from TASK.md] | ✅ Met / ❌ Not met / ⚠️ Partial |
|
|
59
|
+
| T02 | ... | ... |
|
|
60
|
+
|
|
61
|
+
---
|
|
62
|
+
|
|
63
|
+
## Acceptance Test Coverage
|
|
64
|
+
|
|
65
|
+
| Test Case | Description | Status | Evidence |
|
|
66
|
+
|---|---|---|---|
|
|
67
|
+
| TC01 | [behavior being tested] | ✅ Verified / ❌ Not met / ⚠️ Partial | [file and line or behavior observed in code] |
|
|
68
|
+
| TC02 | ... | ... | ... |
|
|
69
|
+
|
|
70
|
+
---
|
|
71
|
+
|
|
72
|
+
## Gaps Found
|
|
73
|
+
|
|
74
|
+
List any `verify:` conditions or test cases that are not fully met.
|
|
75
|
+
Write `None` if everything is satisfied.
|
|
76
|
+
|
|
77
|
+
- [ ] [Gap description — what is missing or incorrect]
|
|
78
|
+
|
|
79
|
+
---
|
|
80
|
+
|
|
81
|
+
## Recommendation
|
|
82
|
+
|
|
83
|
+
[Approve — all criteria met]
|
|
84
|
+
[Request fixes — list the gaps that must be resolved before approval]
|
|
85
|
+
```
|
|
86
|
+
|
|
87
|
+
---
|
|
88
|
+
|
|
89
|
+
## Constraints
|
|
90
|
+
|
|
91
|
+
- Do not write or modify any code in this phase
|
|
92
|
+
- Do not mark gaps as acceptable — report them, even if minor
|
|
93
|
+
- If a test case cannot be verified from static code analysis alone, flag it explicitly:
|
|
94
|
+
`⚠️ Requires runtime verification — cannot confirm from code alone`
|
|
95
|
+
- After delivering VALIDATION.md, **wait for developer review**
|
|
96
|
+
- If gaps are found and fixed, a new Validate session must be run — do not reuse this report
|