Rapid Saas Builder

Rapid SaaS Builder

Use this skill after PRD.md exists and the MVP scope is approved. Rapid SaaS Builder turns product requirements into a staged AI-assisted SaaS build workflow.

This skill is for execution, not validation. It should not validate business ideas, create marketing plans, expand product strategy, or invent features outside the PRD.

Primary Purpose

Create a clear, checklist-based build pipeline for:

1. Planning / PRD
2. Frontend Development
3. Backend Development
4. Integration
5. Deploy
6. Testing

Required Inputs

Use as many of these as available:

• PRD.md
• TASKS.md
• USER_FLOW.md
• MVP_CHECKLIST.md
• ARCHITECTURE_REVIEW.md
• Tech stack or repository context
• Deployment target
• Authentication, database, payment, and integration requirements

If PRD.md is missing, stop and ask for it. If architecture is missing, proceed with conservative assumptions and flag them.

Default Output Format

1. Build Summary
2. Required Inputs
3. Frontend Plan
4. Backend Plan
5. Integration Plan
6. Deployment Plan
7. Testing Plan
8. Tool Recommendations
9. MVP Guardrails
10. Next Implementation Tasks

Operating Rules

• Build only the MVP scope from PRD.md.
• Do not validate the business idea.
• Do not create marketing plans.
• Do not add features because they are "standard SaaS" unless the PRD requires them.
• Avoid overengineering.
• Prefer simple, proven tools.
• Prefer one deployable product over fragmented services.
• Keep stages small and independently verifiable.
• Use checklists for each stage.
• Treat AI coding tools as accelerators, not decision-makers.
• For mobile apps, do not implement external checkout for in-app digital goods, credits, premium features, or subscriptions unless a documented store-policy exception applies. Use Apple IAP / Google Play Billing, often via RevenueCat.

MVP Guardrails

Always include:

• In scope.
• Out of scope.
• Assumptions.
• Dependencies.
• Manual steps allowed.
• What not to build yet.
• Verification required before moving to the next stage.

Stage Handoff

Each stage should end with:

Done:
- [completed item]

Blocked:
- [blocker or none]

Verify:
- [test/check]

Next:
- [next task]

References

• references/ai-saas-pipeline.md for the full build pipeline.
• references/frontend-workflow.md for frontend execution.
• references/backend-workflow.md for backend execution.
• references/integration-workflow.md for integration execution.
• references/deploy-workflow.md for deploy execution.
• references/testing-workflow.md for testing execution.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: wolulabs
• Source: wolulabs/hermes-founder-os
• License: MIT

Install and usage instructions live in the source repository linked above.