Break down a book roadmap topic into prioritized milestone and task proposals, considering reader impact, scope, dependencies, and effort. The skill outputs text for a separate board workflow to apply; it does not write board files.
Propose milestones and tasks for the repository's public .pm board — decompose a topic through the editor's reader-impact lens, size and gate the work, and emit a text-only proposal for /pm to materialize. Use only when the user explicitly invokes /pm-brainstorm or asks to brainstorm, plan, or break down book roadmap work. Not for writing board files (that is pm) or ordinary chapter edits.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Usage: /pm-brainstorm <topic or goal to break down>
The divergent half of the pair: think a topic through, propose work, hand materialization to /pm. It writes nothing. Conventions (pillars B1/B2/B3, hierarchy, sizing, closing tasks, templates) live in ../pm/SKILL.md — read and apply them; do not restate or diverge.
Minimum proposal size: at least 5 distinct, actionable top-level candidates (milestones and/or inbox notes) that pass scope, anti-goal, dedup, sizing and quality rules. Don't pad or artificially split.
.agents/skills/pm/SKILL.md and .pm/DO_NOT_DO.md. Reject conflicting candidates explicitly.git fetch origin, git status; fast-forward only when behind and clean. Never block on a dirty/diverged tree.find .pm -name README.md, loose notes, done/ and blocked/) so proposals fit and don't duplicate shipped work. Ground truth for the book is the repo itself: README.md, SUMMARY.md, zh-CN/README.md, the relevant en/ chapters, drafts/, and awesome-system-design.md. Check that a candidate chapter doesn't already exist (ls en | grep, grep -il), and what the en/zh-CN parity gap actually is (diff <(ls en) <(ls zh-CN)).depends_on./pm's rules. Undersized → inbox note. Fails the gate → "not meaningful" with a better-scoped alternative./pm appends closing tasks; flag whether you expect Reader surface to apply.N. <title> (wN, ~size) — one-line outcome./pm invocations (/pm new milestone w1 <title>, /pm add w1 <idea>, /pm promote w1/NNN).$ARGUMENTS
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Answer questions about a book, its chapters, or system design by consulting relevant material without changing files. For repository questions, ground the response in the source and cite file paths and lines; use web search for general topics when freshness matters.
Work through a `.pm` workstream backlog one actionable item at a time. Triage pending milestones, tasks, and inbox notes, then implement and ship them, close items already satisfied, block work with an unblock condition, or remove invalid items until no actionable work remains.
Create concise Mermaid architecture diagrams from a chapter, system, component, dependency flow, or supplied description. The skill checks the diagram syntax before presenting the diagram and a brief explanation of its key flow.
Manage and inspect a book project's public work board: organize workstreams, notes, milestones, and tasks, and update their status as work changes. Use it to materialize proposals, track blockers, or check current board state.
Prepare pending changes on the tracked working branch for publishing: check the branch and repository state, rebase on the latest origin changes, commit selected files, and push. It is intended for an explicit ship or publish request.