Doc Writer

What It Does

You describe the problem or outcome; the skill infers the right document format and fills it with structured PM thinking—problem framing, goals, requirements, tradeoffs, and success criteria where they belong. No need to name the template first unless you want to. Output lands as markdown (or issue-ready text) so you can paste into Notion, Google Docs, or GitHub.

The 7 Formats

Concept One-Pager

New ideas, vision, and strategic bets—narrative-first, light on implementation detail.

Problem/Solution One-Pager

Enhancements to existing products: background, problem, requirements, and explicit non-goals.

Decision One-Pager

Choosing between options: recommendation, alternatives, tradeoffs, and kill criteria.

PRFAQ

Big launches and bets: press release plus external and internal FAQs to stress-test the story.

PRD / Structured Epic

Full specs: problem, goals, detailed requirements, milestones, and measurable success criteria.

Vision Epic

Direction-setting narrative that aligns teams on the north star without locking every story.

GitHub Issue

Engineering-ready issue body: context, acceptance criteria, and links—ready to paste or open via API.

Example Prompts

Write a one-pager for [feature]

Help me decide between A and B

Write a PRFAQ for [initiative]

Create an epic for [project]

Open an issue on org/repo for [feature]

How It Works

Parses your request and infers the format (or follows your explicit choice).
Gathers context—pulls from linked docs or repos when available, and asks clarifying questions when gaps would weaken the doc.
Loads the matching template and writes the full draft in that structure.
Saves output to the appropriate path in your workspace so version control and reviews stay easy.
Optionally runs persona-based review (e.g., CTO or GM lens) to tighten arguments before you share.