Agent skill
create-saas
Complete SaaS ideation to implementation workflow - from idea discovery to task breakdown
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/create-saas
SKILL.md
This workflow responds in the user's language while prompts are in English. It's designed for solo developers learning Next.js with Prisma and Better-Auth who want to build a monetizable SaaS in less than 2 weeks.
<quick_start> Start a new SaaS project (interactive discovery):
/create-saas
With custom project name:
/create-saas my-awesome-saas
Continue existing project:
/create-saas -c my-awesome-saas
What it does:
- Discovery: Ask questions to understand your background
- Brainstorm: Generate 3-6 validated SaaS ideas
- Validate: Challenge and refine your chosen idea
- PRD: Create Product Requirements Document
- Architecture: Design technical stack (Next.js + Prisma + Better-Auth)
- Tasks: Break down into actionable implementation tasks
Outputs saved to ~/.claude/output/saas/{project-id}/
</quick_start>
Flags:
-a/-A- Auto mode: skip confirmations (default: false)-s/-S- Save mode: save outputs to files (default: true)-c <project-id>- Continue mode: reload existing project and resume where you left off
<state_variables> Core Variables (persist throughout all steps):
| Variable | Type | Description |
|---|---|---|
{project_name} |
string | SaaS project name |
{project_id} |
string | Kebab-case identifier for folders |
{auto_mode} |
boolean | Skip confirmations |
{save_mode} |
boolean | Save outputs to files |
{output_dir} |
string | Path to output folder |
{user_language} |
string | User's preferred language |
Accumulated State (grows across steps):
| Variable | Set In | Description |
|---|---|---|
{discovery_answers} |
Step 1 | User's answers to discovery questions |
{has_previous_project} |
Step 1 | Whether user built a project before |
{ideas} |
Step 2 | List of 3-6 brainstormed ideas |
{selected_idea} |
Step 2 | User's chosen idea |
{validated_idea} |
Step 3 | Fully developed and validated idea |
{prd_content} |
Step 4 | Product Requirements Document |
{architecture} |
Step 5 | Technical architecture decisions |
{tasks} |
Step 6 | List of implementation tasks |
</state_variables>
<entry_point>
Load steps/step-00-init.md
</entry_point>
<step_files>
| Step | File | Description |
|---|---|---|
| 0 | steps/step-00-init.md |
Initialize: parse flags, create output folder |
| 1 | steps/step-01-discovery.md |
Discovery: ask questions to find the right idea |
| 2 | steps/step-02-brainstorm.md |
Brainstorm: generate 3-6 ideas, user chooses one |
| 3 | steps/step-03-validate.md |
Validate: research, challenge, develop the idea |
| 4 | steps/step-04-prd.md |
PRD: create Product Requirements Document |
| 5 | steps/step-05-architecture.md |
Architecture: design technical stack |
| 6 | steps/step-06-tasks.md |
Tasks: split into actionable implementation tasks |
| </step_files> |
<workflow_diagram>
┌──────────────┐ ┌───────────────┐ ┌───────────────┐
│ Step 0 │────►│ Step 1 │────►│ Step 2 │
│ Initialize │ │ Discovery │ │ Brainstorm │
└──────────────┘ └───────────────┘ └───────┬───────┘
│
┌────────────────────────┘
│ ▲
▼ │ (if not validated)
┌───────────────┴─┐
│ Step 3 │
│ Validate │
└────────┬────────┘
│ (if validated)
▼
┌───────────────┐ ┌───────────────┐
│ Step 4 │────►│ Step 5 │
│ PRD │ │ Architecture │
└───────────────┘ └───────┬───────┘
│
▼
┌───────────────┐
│ Step 6 │
│ Tasks │
└───────────────┘
</workflow_diagram>
<output_structure>
When {save_mode} = true, creates:
~/.claude/output/saas/{project_id}/
├── discovery.md # Discovery answers and insights
├── idea.md # Validated idea with all details
├── prd.md # Product Requirements Document
├── archi.md # Technical Architecture
├── marketing.md # Marketing strategy notes
└── tasks/ # Implementation tasks
├── 01-setup.md
├── 02-auth.md
├── ...
</output_structure>
<success_criteria>
- Discovery questions answered and insights captured
- 3-6 validated SaaS ideas generated
- One idea selected and validated against market
- PRD created with clear problem, solution, and user stories
- Technical architecture defined (Next.js + Prisma + Better-Auth)
- Implementation tasks broken down and prioritized
- All outputs saved to
~/.claude/output/saas/{project-id}/ - Project ready to start implementation </success_criteria>
Scripts:
scripts/setup.sh <project_id>- Creates output folder structurescripts/rename-project.sh <old> <new>- Renames project and updates all project_id references
Base Project:
- NOW.TS boilerplate - User provides path during step-07 setup
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?