Review before it lands
Review the plan before anyone builds it, test the running app in a real browser, check readiness before merge, and write the release notes.
Review happens at 3 points: on the plan before anyone builds it, on the running app after a change, and on the branch before it merges. Each review skill reports what it checked and leaves the decisions and the merge to you.
Review the plan
Invoke /plan-review$plan-review@planr-plan-review after planning and before implementation. It checks that the outcome is clear and measurable, then looks at scope, sequencing, ownership, architecture, migration, security, operability, testing, and rollback in proportion to the change. It also checks the first-run and everyday developer experience: setup, diagnostics, defaults, and recovery.
It leads with one verdict: ready, ready with improvements, or needs revision. Then it lists what must be fixed, the improvements worth making, the open decisions with a recommended default, and the smallest next step. Each finding names the plan section it affects.
Test the running app
Invoke /browser-qa$browser-qa@planr-browser-qa after a change to a page, a form, sign-in, or navigation. It starts or reuses your local app and exercises the route in a real browser: navigation, forms, responsive layout, keyboard access, visible focus, accessible names, console errors, failed requests, and loading and error states.
Browser QA only reports. It lists reproducible findings with the page and the expected behavior, and you rerun it after the fix. A check it could not run is reported as unverified, and a passing subset never stands in for the whole app.
Check readiness before merge
Invoke /land$land@planr-land after implementation and checks are complete. It reads the branch, the worktree, the checks that already ran, and the release constraints, then answers ready, conditional, or blocked. You get the blockers, the ordered landing sequence with its preconditions, recovery guidance for the first failure, and one next action.
Land prepares the sequence; it never merges, publishes, or deploys.
Release what landed
After landing, /release$release@planr-release picks the next version from what changed for users and writes the release notes. It prepares the changelog and the version bump locally. Pushing tags, publishing packages, and deploying happen only when you ask.
Review an HTML artifact
To collect comments on a prototype or any HTML file, open it with openplanr artifact. Reviewers can comment, pin, reply in threads, and approve or request changes. See Artifact review and private sharing.
Prompts for this stage
- Review a plan before anyone builds it
- Check a plan's first-run developer experience
- Check migration and rollback before you build
- Test the change in a real browser
- Check a page for accessibility and console errors
- Check a branch is ready to land
- Prepare the merge and deploy steps
- Write release notes users can read