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/4-scenarios.md
View on GitHub# Phase 4: Cross-System Scenario Walkthroughs
Walk through end-to-end customer workflows to identify edge cases that emerge only
when multiple SaaS modules interact.
### Critical Cross-System Touchpoints:
1. **Onboarding + Auth + Billing**:
- New user signs up through an organization invite link while not having an account.
- User signs up for a trial, trial expires mid-session, user attempts to save ongoing work.
2. **Quota Depletion + Background Processing**:
- Customer initiates a bulk batch import of 5,000 records on a plan with 2,000 quota remaining.
- Does the worker process 2,000 and pause, reject the whole batch, or prompt for an in-flight upgrade?
3. **Plan Downgrade + Resource Retention**:
- Admin downgrades from Enterprise (unlimited team seats) to Starter (3 seats).
- What happens to the remaining 10 active members? Are they suspended, converted to read-only, or selected by the admin?
4. **Account Deletion + Active Subscriptions**:
- User triggers "Delete Organization" while an annual Stripe subscription is active.
- Verify that Stripe webhook cancellation is dispatched and external data exports are properly purged.
### Scenario Output Table
Document each walked scenario:
- **Trigger**: User action or webhook event
- **Data Flow Across Systems**: Sequence of module interactions (e.g. `Router → Auth → Billing → Worker → DB`)
- **Observed Risk / Edge Case**: Discrepancies or missing states discovered
- **Remediation**: Recommended PRD update or architecture constraint
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: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | 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: 323k | 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: 323k | Updated | Claude CodeCodex | Verified | Install |