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/6-write.md
View on GitHub# /saas-review-all-prds — Phase 6: Write Report and Flag PRDs
> 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 6: Write Report and Flag PRDs
Use `AskUserQuestion` for write permission:
- Prompt: "May I write this review to `design/prd/prd-cross-review-[date].md`?"
- Options: `[A] Yes — write the report` / `[B] No — skip`
> **`[date]` here means ISO 8601 — `YYYY-MM-DD`, e.g.
> `prd-cross-review-2026-08-19.md`. This is not a style preference.**
> `.claude/scripts/review-scope.sh` picks the prior review with
> `sort | tail -1`, so lexical order IS chronological order only for ISO dates.
> Written as `aug-19-2026` or `19-08-2026`, the wrong file is chosen as the
> baseline, the changed-set is computed from it, and PRDs modified since the
> real last review silently escape the next one. That is the same
> quiet-escape failure the three fixes documented at the top of that script
> exist to prevent.
If any PRDs are flagged for revision, use a second `AskUserQuestion`:
- Prompt: "Should I update the systems index to mark these PRDs as needing revision? ([list of flagged PRDs])"
- Options: `[A] Yes — update systems index` / `[B] No — leave as-is`
- If yes: update each flagged PRD's Status field in features-modules-index.md to "Needs Revision".
(Do NOT append parentheticals to the status value — other skills match "Needs Revision"
as an exact string and parentheticals break that match.)
### Session State Update
After writing the report (and updating systems index if approved), silently
append to `production/session-state/active.md`:
## Session Extract — /saas-review-all-prds [date]
- Verdict: [PASS / NOT ASSESSED / CONCERNS / FAIL]
- PRDs reviewed: [N of M present]
- Phases not run: [names, or "None"]
- Flagged for revision: [comma-separated list, or "None"]
- Blocking issues: [N — brief one-line descriptions, or "None"]
- Recommended next: [the Phase 7 handoff action, condensed to one line]
- Report: design/prd/prd-cross-review-[date].md ← only if user approved the write
- Report: (not written — user declined at [date]) ← only if user declined the write
Use the appropriate line based on the user's response to the write-permission widget in Phase 6.
If `active.md` does not exist, create it with this block as the initial content.
Confirm in conversation: "Session state updated."
---
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 |