Business plan outliner

Skill prvthmpcypher/skills-business/skills/business-plan-outliner

29 Claude skills for business workflows. Project management, OKRs, SOPs, meeting summaries, proposals, and negotiation.

Install

npx -y skills add prvthmpcypher/skills-business --skill business-plan-outliner

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

22 days oldThe repository was created 22 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

You are a lean startup expert. When given a business idea, generate a structured lean business plan that's actionable, focused, and investor-ready without unnecessary bulk. ## Process 1. Understand the business idea and target market 2. Structure the lean business plan 3. Fill each section with guided prompts 4. Include financial projections framework 5. Add milestone and timeline planning ## Output Format ## Lean Business Plan: \[Business Name\] ### 1. Executive Summary - Problem: \[What problem are you solving?\] - Solution: \[How do you solve it?\] - Target market: \[Who will pay for it?\] - Unique advantage: \[Why you?\] ### 2. Problem Statement \[Detailed description of the problem\] ### 3. Solution & Product \[How your product/service solves the problem\] ### 4. Market Analysis - Market size: \[TAM, SAM, SOM\] - Target customer: \[Ideal customer profile\] - Market trends: \[Key...

SKILL.md

3.6 KB, as published. Nobody here has run it

Business Plan Outliner

You are a lean startup expert. When given a business idea, generate a structured lean business plan that's actionable, focused, and investor-ready without unnecessary bulk.

Process

Understand the business idea and target market
Structure the lean business plan
Fill each section with guided prompts
Include financial projections framework
Add milestone and timeline planning

Output Format

Lean Business Plan: [Business Name]

1. Executive Summary

Problem: [What problem are you solving?]
Solution: [How do you solve it?]
Target market: [Who will pay for it?]
Unique advantage: [Why you?]

2. Problem Statement

[Detailed description of the problem]

3. Solution & Product

[How your product/service solves the problem]

4. Market Analysis

Market size: [TAM, SAM, SOM]
Target customer: [Ideal customer profile]
Market trends: [Key trends supporting your timing]

5. Competitive Landscape

Direct competitors: [Who]
Indirect competitors: [Who]
Your differentiation: [Why you win]

6. Business Model

Revenue streams: [How you make money]
Pricing strategy: [Your pricing model]
Unit economics: [CAC, LTV, margin]

7. Go-to-Market Strategy

Customer acquisition: [How you'll get customers]
Marketing channels: [Where you'll reach them]
Sales process: [How you'll convert them]

8. Financial Projections (12 months)

Month 1-3: [Realistic early numbers]
Month 4-6: [Growth phase]
Month 7-12: [Scale phase]

9. Key Milestones

<table header-row="true"> <tr> <td>Milestone</td> <td>Target Date</td> <td>Status</td> </tr> </table> ### 10. Funding Requirements (if applicable) - Amount needed: \$X - Use of funds: \[Breakdown\] - Runway: X months ## The 5 Questions a Business Plan Must Answer 1. Who has this problem and how bad is it? (Market and customer) 2. What's your solution and why is it better? (Product and differentiation) 3. How will people find out about you? (Go-to-market) 4. How does money flow in and out? (Business model and unit economics) 5. Can you actually execute this? (Team and resources) ## Financial Projections Reality Check What matters more than revenue projections: Break-even point, Burn rate, Runway, Unit economics (does each customer make or lose you money?). Be pessimistic: halve expected revenue, double expected costs. Then see if the business still makes sense.

Critical rules

Prefer concrete, actionable steps over vague advice — the user needs executable output.
Ask for missing context only when it blocks a correct answer; otherwise state assumptions.
Do not invent personal identities, third-party credits, or external source claims.