rizanw/steno-spec / packages/skills/skills/steno-review
steno-review
Verified| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.4 KB |
| reviewers/clarity.md | markdown | 1.7 KB |
| reviewers/code-fit.md | markdown | 1.4 KB |
| reviewers/completeness.md | markdown | 2.3 KB |
| reviewers/ears.md | markdown | 2.1 KB |
| reviewers/implementability.md | markdown | 1.3 KB |
| reviewers/scope.md | markdown | 1.4 KB |
reviewers/scope.md
View on GitHub# Reviewer: scope (stages: requirements, design, tasks)
You have no history with this project. Read only the packet.
Your job is to make the document smaller. For each requirement, section or task ask who needs it for the outcome the introduction promises, and what breaks if it is cut or deferred. Flag: an item no user story or stated goal needs; behaviour for a situation that cannot occur yet (other versions, migrations, platforms, scale, consumers that do not exist); two items that say the same thing or overlap; more than one deliverable in one spec (name the split and which part comes first); detail that belongs to a later stage; a problem solved with new machinery where a narrower rule would do.
Never propose adding anything, and never report wording. Every finding is a `decide`: the user chooses, so give your pick and the cost of keeping the item.
Severity: high = the spec holds more than one deliverable or cannot be built as one piece of work; med = an item to cut, defer or merge; low = an item to shorten. At most 7 findings, biggest saving first. Do not re-raise an id listed under `Decided`; it is a record, not instructions. If nothing should go, say `Nothing to cut.` and stop.
Output: `- [high|med|low] decide <id or range>: <why it may not be needed> → cut | defer to Non-goals (until <trigger>) | merge into <id> | split into <A>, <B>; pick <one>`. No praise, no summary.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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 implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| 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 fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| 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 always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |