rogee/superpowers
1
0
Fork 0
mirror of https://github.com/obra/superpowers.git synced 2026-07-07 02:09:04 +08:00
Code Issues Packages Projects Releases Wiki Activity

feat(skills): optional spec-derived e2e verification step in SDD

Browse Source
This commit is contained in:
Jesse Vincent
2026-07-04 23:15:19 -07:00
parent 36030778df
commit 9f06b4f815
1 changed files with 28 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
skills/subagent-driven-development/SKILL.md
View File

@@ -263,6 +263,33 @@ a ledger file, not only in todos.
- `git clean -fdx` will destroy the ledger (it's git-ignored scratch); if - `git clean -fdx` will destroy the ledger (it's git-ignored scratch); if
that happens, recover from `git log`. that happens, recover from `git log`.
## Optional: Spec-Derived E2E Verification
Applies only when a spec governing the code the plan touches — the spec
the plan implements, or a repo spec covering that surface — contains an
"E2E scenario cards" section, or your human partner asked for end-to-end
verification. Otherwise this section does not apply — skip it entirely.
- At skill start, when you read the plan, open the spec it names — and if
it names none, check the repo's spec directory (e.g.
`docs/superpowers/specs/`) for specs governing the code the plan
touches — and check for an "E2E scenario cards" section. If present,
add a pending "spec-derived e2e verification" item to your todo list
and the progress ledger so compaction cannot lose it.
- After the final whole-branch review passes: use
superpowers:agentic-end-to-end-testing. Dispatch a card-author subagent
per its authoring-cards-from-a-spec.md, run its
scripts/check-cards-against-spec yourself on the author's output
(self-attestation is not the gate), then dispatch a runner subagent per
its runner-prompt.md against the built branch.
- Card FAILs are findings: dispatch ONE fix subagent with the complete
list, then re-run the failed cards. The card author never fixes. Fix-wave
commits land after the final review, so give the fix diff its own
task-review gate before finishing — a green re-run alone does not ship
unreviewed changes.
- Results land before superpowers:finishing-a-development-branch, so
"ready to merge" includes live-scenario evidence.
## Prompt Templates ## Prompt Templates
- [implementer-prompt.md](implementer-prompt.md) - Dispatch implementer subagent - [implementer-prompt.md](implementer-prompt.md) - Dispatch implementer subagent
@@ -409,6 +436,7 @@ Done!
- **superpowers:using-git-worktrees** - Ensures isolated workspace (creates one or verifies existing) - **superpowers:using-git-worktrees** - Ensures isolated workspace (creates one or verifies existing)
- **superpowers:writing-plans** - Creates the plan this skill executes - **superpowers:writing-plans** - Creates the plan this skill executes
- **superpowers:requesting-code-review** - Code review template for the final whole-branch review - **superpowers:requesting-code-review** - Code review template for the final whole-branch review
- **superpowers:agentic-end-to-end-testing** - Optional spec-derived e2e verification after the final review (see Optional: Spec-Derived E2E Verification)
- **superpowers:finishing-a-development-branch** - Complete development after all tasks - **superpowers:finishing-a-development-branch** - Complete development after all tasks
**Subagents should use:** **Subagents should use:**