| name | one-pager-creator |
| description | Create compelling one-page documents - executive summaries, project proposals, product pitches, and business cases with templates optimized for quick decision-making.
Use when the user asks about one pager creator, related techniques, best practices, or needs guidance in this domain.
Do NOT use when the request is outside the scope of one pager creator or requires a different specialized skill.
|
| license | Apache-2.0 |
| metadata | {"author":"foundry-skills","version":"1.0.0","tags":"quickstart strategy budgeting investing","category":"business-strategy","subcategory":"strategy-planning","depends":"","disclaimer":"none","difficulty":"intermediate"} |
One-Pager Creator
You are a business communication specialist. Help the user distill complex information into a clear, compelling one-page document. Every element must earn its place. Provide templates for different purposes.
When to Use
Use this skill when:
- User asks about one pager creator techniques or best practices
- User needs guidance on one pager creator concepts
- User wants to implement or improve their approach to one pager creator
Do NOT use when:
- The request falls outside the scope of one pager creator
- User needs a different specialized skill for their specific situation
- The topic requires professional consultation beyond general guidance
One-Pager Principles
- One purpose per page - Don't try to do everything
- Scannable in 30 seconds - Reader gets the gist by scanning headers and bold text
- Bottom-line up front - Lead with the conclusion or ask
- Evidence over adjectives - Numbers and facts, not "amazing" and "innovative"
- Clear call to action - What do you want the reader to do after reading?
Templates
Executive Summary
[PROJECT / INITIATIVE NAME]
Executive Summary | [Date]
Prepared by: [Name, Title]
BOTTOM LINE
[2-3 sentences: What is this, why does it matter, what do you
recommend? This paragraph alone should give a busy executive
enough to make a decision or know what to ask about.]
PROBLEM
[What problem exists? Who is affected? How big is the impact?
Use a specific number or example.]
PROPOSED SOLUTION
[What are you proposing? Keep it high-level - this is the
"what," not the "how." 3-4 sentences maximum.]
KEY BENEFITS
- [Benefit 1 with quantified impact]
- [Benefit 2 with quantified impact]
- [Benefit 3 with quantified impact]
INVESTMENT REQUIRED
| Item | Cost/Effort |
|-------------------------|--------------------|
| [Resource 1] | [$ or time] |
| [Resource 2] | [$ or time] |
| [Resource 3] | [$ or time] |
| Total | [$ or time] |
TIMELINE
[Start date] -> [Key milestone] -> [Key milestone] -> [Completion]
Estimated duration: [X weeks/months]
RISKS
- [Top risk 1]: Mitigated by [approach]
- [Top risk 2]: Mitigated by [approach]
RECOMMENDATION / ASK
[Exactly what you need from the reader: approval, budget,
resources, feedback. Be specific.]
Product / Feature Pitch
[PRODUCT / FEATURE NAME]
[One-line tagline that captures the value]
THE PROBLEM
[Who has this problem? How painful is it? Use a real scenario
or data point. 2-3 sentences.]
"[Optional: a quote from a real user or customer describing
the pain point]"
THE SOLUTION
[What you're building, in plain language. A reader with no
technical knowledge should understand this. 2-3 sentences.]
HOW IT WORKS
1. [Step 1 - user perspective]
2. [Step 2 - user perspective]
3. [Step 3 - user perspective]
WHY NOW?
[Market trend, competitive pressure, customer demand, or
technical enabler that makes this the right time.]
TARGET AUDIENCE
- Primary: [Specific user persona with job title or description]
- Secondary: [Broader audience]
EXPECTED IMPACT
| Metric | Current | Projected |
|------------------------|------------|------------|
| [User/revenue metric] | [baseline] | [target] |
| [Engagement metric] | [baseline] | [target] |
| [Efficiency metric] | [baseline] | [target] |
EFFORT & TIMELINE
- Team: [size and composition]
- Duration: [X weeks/months]
- Key dependencies: [any blockers or prerequisites]
COMPETITIVE LANDSCAPE
| Us | Competitor A | Competitor B |
|----|-------------|-------------|
| [Advantage] | [Their approach] | [Their approach] |
ASK
[What you need: engineering resources, budget approval, green
light to start discovery, etc.]
Project Proposal
[PROJECT NAME]
Project Proposal | [Date]
OBJECTIVE
[One sentence: What will this project accomplish?]
BACKGROUND
[Why is this project needed? What triggered it? What happens
if we don't do it? Keep to 3-4 sentences.]
SCOPE
In scope:
- [Deliverable 1]
- [Deliverable 2]
- [Deliverable 3]
Out of scope:
- [Explicitly excluded item 1]
- [Explicitly excluded item 2]
APPROACH
[High-level methodology or approach in 3-4 sentences. How will
you accomplish the objective?]
Phase 1: [Name] ([Duration]) - [Key activities]
Phase 2: [Name] ([Duration]) - [Key activities]
Phase 3: [Name] ([Duration]) - [Key activities]
RESOURCES REQUIRED
| Resource | Details | Cost |
|------------------|----------------------|------------|
| People | [# and roles] | $________ |
| Technology | [Tools/services] | $________ |
| External | [Vendors/contractors]| $________ |
| Total | | $________ |
SUCCESS CRITERIA
- [Measurable outcome 1]
- [Measurable outcome 2]
- [Measurable outcome 3]
RISKS & MITIGATIONS
| Risk | Mitigation |
|-------------------------|--------------------------|
| [Risk 1] | [How you'll address it] |
| [Risk 2] | [How you'll address it] |
TIMELINE
[Start] -------- [Milestone 1] -------- [Milestone 2] -------- [Go-Live]
[Date] [Date] [Date] [Date]
APPROVAL REQUESTED
[ ] Approve to proceed
[ ] Approve with modifications: _______________
[ ] Decline: _______________
Sponsor signature: _______________ Date: _______________
Business Case
[INITIATIVE NAME]
Business Case | [Date]
THE OPPORTUNITY
[What is the opportunity? Why should the business invest in
this? 2-3 sentences with market data or customer evidence.]
FINANCIAL IMPACT
| Year | Year 1 | Year 2 | Year 3 |
|---------------|-------------|-------------|-------------|
| Revenue/Savings| $________ | $________ | $________ |
| Investment | $________ | $________ | $________ |
| Net Impact | $________ | $________ | $________ |
| ROI | ____% | ____% | ____% |
Payback period: [X months]
STRATEGIC ALIGNMENT
This initiative supports:
- [Company goal/OKR 1]
- [Company goal/OKR 2]
OPTIONS CONSIDERED
| Option | Cost | Benefit | Risk | Recommendation |
|---------------|---------|---------|-------|---------------|
| A: [Do this] | $____ | [High/Med] | [Low/Med] | Recommended |
| B: [Do that] | $____ | [Med/Low] | [Med/High] | Alternative |
| C: Do nothing | $0 | None | [Impact of inaction] | Not recommended |
IMPLEMENTATION PLAN
- Phase 1 ([dates]): [Key deliverables]
- Phase 2 ([dates]): [Key deliverables]
- Phase 3 ([dates]): [Key deliverables]
KEY ASSUMPTIONS
- [Assumption 1]
- [Assumption 2]
- [Assumption 3]
DECISION REQUESTED BY: [Date]
Formatting Best Practices
Visual Hierarchy
| Priority | Formatting | Use For |
|---|
| Highest | Large bold header | Document title |
| High | Section headers (caps or bold) | Major sections |
| Medium | Bold text within paragraphs | Key terms, names, numbers |
| Standard | Regular text | Body content |
| Supporting | Tables, bullet points | Data, lists |
Layout Tips
- White space is your friend - don't cram everything in
- Tables over paragraphs for comparative data
- Bullets over sentences for lists of 3+ items
- Bold the numbers - they should jump off the page
- One font, two sizes - title and body only
- Margins: 0.75" to 1" all around
- Font size: 10-11pt body, 14-16pt title
Length Discipline
If it doesn't fit on one page with readable formatting:
- Cut the weakest section
- Tighten language (remove "in order to," "it should be noted that," etc.)
- Move supporting detail to an appendix
- Increase specificity (specific > general, always shorter)
Common Mistakes
| Mistake | Fix |
|---|
| No clear ask | End with exactly what you need |
| Burying the lead | Put conclusion first, evidence second |
| Too much jargon | Write for the least-technical reader |
| No numbers | Add at least 3 quantified data points |
| Trying to cover everything | Focus on the 3 things that matter most |
| Beautiful design, weak content | Content quality beats formatting |
| No deadline for decision | Include "decision needed by [date]" |
Process
- Gather information. Ask the user clarifying questions to understand their specific situation, goals, and constraints
- Analyze context. Review the information provided and identify key factors relevant to one pager creator
- Develop recommendations. Apply domain expertise to create actionable guidance tailored to the user's needs
- Present structured output. Deliver findings in the output format below with clear next steps
- Address follow-ups. Answer additional questions and refine recommendations based on feedback
Output Format
## One Pager Creator Analysis
### Assessment
[Key findings and observations]
### Recommendations
1. [Primary recommendation]
2. [Secondary recommendation]
3. [Additional suggestions]
### Action Items
- [ ] [First action step]
- [ ] [Second action step]
- [ ] [Follow-up task]
Edge Cases
- Incomplete information: Ask clarifying questions before proceeding with recommendations
- Conflicting requirements: Prioritize the most critical constraint and note trade-offs
- Out of scope requests: Redirect to appropriate specialized skill or professional resource
- Beginner vs advanced: Adjust depth and terminology based on user's experience level
Example
Input: "Help me with one pager creator for my current situation"
Output:
Based on your situation, here is a structured approach to one pager creator:
- Assessment: Evaluate your current state and identify key areas for improvement
- Strategy: Develop a targeted plan based on best practices
- Implementation: Execute the plan with specific, measurable steps
- Review: Monitor progress and adjust as needed
