Turn a one-line SaaS idea into a complete blueprint, right inside Claude Code.
Install · Use · See it in action · Customise · Roadmap
Type one line in Claude Code. Get back nine markdown files in your project folder. Real research, real architecture, real Claude Code ready build prompts. Two minutes. No browser. No signup. No API key.
$ /planmysaas "AI tutor for JEE students, voice-first, ₹99/month"
✓ Blueprint generated for: AI tutor for JEE students…
./planmysaas-blueprint/
├── 01-idea.md ← Refined idea + audience + business model
├── 02-research.md ← Competitors, problem clusters, opportunities
├── 03-analysis.md ← BMC, SWOT, PMF score, risk matrix
├── 04-architecture.md ← Services, data models, API surface
├── 05-features.md ← Feature specs with user flows
├── 06-frontend.md ← Routes, wireframes, component tree
├── 07-phases.md ← Release plan + milestones
├── 08-build-playbook.md ← Decision-grade build steps with rubrics, leaf to root
└── README.md ← Index of everythingOne command. The skill auto-discovers from your ~/.claude/skills/ folder on startup.
git clone https://github.com/creationskiro/planmysaas-claude-skill ~/.claude/skills/planmysaasThat's it. Restart Claude Code (or open a new session) and the skill is live.
In Claude Code, run the slash command:
/planmysaas "your one-line saas idea"
Or just describe a product idea naturally — Claude picks up the skill from the description:
"Help me plan a SaaS for AI + robotics learning for school students"
"Turn this idea into a structured blueprint: AI tutor for JEE students, voice-first, ₹99 per month"
"I want to build a course platform for college students. Give me an architecture and feature list."
The skill writes a fresh ./planmysaas-blueprint/ folder in your current project directory. Open README.md first — it indexes the rest.
Each file in ./planmysaas-blueprint/ is a deep, structured document written for engineers and founders, not for marketers. Below are screenshots from the PlanMySaaS dashboard showing what each section looks like when rendered visually. The skill outputs the same data as markdown.
5–8 real competitors, classified into direct / adjacent / substitute / manual-alternative. Each gets an opportunity score from 1–10 based on workflow overlap, weakness exploitability, and differentiation room. Plus problem clusters, market gaps, insights, and a strategic direction with the recommended wedge.
The full 9-block business model canvas, plus directional TAM/SAM/SOM, Porter's 5 forces, SWOT, competitive positioning, a 7-row risk matrix, a 6-dimension PMF score breakdown, and a phased strategic recommendation list.
3–5 top-level containers, 10–25 services or modules grouped by domain, 8–15 core data models with relations, 20+ REST API endpoints, background jobs, external integrations, and an opinionated tech stack with one row per layer.
12–20 feature specs, each with a numeric ID (F-01, F-02 …), priority (P0–P3), effort estimate in days, primary actors, purpose, numbered user flow, testable acceptance criteria, edge cases, and telemetry events to fire.
The most important artifact in the blueprint. Not a paste-ready prompt list — a decision-grade build playbook structured as a dependency tree: foundation primitives first (repo, deploy pipeline, data layer), then services, then features in priority order, then polish, then ship. Every step includes:
- 🎯 Goal · 📍 Why this comes first · 📥 Inputs · 📤 Outputs
- 🛠 Implementation details (files, tech decisions, mandatory patterns)
- ✅ Acceptance rubric (8–14 testable checkboxes per step)
⚠️ Edge cases · ❌ Common pitfalls · 📊 Quality bar (measurable thresholds)- 🛑 Stop-and-review gate before the next step
The user (or their AI coding tool) follows it step-by-step. Each step's rubric must pass before advancing — no skipping ahead. Reads like a senior engineer's runbook for a high-stakes deploy.
Routes grouped by public/app/admin sections, page specs for the top 8 routes, ASCII wireframes you can read in the markdown file, a component tree of 12–25 reusable components with their key props, and a design system covering colors, typography, spacing, radius, shadow, and motion.
In the dashboard, all sections land in an Artifact Hub view (above) with completion tracking, version history, and exports. The skill ships the same content as portable markdown — no lock-in.
The skill and the PlanMySaaS dashboard are not competitors. They are the same product expressed at two different friction levels.
| Capability | This Skill | planmysaas.com |
|---|---|---|
| Top-level stages generated | 8 | 30+ |
| Total generated pages / artifacts | 9 markdown files | 26+ artifacts across 8 categories |
| Sub-views per stage | inline sections | multi-tab pages (Research = 8 tabs, Analysis = 9, Architecture = 6, Phases = 9 …) |
| Sidebar workflow groups | — | 7 groups — Command · Research · Planning · Frameworks · Output · Evolution · Tools |
| Inline charts (recharts) | — | ✓ bars, canvas, score dials |
| Visual architecture canvas | text only | ✓ drag-able 29-node diagram |
| Auto-research on real competitors (web search) | Claude only | ✓ deep research, 60 sub-topics |
| Project documentation page | — | ✓ a single docs hub per project, auto-generated |
| Versions + diff view per stage | — | ✓ rollback to any earlier version, side-by-side compare |
| Re-run any stage with feedback | — | ✓ "make this more X" prompts on any output |
| Team collaboration | — | ✓ workspaces + invites |
| Build tracker (post-blueprint) | — | ✓ kanban-style progress, P0 / P1 swimlanes |
| Risk register · decision log · event flows | — | ✓ dedicated pages |
| Exports (PDF, JSON, ZIP, public share link) | — | ✓ |
| Admin-side runbooks (refunds, password resets, etc.) | — | ✓ for ops teams |
| Cost per use | your Claude tokens | credits (100 free) |
| Internet required | — | ✓ |
| Account required | — | ✓ |
| Best for | Solo · in-editor · fast loop | Teams · long projects · iteration over months |
Use the skill when you are exploring an idea, prototyping for a hackathon, or already deep in Claude Code.
Use the dashboard when the project is real — when you have decided to spend three months on it, when a co-founder joins, when you want exports for a pitch deck, or when you need version history because you will iterate on the wedge based on early customer interviews.
The skill ships the planning pipeline. The web product ships the planning pipeline plus a public knowledge surface that the skill structurally cannot include. Free, no signup needed for any of these:
| Surface | What it gives you |
|---|---|
| 🔍 Ideas directory | 500+ curated SaaS ideas organised by category — B2B SaaS, Micro-SaaS, AI, FinTech, HealthTech, EdTech, No-Code, Developer Tools, Marketing, Weekend Projects. Each idea has a deep page with audience, business model, tech stack, and a one-click "plan this idea" button that pre-fills the blueprint flow. |
| 🛠️ Free tools directory | 12+ founder calculators, all free, no signup — Runway · Break-even · SaaS pricing · Startup cost · LTV/CAC · MRR growth · Market size (TAM/SAM/SOM) · Business name generator · Customer persona builder · Business plan template · Tech stack recommender · SEO competitor analyzer. |
| 📘 Guides | Step-by-step long-form guides on planning, architecture, pricing, and go-to-market. Structured as a path to a concrete outcome. |
| ✍️ Blog | Long-form deep reads for SaaS founders — research, frameworks, case studies. Includes the launch story for this skill. |
| 📉 Startup failures | Post-mortems of $46B+ in losses — what went wrong and the lesson per failure. |
| 📈 Startup success stories | How the best were built. Attached frameworks and decisions. |
| 🆚 Alternatives pages | "X vs Y" comparison pages for popular SaaS planning + AI tools. |
| 🆘 Help center | Per-page docs for every dashboard surface — Blueprint · Dashboard · Growth · Frameworks. |
The skill is the in-editor cousin of all of this. If you only ever use /planmysaas, you still get the blueprint pipeline. If you visit planmysaas.com, you also get a small library of ideas, tools, and case studies for free.
The skill is plain markdown. Open any file in ~/.claude/skills/planmysaas/ and edit it.
~/.claude/skills/planmysaas/
├── SKILL.md ← Frontmatter + orchestration workflow
├── README.md ← This file
├── LICENSE ← MIT
├── pipeline/
│ ├── 01-idea-refine.md ← Stage 1 prompt
│ ├── 02-research.md ← Stage 2 prompt
│ ├── 03-analysis.md ← Stage 3 prompt
│ ├── 04-architecture.md ← Stage 4 prompt
│ ├── 05-features.md ← Stage 5 prompt
│ ├── 06-frontend.md ← Stage 6 prompt
│ ├── 07-phases.md ← Stage 7 prompt
│ └── 08-build-playbook.md ← Stage 8 prompt (the build playbook generator)
├── templates/
│ ├── blueprint-readme.md ← Final README template
└── assets/ ← README screenshots
Common tweaks:
- Change default tech stack — edit
pipeline/04-architecture.md. Replace Next.js / Postgres / Vercel with your preferred defaults. - Add a stage — drop a new file like
pipeline/09-marketing.md, then add it to the pipeline table inSKILL.md. - Tighten the tone — every prompt has a Tone section at the bottom. Rewrite it.
- Change the output folder — search
./planmysaas-blueprint/inSKILL.mdand replace. - Localise — add Hindi / Spanish / French versions of any prompt; Claude will follow the language you ask in.
No build step. No package.json. No deploy. Save the file, run /planmysaas again, the next invocation uses the new prompt.
| When | What |
|---|---|
| Now (v1.0) | 8-stage prompt-based pipeline · MIT · auto-discovery · markdown output |
| Next 2 weeks | Optional auth.md for API mode — connect a PlanMySaaS API key to save the project to your dashboard with charts, version history, and exports |
| Q3 2026 | Skill variants — /planmysaas-mvp (faster 4-stage cut), /planmysaas-validate (idea validation only), /planmysaas-redesign (replan an existing product) |
| Q3 2026 | MCP server — same engine over Model Context Protocol so it works in any MCP-compatible client (Cursor, Cline, Continue) |
| Q4 2026 | Localisation — Hindi / Hinglish prompts for Indian founders |
Want something else? Open an issue — small skill, fast PRs.
Forks, PRs, and issues all welcome.
- Fork the repo
- Edit any prompt in
pipeline/or extendSKILL.md - Test locally — install your fork, run
/planmysaason a few different ideas - Open a PR with the test inputs + screenshots of the output
Especially welcome:
- Better default prompts for any stage (PRs that produce sharper, more specific outputs win)
- Stage variants for specific verticals (B2B SaaS, marketplaces, mobile-first, AI tools)
- Localised versions of any prompt
- Bug fixes when Claude misinterprets a stage instruction
None. The skill runs entirely in your Claude Code session. No analytics, no phone-home, no API calls (in v1). The only network the skill touches is whatever Claude already does for you.
MIT — see LICENSE. Fork it, ship it, sell it, build a company on it. Just don't blame us if Claude generates a strange tagline once in a while.
Built by @creationskiro · made for Claude Code · part of the PlanMySaaS ecosystem.
If you ship something with the skill, post it on X and tag @planmysaas. We are collecting the best blueprints from the first month and featuring them on the homepage. The earliest community projects get a free year of the dashboard's Pro tier.