Turns ideas into quick feature specs (10-15 min) for AI builds and full project scopes (1-2 hrs) for stakeholders, estimates, and planning. Covers user flows, edge cases, milestones.
npx claudepluginhub whawkinsiv/solo-founder-superpowers --plugin solo-founder-superpowersThis skill uses the workspace's default tool permissions.
Turn ideas into specs that AI tools can execute and stakeholders can evaluate.
Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.
Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.
Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.
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