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/2-consistency.md
View on GitHub# Phase 2: Cross-PRD Consistency Check
Verify that requirement definitions across PRDs do not contradict each other.
### Areas to Check:
1. **Data Contracts & Terminology**:
- Are entities named consistently? (e.g. `workspace` vs `organization` vs `team`; `member` vs `user`).
- Are IDs, roles, and status strings standardized across documents?
2. **Dependent Requirement Guarantees**:
- If `teams.md` relies on seat limits defined in `billing.md`, does `billing.md` explicitly expose `seat_quota` and define behavior when the limit is exceeded?
- If `notifications.md` consumes events from `auth.md`, are all auth event payloads specified?
3. **Permission & Security Contradictions**:
- Does one PRD state that "any member can export reports", while another states "only Admin/Owner roles can export data"?
4. **Error Handling & State Sync**:
- How do dependent systems handle transient failures (e.g. webhook delivery delays, billing grace periods)?
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 |