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

sdd: clarify deviation valve scope and concern status

Browse Source
This commit is contained in:
Drew Ritter
2026-07-20 02:33:10 -07:00
parent f0ef65c126
commit ef834a2949
2 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -396,7 +396,9 @@ message as your other bookkeeping:
downstream builds on. Record the ruling in the ledger. A green build with downstream builds on. Record the ruling in the ledger. A green build with
a parked, recorded deviation is complete — do not fail the task, and do a parked, recorded deviation is complete — do not fail the task, and do
not rewrite landed history to chase cosmetics. A load-bearing violation not rewrite landed history to chase cosmetics. A load-bearing violation
is different: that is a BLOCKED, not a deviation. is different: that is a BLOCKED, not a deviation. This valve is not the
breaker: it needs no exhausted fix rounds — a mechanical deviation
discovered at completion parks here directly, with its ruling in the ledger.
Then mark the todo complete and move on. Never move to the next task while Then mark the todo complete and move on. Never move to the next task while
the review has open Critical/Important issues that are neither fixed nor the review has open Critical/Important issues that are neither fixed nor

3
skills/subagent-driven-development/implementer-prompt.md
View File

@@ -156,7 +156,8 @@ Subagent (general-purpose):
If BLOCKED or NEEDS_CONTEXT, put the specifics in the final message If BLOCKED or NEEDS_CONTEXT, put the specifics in the final message
itself — the controller acts on it directly. itself — the controller acts on it directly.
Use DONE_WITH_CONCERNS if you completed the work but have doubts about correctness. Use DONE_WITH_CONCERNS if you completed the work but have doubts about correctness, or
when you are reporting a known deviation you could not safely fix.
Use BLOCKED if you cannot complete the task. Use NEEDS_CONTEXT if you need Use BLOCKED if you cannot complete the task. Use NEEDS_CONTEXT if you need
information that wasn't provided. Never silently produce work you're unsure about. information that wasn't provided. Never silently produce work you're unsure about.
``` ```