nWave-ai/nWave / nWave/skills/nw-rigor
nw-rigor
VerifiedUse when the user wants to see or change how much rigor a project gets (review rounds, examine level), which provider/model a role uses, or whether readable documents are written. The LLM reads the current settings, asks only the missing choices in plain words, and runs `nwave-ai rigor` or `nwave-ai model set` itself. Never derives a model from a competence label.
| Commit | Indexed | Files | Content hash |
|---|---|---|---|
bd0fbf4current | 2026-11-16 | 1 · 6.2 KB | cff15a53d6662aff… |
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: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | 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: 322k | 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: 322k | Updated | Claude CodeCodex | Verified | Install |