harden-plan
/harden-plan — Pre-code Plan Quality Gate
Takes a WRITTEN plan and runs the /review-pr anti-slop lens against it
BEFORE any code is written. Goal: catch security, concurrency, round-trip,
and pattern-consistency issues when fixing them is a plan edit, not a code
refactor.
Usage
/harden-plan <path-to-plan-file> # file input (enables write-back)
/harden-plan "<pasted plan text>" # inline input (print-only)
/harden-plan # auto-detect plan-mode buffer
/harden-plan --plan-mode # explicit plan-mode grab
This skill runs AFTER design has been settled (via /superpowers:brainstorm
and/or /grill-me) and BEFORE you start coding. For post-code review use
/review-pr. For fixing review findings use /fix-pr-review.
More from bhagyamudgal/skills
review-pr
Deep, anti-slop review of a GitHub PR. Grounds findings in the linked issue's intent, runs a Claude reviewer (+ conditional silent-failure hunter) in parallel with existing CodeRabbit comments fetched from the PR, then critic-passes the findings before printing. Use when user says "review this pr", pastes a GitHub PR URL, or asks "check this pull request". NOT for local uncommitted changes — use /parallel-review for those.
14fix-pr-review
Triage and fix CodeRabbit / review-pr findings on a GitHub PR, then reply + resolve conversations. Classifies each finding (FIX/DISMISS/DEFER/DISAGREE/NEEDS-INPUT), runs /done, posts specific replies. Use on CodeRabbit review URLs, PR URLs, or local review files. Pairs with /review-pr.
8forge-plan
Use when starting any non-trivial feature or design task that needs the full idea-to-implementation pipeline. Also use when user says "forge", "forge plan", "full pipeline", or wants the complete AI development workflow before shipping.
6project-discovery
Deep project discovery and architecture planning. Use when starting a new project, when user says "new project", "let's build", or asks for help architecting/planning a non-trivial application.
6qa
Use when user says "qa", "test the flow", "QA this", "verify the UI", "test this page", "check if it works", "end-to-end check", or after completing code changes that affect UI and need manual verification replaced by automation.
5done
MANDATORY post-task verification. Run after EVERY task — no exceptions, no skipping, regardless of task size. Executes type-check, parallel code review, and code simplification in sequence.
5