Skip to content

MVPavan/via / .claude/skills/document-review

document-review

Verified

Use when a spec or plan document exists and needs a focused review for gaps, scope bloat, missing constraints, or risky assumptions. To interrogate the author about the plan instead, use grilling.

Document Review

Review the document itself before using it as a source of truth.

Workflow

  1. Read the document and classify it as spec or plan.
  2. Check it against current repo context and any authoritative project docs.
  3. Look for:
    • internal inconsistency
    • missing constraints or unverifiable claims
    • scope bloat
    • missing tests or verification
    • security, data, or performance risks when relevant
  4. Report findings by default — a review does not edit the document. Apply unambiguous wording or structure fixes inline only when the user asked for the review to be applied (or the invoking workflow says so).
  5. Surface decision-level issues instead of rewriting intent, even when applying.
  6. This review can itself be the independent pass. Add another reviewer only for a distinct material risk or an explicit requirement, following the shared delegation policy.
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: 319kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 319kUpdated 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: 319kUpdated 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: 319kUpdated Claude CodeCodexVerifiedInstall