Basinfy/Basinfy-SaaS-Studio / .agents/skills/saas-review-all-prds
saas-review-all-prds
UnverifiedRun holistic cross-PRD consistency, business-rule, and scope alignment review.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.8 KB |
| references/1-load.md | markdown | 621 B |
| references/2-consistency.md | markdown | 972 B |
| references/3-design-holism.md | markdown | 1.4 KB |
| references/4-scenarios.md | markdown | 1.5 KB |
| references/5-report.md | markdown | 4.6 KB |
| references/6-write.md | markdown | 2.5 KB |
| references/7-handoff.md | markdown | 2.1 KB |
references/7-handoff.md
View on GitHub# /saas-review-all-prds — Phase 7: Handoff
> Part of `/saas-review-all-prds`. `SKILL.md` names when to read this file; the settings it
> resolved and the rules under its later headings still apply here.
## Phase 7: Handoff
After all file writes are complete, use `AskUserQuestion` for a closing widget.
Before building options, check project state:
- Are there any Warning-level items that are simple edits (flagged with "30-second edit", "brief addition", or similar)? → offer inline quick-fix option
- Are any PRDs in the "Flagged for Revision" table? → offer /saas-design-review option for each
- Read features-modules-index.md for the next system with Status: Not Started → offer /saas-design-system option
- Is the verdict PASS or CONCERNS on a review that ran both passes? → offer /saas-gate-check or /saas-create-architecture. A focus run (`consistency` or `design-theory`) checked one pass, so it never offers either
Build the option list dynamically — only include options that apply:
**Option pool:**
- `[_] Apply quick fix: [W-XX description] in [prd-name].md — [effort estimate]` (one option per simple-edit warning; only for Warning-level, not Blocking)
- `[_] Run /saas-design-review [flagged-prd-path] — address flagged warnings` (one per flagged PRD, if any)
- `[_] Run /saas-design-system [next-system] — next in design order` (always include, name the actual system)
- `[_] Run /saas-create-architecture — begin architecture (verdict is PASS/CONCERNS)` (include only if the verdict is PASS or CONCERNS on a review that ran both passes — never on FAIL, NOT ASSESSED or a focus run)
- `[_] Run /saas-gate-check — validate Systems Design phase gate` (include if verdict is PASS on a review that ran both passes)
- `[_] Stop here`
Assign letters A, B, C… only to included options. Mark the most pipeline-advancing option as `(recommended)`.
In collaborative and guided modes, never end the skill with plain text — always
close with this widget. In autonomous mode, print the verdict and recommended
next step, then record via `log_decision` (no widget).
---
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 |