跳到正文
cccskills
免费在 GitHub 公开

pm-brainstorm

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.

puncsky/system-design-and-architecture星标 3,606(GitHub 3,606 + cccskills 0)

实测评分 未实测

查看安装方法

适用场景

  • Turn a book improvement idea into milestone proposals
  • Prioritize roadmap work by reader impact
  • Break a goal into sized tasks with dependencies

包含的文件(1)

  • SKILL.md3.2 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Task: Propose milestones and tasks

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.

Steps

  1. Load canon and anti-goals. Read .agents/skills/pm/SKILL.md and .pm/DO_NOT_DO.md. Reject conflicting candidates explicitly.
  2. Sync if safe. git fetch origin, git status; fast-forward only when behind and clean. Never block on a dirty/diverged tree.
  3. Load context. Read the board (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)).
  4. Apply the editor's lens. For each candidate answer: Pillar (B1/B2/B3, else out); Reader (interview candidate, practicing engineer, translator/contributor); Friction removed (what they can now learn/find/trust); Signal (site traffic, GitHub stars/issues, reader feedback, build passing). Prefer compounding assets (fixing a template, parity tooling, a TOC) over one-off prose; prefer fixing wrong/outdated content over adding more.
  5. Discuss & decompose. Pressure-test scope, surface dependencies/risks; break into tasks with estimates and depends_on.
  6. Size and gate by /pm's rules. Undersized → inbox note. Fails the gate → "not meaningful" with a better-scoped alternative.
  7. Emit text only. Full detail first: target queue and why, each milestone (task table, definition of done, source, pillar, outcome, why-now) or inbox note, in proposed priority order. Implementation tasks only — /pm appends closing tasks; flag whether you expect Reader surface to apply.
  8. End with exactly two blocks, nothing after:
    1. "Summary (priority order)" — N. <title> (wN, ~size) — one-line outcome.
    2. The exact /pm invocations (/pm new milestone w1 <title>, /pm add w1 <idea>, /pm promote w1/NNN).

Topic

$ARGUMENTS

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

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.

中文简介正在准备中。当前显示英语简介。

  • Asking about a book or chapter
  • Getting an explanation of system design
  • Checking repository material without edits
puncsky/system-design-and-architecture36062026年10月23日 更新

loopx

免费

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.

中文简介正在准备中。当前显示英语简介。

  • Draining a workstream backlog
  • Reviewing pending milestones and tasks
  • Resolving open inbox notes
puncsky/system-design-and-architecture36062026年10月23日 更新

mermaid

免费

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.

中文简介正在准备中。当前显示英语简介。

  • Diagramming a system or its components
  • Showing dependency and call directions
  • Turning a chapter topic into a diagram
puncsky/system-design-and-architecture36062026年10月23日 更新

pm

免费

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.

中文简介正在准备中。当前显示英语简介。

  • Check open milestones, tasks, and blockers
  • Add a roadmap note or milestone to the board
  • Mark completed or blocked work
puncsky/system-design-and-architecture36062026年10月23日 更新

ship

免费

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.

中文简介正在准备中。当前显示英语简介。

  • Publish finished changes from the current branch
  • Commit and push selected pending files
  • Update the branch with origin before shipping
puncsky/system-design-and-architecture36062026年10月23日 更新

查看 puncsky 的全部技能

报告此技能的问题