Menu
Create concise one-page briefs for quick alignment and stakeholder decisions. Use when: one pager, feature brief, quick spec, feature proposal.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when executing implementation plans with independent tasks in the current session
| name | one-pager-creator |
| description | Create concise one-page briefs for quick alignment and stakeholder decisions. Use when: one pager, feature brief, quick spec, feature proposal. |
Create concise one-page briefs for quick alignment and stakeholder decisions.
First, read the user's context files:
context/product.md — Is this on the roadmap? What's the current state?context/personas.md — Who has this problem? What's the impact?context/company.md — Strategic priorities this aligns with?context/competitors.md — Competitive pressure to cite?Tell the user what you found. For example:
"I found 'Advanced Reporting' in your product.md as a known issue. Your Alex persona (agency owner) cites lack of profitability visibility as a pain point. I'll frame the one-pager around this evidence."
Before generating, verify you have:
If any are missing, ask:
"Before I create this one-pager, I need to understand:
- What problem or opportunity are we addressing? (I found [X] in your files — is that it?)
- What's your ask — approval, resources, feedback, or awareness?
- Who will read this — execs, eng leads, or cross-functional stakeholders?"
What do you need from the reader?
One page means:
# [Project/Feature Name] — One-Pager
**Author:** [Name]
**Date:** [Date]
**Status:** [Draft/Review/Final]
**Ask:** [Decision needed]
**Decision Deadline:** [Date]
## Context
*What I found in your files:*
- **Problem evidence:** [From personas.md, product.md]
- **Strategic alignment:** [From company.md]
- **Competitive factor:** [From competitors.md if relevant]
---
## Problem
[2-3 sentences: What problem exists? Who has it? What's the impact?]
**Evidence:**
- [From personas.md — user pain point]
- [From product.md — known issue, feedback]
- [From competitors.md — competitive gap if relevant]
## Proposed Solution
[2-3 sentences: What are we proposing at a high level?]
## Why Now?
- [Strategic alignment — from company.md priorities]
- [Competitive pressure — from competitors.md]
- [Opportunity cost of waiting]
## Expected Impact
| Metric | Current | Target | Confidence |
|--------|---------|--------|------------|
| [Metric] | [From product.md] | [Target] | High/Med/Low |
## Key Risks
- [Risk 1] — Mitigation: [Plan]
- [Risk 2] — Mitigation: [Plan]
## Open Questions
- [ ] [Question that needs answering]
## The Ask
[Specifically what you need from the reader — approval, resources, feedback]
## Next Steps (if approved)
1. [Step 1]
2. [Step 2]
Based on Lenny Rachitsky's one-pager format: