Just dropped · v1.0.0 · MIT

PlanMySaaS Claude Skill
one install, one slash command, eight markdown files

Clone the repo into ~/.claude/skills/, then run /planmysaas "<your idea>" inside Claude Code. Get a complete 8-stage blueprint locally — no API key, no signup, fully open.

Installgit clone https://github.com/creationskiro/planmysaas-claude-skill ~/.claude/skills/planmysaas
Run/planmysaas "quiet-hours SMS scheduler for solo founders"
Star on GitHubRead the launch story
MIT licensed·0 dependencies·No API key, no signup·v1.0.0 release
What you get

Eight stages, one folder

Every stage is a separate markdown file in your project. You can edit any one and re-run downstream stages.

01

Idea refine

Audience, business model, founder rules, success criteria.

02

Research

Competitors, problem clusters, market gaps, strategic direction.

03

Analysis

PMF score, SWOT, TAM/SAM/SOM, Porter's 5F, BMC, GTM strategy.

04

Architecture

Containers, services, data models, API surface, integrations.

05

Features

Per-feature specs: purpose, user flow, acceptance criteria, edge cases.

06

Frontend

Routes, page specs, wireframes, component tree, design system.

07

Phases

Foundation → MVP → launch → growth → scale, with risk register.

08

Build playbook

New

Decision-grade, rubric-graded build steps. Leaf to root, dependency-ordered.

The differentiator

Stage 8 is a build playbook, not a prompt pack

Most planners end with "here's a prompt pack, good luck." Stage 8 ships 9–12 dependency-ordered build steps (leaf to root), each with a testable rubric. Treat it as a senior engineer's runbook.

🎯
Goal
What this step exists to achieve.
📥
Inputs
Concrete IDs from earlier stages.
📤
Outputs
Files, schemas, API contracts produced.
✅
Acceptance rubric
8–14 testable boxes. No vague phrasing.
⚠️
Edge cases
What breaks, and how to handle each.
❌
Common pitfalls
Anti-patterns to avoid, with reasons.
📊
Quality bar
Performance / security / UX thresholds.
🛑
Stop-and-review gate
Don't advance until every box passes.
Skill vs Dashboard

Same pipeline, different surface

The skill IS the full 8-stage pipeline. The dashboard adds rendered pages, charts, version history, exports, and team workspaces.

SurfaceClaude Skill (this)Dashboard (planmysaas.com)
Installgit clone, 5 secondsSign up, free tier
Where artifacts liveYour repo as markdownWeb app + exports
Stages88 + 30+ rendered pages
Stage 8Decision-grade rubricSame — plus interactive checklist
Charts (recharts)Markdown tablesLive charts (bar, dial, score)
Architecture diagramMarkdownDrag-able 29-node canvas
Version historyUse gitBuilt-in diff per stage
Re-run a stageRe-run skillOne click + per-stage feedback
Team workspaces—Yes, with roles
ExportsMarkdown onlyPDF / JSON / ZIP / share link
LicenseMIT, open sourceCommercial, hosted
CostFreeFree tier + paid plans
Common questions

FAQ

Do I need an API key or signup?
No. The skill is plain markdown — install with git clone and run /planmysaas inside Claude Code. No accounts, no telemetry, no API keys.
What does the skill cost?
Nothing. MIT licensed, fully open source. The hosted dashboard at planmysaas.com is paid (with a free tier of 100 credits) but the skill is free forever.
Why is Stage 8 a rubric instead of a prompt pack?
Most AI planners end with 'here's a prompt pack, good luck' — a gap where most projects die. Stage 8 is rewritten as 9–12 dependency-ordered build steps (leaf to root), each with goal, inputs, outputs, an 8–14 box acceptance rubric, edge cases, common pitfalls, quality bar, and a stop-and-review gate. Treat it as a senior engineer's runbook.
Does it work outside Claude Code?
The skill is built for Claude Code's slash-command runtime. The output is plain markdown so any AI coding tool (Cursor, Windsurf, Bolt, v0, Lovable) can consume the generated blueprint files — but the /planmysaas command runs inside Claude Code.
How do I update the skill?
cd ~/.claude/skills/planmysaas && git pull. Releases follow semver — see the GitHub releases tab.
Can I customise the prompts?
Yes — that's the point of being open source. Fork the repo, edit any file in pipeline/, and the skill picks up your changes immediately. Send a PR if your variant should ship for everyone.
Will my data leave my machine?
The skill itself makes zero network calls. All generation happens through your Claude Code session, which is governed by Anthropic's usage policy — not by us.

Five seconds to install.
One slash command to ship.

Star the repo, install the skill, run it on your idea. If it breaks, open an issue. If you fix it, open a PR.

View repo on GitHubSee the dashboard version
v1.0.0 · MIT · 0 dependencies · works inside Claude Code today