template-designer
Turn a document the team keeps rewriting into a template that actually helps — extract the recurring skeleton, mark what varies with real placeholder prompts, keep it lighter than the ceremony it replaces, and pilot it before decreeing it. Use when asked make a template from this doc, we write this same thing every week, standardize our status updates or briefs, or why does nobody use our templates. Produces the extracted template with prompting placeholders, the keep-it-light rules, the example-filled twin, and the adoption path.
npx skills add mohitagw15856/pm-claude-skills --skill template-designer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Template Designer Skill Templates fail in two familiar ways: the empty-headings ghost (`## Background` — helpfully blank) that guides nobody, and the forty-field bureaucratic form that takes longer than freeform writing did. A working template is extracted from documents the team *already writes repeatedly*, keeps only the sections that recur with purpose, and — the difference-maker — its placeholders are *prompts* ("One sentence: what changed since last update, and does the date still hold?") rather than labels ("Update:"). It ships with a filled example, because the example teaches what the skeleton can't. ## What This Skill Produces - **The template** — the recurring skeleton with prompting placeholders, each section justified by recurrence - **The filled twin** — a realistic example completed end-to-end; templates travel in pairs or don't travel - **The light-ness audit** — what was deliberately left out, and the freeform escape-hatch section - **The adoption path** — pilot with the next real instance, revise from friction, then propose as default (not decree) ## Required Inputs Ask for these if not provided: - **The recurring documents** — 3+ past instances of the thing bein
- What This Skill Produces
- Required Inputs
- Framework: The Design Rules
- Output Format
- The Template
- The Filled Twin
- The Light-ness Audit
- Adoption Path
- Quality Checks
- Anti-Patterns
What does the template-designer skill do?
Turn a document the team keeps rewriting into a template that actually helps — extract the recurring skeleton, mark what varies with real placeholder prompts, keep it lighter than the ceremony it replaces, and pilot it before decreeing it. Use when asked make a template from this doc, we write this same thing every week, standardize our status updates or briefs, or why does nobody use our templates. Produces the extracted template with prompting placeholders, the keep-it-light rules, the example-filled twin, and the adoption path.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill template-designer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.