Help us improve
Share bugs, ideas, or general feedback.
Turns ideas into buildable feature specs, project scopes, requirements, or MVP definitions. Guides quick workflows for AI builds and full scopes for planning and estimates.
npx claudepluginhub whawkinsiv/solo-founder-superpowers --plugin solo-founder-superpowersHow this skill is triggered — by the user, by Claude, or both
Slash command
/solo-founder-superpowers:planThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Turn ideas into specs that AI tools can execute and stakeholders can evaluate.
Generates project specs at optimal depth: quick Linear issues for tasks, lite PRDs for features, AI specs with context, evals. Use /spec shortcuts like --quick or --ai.
Translates vague ideas, feature requests, and bug reports into structured dev briefs, PRDs, user stories, and acceptance criteria. Stack-agnostic.
Guides users through structured dialogue to turn fuzzy ideas into concrete, implementation-free project specs. Focuses on WHAT/WHY, never HOW.
Share bugs, ideas, or general feedback.
Turn ideas into specs that AI tools can execute and stakeholders can evaluate.
Quick Feature Spec (10-15 minutes)
Full Project Scope (1-2 hours)
Use this checklist and complete each section:
Feature Spec Progress:
- [ ] Write what users will do (2-3 sentences)
- [ ] Show what it looks like (reference, screenshot, or description)
- [ ] Define happy path (3-5 steps)
- [ ] List edge cases (2-4 scenarios)
- [ ] Specify out of scope items
- [ ] Save to docs/specs/YYYY-MM-DD-feature-name.md
Write 2-3 sentences describing user actions and outcomes.
Template:
Users can [ACTION] to [OUTCOME].
When they [DO THIS], they see [WHAT HAPPENS].
If [EDGE CASE], then [WHAT HAPPENS].
Example:
Users sign up with email/password, receive confirmation email, and log in to
see their dashboard. They can reset forgotten passwords via email link.
Pick ONE:
List 3-5 steps users take to complete the task.
List 2-4 scenarios where things don't go as planned and what happens.
Format:
- **[Scenario]:** [Response shown to user]
Define what you're NOT building to prevent scope creep.
For complete template and examples, see QUICK-SPEC.md
Use this checklist for comprehensive project planning:
Project Scope Progress:
- [ ] Write introduction (background, in/out of scope)
- [ ] Define user roles
- [ ] List all pages/screens
- [ ] Describe core features
- [ ] Identify integrations
- [ ] Create milestones with hour estimates
- [ ] Document assumptions and open questions
- [ ] Save to docs/specs/YYYY-MM-DD-project-name.md
For complete template and examples, see PROJECT-SCOPE.md
Claude Code / Cursor:
Build this feature: [paste Quick Feature Spec]
Lovable / Replit / Bolt:
Hiring contractors:
| Mistake | Fix |
|---|---|
| "Build a dashboard" | Describe what's ON dashboard and what each thing does |
| Describing HOW to code it | Describe WHAT it should do |
| Forgetting mobile | Add "Works on mobile" to every spec |
| Skipping edge cases | Define what happens when things break |
| No out-of-scope | Prevents scope creep |
"I don't know what I want yet"
"AI keeps building the wrong thing"
Save as: docs/specs/YYYY-MM-DD-feature-name.md
Then:
✅ AI builds it right first time (or very close) ✅ Contractors give realistic estimates without surprises ✅ Edge cases don't surprise you in production ✅ Stakeholders know exactly what they're getting