one-pager
Skill3 starsChanged 19 days agoMITView on GitHub
Help PMs write feature one-pagers — lighter than a PRD, used for quick alignment. Use when you need to align stakeholders without a full spec.
12 other projects use a version of this.
Adopted by
Most recently taken up by
- CSPulse/customer-success-skillstheir own version, first seen Nov 8, 2026
- plannotator/effective-htmltheir own version, first seen Nov 1, 2026
- backnotprop/brotheir own version, first seen Nov 1, 2026
- JScottCarter/Claude_skillstheir own version, first seen Oct 11, 2026
- youdcode/open-companytheir own version, first seen Sep 21, 2026
- montgomery-pixel/leadgen-skillstheir own version, first seen Sep 15, 2026
Other versions12 projects use a version of this.
Word for word · 1
- ianklassen/ai-pm-system★ 1100% same
Edited · 0
None found.
Wrote their own version · 11
- plannotator/effective-html★ 3.8ksame name
- backnotprop/bro★ 176same name
- GTMify/aigtm★ 25same name
- 0xelitesystem/claude-skills-templates★ 2same name
- CSPulse/customer-success-skills★ 2same name
- ouachitalabs/skills★ 2same name
- youdcode/open-company★ 2same name
- jingjing-yxng/claude-skills★ 0same name
- JScottCarter/Claude_skills★ 0same name
- kwana117/claude-skills★ 0same name
1 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/agents.mdAGENTS.md
- company-product-signalsSkill
- company-researcherSkill
- company-strategySkill
- pm-os-onboardingSkill
- brainstormingSkill
- continual-learningSkill
- decision-loggerSkill
- eval-briefSkill
- exec-communicatorSkill
- experiment-designerSkill
- experiment-writeupSkill
- knowledge-updaterSkill
- launch-postSkill
- launch-readinessSkill
- meeting-to-actionsSkill
- pptx-creatorSkill
- prd-writerSkill
- stakeholder-updateSkill
- strategy-connectorSkill
- what-ifSkill
- working-backwardsSkill
- writing-clearlySkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
When a full PRD is overkill
- Distinctive: line 62
No more than 5–7 sections
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
One-Pager
Help PMs write feature one-pagers: lightweight alignment documents that capture the essentials without the full structure of a PRD. Ideal for quick buy-in and shared understanding.
When to Use
- Aligning stakeholders before a full PRD
- Pitching a new feature or initiative
- Quick spec for a small scope
- When a full PRD is overkill
- Exploratory or early-stage ideas
Process / Template
1. Gather Core Information
- What is the feature or initiative?
- Who is it for? (persona/segment)
- What problem does it solve?
- What does success look like? (metric or outcome)
- What's the proposed approach?
2. Use the One-Pager Structure
Title & One-Liner
- Feature name and 1-sentence description
Problem
- Customer problem (1–2 sentences)
- Optional: business problem or opportunity
Proposed Solution
- What we're building (3–5 bullets)
- Key flows or changes
- Out of scope (what we're not doing)
Success Metrics
- Primary metric and target
- How we'll measure
Risks & Assumptions
- Key assumptions we're making
- Risks or unknowns
Timeline
- High-level milestones (optional)
- Target launch or phase
Open Questions
- Decisions needed
- Dependencies to resolve
3. Keep It Tight
- Aim for 1 page (or equivalent in markdown)
- Bullets over paragraphs
- No more than 5–7 sections
- Skip implementation detail
4. Validate Alignment
- Does it answer: What? Why? Who? How we'll know?
- Can a stakeholder understand it in 2 minutes?
- Are open questions explicit?
Output
A One-Pager document that:
- Fits on one page or screen
- Enables quick alignment
- Can be expanded into a PRD later
- Serves as a shared reference for the team
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.