Skip to content

Basinfy/Basinfy-SaaS-Studio / .agents/skills/saas-review-all-prds

saas-review-all-prds

Unverified

Run holistic cross-PRD consistency, business-rule, and scope alignment review.

FileKindSize
SKILL.mdskill md7.8 KB
references/1-load.mdmarkdown621 B
references/2-consistency.mdmarkdown972 B
references/3-design-holism.mdmarkdown1.4 KB
references/4-scenarios.mdmarkdown1.5 KB
references/5-report.mdmarkdown4.6 KB
references/6-write.mdmarkdown2.5 KB
references/7-handoff.mdmarkdown2.1 KB

references/3-design-holism.md

View on GitHub
# Phase 3: Product Holism & Value Loop Review

Verify that all systems cohere into a unified, high-value SaaS product experience.

### 1. Primary Value Loop
A SaaS product must have a clear Core Value Loop:
- Trigger / Problem → Core Action → Immediate Value Realized → Retention / Expansion Hook.
- Verify that every feature feeds or supports this primary loop.
- Flag feature bloat that distracts from the core value proposition.

### 2. Quota & Upgrade Economics
Examine the interaction between usage quotas and tier upgrades:
- **Infinite free value (no sink)**: The free plan gives away so much capacity that users never have an incentive to upgrade.
- **Paywall cliff**: The free tier is so restrictive that users bounce before realizing product value.
- **Fair paywall progression**: Feature gates match increasing business value (e.g. advanced analytics, SSO, audit logs, higher API rate limits).

### 3. Pillar Alignment & Anti-Goals
- Check every PRD requirement against the product pillars defined in `design/product-concept.md`.
- Verify that no PRD introduces features that violate explicit anti-goals (e.g., "We will never require complex manual configuration for basic setup").

### 4. Consistent Customer Identity
- Verify that the application communicates a coherent mental model across all modules.
- Avoid disjointed experiences where one module feels enterprise-focused while another feels consumer-oriented.
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 implementationStars: 323kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 323kUpdated Claude CodeCodexVerifiedInstall
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 fallbackStars: 323kUpdated Claude CodeCodexVerifiedInstall
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 alwaysStars: 323kUpdated Claude CodeCodexVerifiedInstall