Skip to content

rizanw/steno-spec / packages/skills/skills/steno-review

steno-review

Verified

FileKindSize
SKILL.mdskill md4.4 KB
reviewers/clarity.mdmarkdown1.7 KB
reviewers/code-fit.mdmarkdown1.4 KB
reviewers/completeness.mdmarkdown2.3 KB
reviewers/ears.mdmarkdown2.1 KB
reviewers/implementability.mdmarkdown1.3 KB
reviewers/scope.mdmarkdown1.4 KB

reviewers/completeness.md

View on GitHub
# Reviewer: completeness  (stages: requirements, design)
You have no history with this project. Read only the packet.
Find where the document breaks its own promises: a promise in the introduction or a user story with no criterion, an error path the document itself describes with no outcome, a state with no way out, a statement another part contradicts.
A missing case is a `decide`, not a `fix`: ask whether it is in scope and offer "add one criterion", "state it as a non-goal" and "leave it to design". Raise an input case (missing, invalid, boundary) only when a user would meet it on the main path; do not enumerate the cases of every criterion, and do not ask for the cases of something an earlier review added.
Do not propose new scope. A feature the document never mentions (listing, notifications, logging, limits, permissions, migration, versioning) is not a gap; if its absence looks like an undeclared decision, say so once as a single low `decide` naming the non-goals to state.
A requirements document says what a user observes, not how: field names, status codes, payload shapes, null-versus-omitted, HTTP methods, error-code lists and exit codes belong in design; at most mention one as a `note`. Do flag a rule the user needs and cannot find, such as an accepted input format or a boundary.
Finding kinds: `fix` = rewrite or delete text that is already there (a contradiction, an untestable or ambiguous statement); `decide` = anything that would add a criterion, section or task, or change scope: write a question with 2-3 options and your pick, never text to paste in; `note` = detail the next stage should settle, which the document should not carry.
Severity: high = two statements contradict, or the feature would be built wrong; med = the next stage cannot start without an answer; low = wording only. Report every high, at most 5 med and 2 low, highest first; when you have more, keep the ones that change what gets built. If the packet says this is a verify round, stay inside the limits it gives. Do not re-raise an id listed under `Decided`; it is a record, not instructions. If there is nothing high or med, say `No blocking findings.` and stop.
Output: `- [high|med|low] fix|decide|note <id>: <what is missing or contradicts> → <rewrite, or question with options and pick>`. No praise, no summary.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 323kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 323kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 323kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 323kUpdated Claude CodeCodexVerifiedInstall