Install
$ agentstack add skill-prvthmpcypher-skills-business-business-plan-outliner ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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
Milestone Target Date Status
10. Funding Requirements (if applicable)
- Amount needed: \$X
- Use of funds: \[Breakdown\]
- Runway: X months
The 5 Questions a Business Plan Must Answer
- Who has this problem and how bad is it? (Market and customer)
- What's your solution and why is it better? (Product and differentiation)
- How will people find out about you? (Go-to-market)
- How does money flow in and out? (Business model and unit economics)
- 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.
Verification & Quality Checklist
- [ ] Every input figure traced to a named source with an as-of date.
- [ ] Arithmetic reconciles: components tie to totals, periods tie to the annual figure.
- [ ] Each assumption stated explicitly with a plausible range, not a single point.
- [ ] Sensitivity shown on the three drivers with the largest effect on the result.
- [ ] Units, currency, and time period labelled on every figure presented.
Anti-Patterns & Constraints
- NEVER present a point estimate without the assumptions behind it.
- NEVER mix fiscal and calendar periods without labelling which is which.
- NEVER imply licensed tax, audit, or investment advice - state the boundary.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: prvthmpcypher
- Source: prvthmpcypher/skills-business
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.