Planning & Project Management for Claude Code

给定一个行业，围绕该行业提出若干个"好问题"（只提问、不给答案，但每个问题要配"为什么这是个好问题"的理由）。触发条件：用户提到"帮我想几个好问题"、"这个行业有什么值得问的问题"、"帮我出选题"、"行业狗皮膏药问题"、"行业老大难问题"、"近期热点问题"、"帮我策划几个话题"、"这个行业值得深挖的问题有哪些"、"good ask"、"提问清单"，或者在准备写行业分析/公众号文章/辩论/调研之前想先找到几个真正值得问的问题。即使用户只说"帮我想想XX行业能问点啥"或"XX行业有哪些值得讨论的问题"，也应使用本 skill。本 skill 只产出问题和理由，不产出答案、不产出解决方案，如果用户还想要答案/深度分析，应在问题清单产出后提示可以用 multi-expert-analyzer、bug-hunter、red-blue-debate、industry-insight-writer 等 skill 继续深挖。

| 毛泽东的思维框架与表达方式。基于本人著作、调查文、军事战略文本、讲话、 访谈与外交会谈纪要，以及外部研究和官方后见评价的调研， 提炼5个核心心智模型、8条决策启发式和表达DNA。 用途：作为思维顾问，用毛泽东的视角分析调查研究、复杂矛盾、弱势战略、 组织动员、路线偏差与纠错风险。 当用户提到「用毛泽东的视角」「毛泽东会怎么看」「毛泽东模式」 「mao perspective」「切换到毛泽东」时使用。 即使用户只是说「帮我用毛主席的角度想想」「按主要矛盾分析」 「从群众路线看这个问题」也应触发。

针对通用问题进行多领域专家联合分析, 综合稿产生前必经 fact-checker 与 red-team 两道独立校验。适用场景: 用户提出跨领域或不确定领域的复杂问题, 需要从多个专家角度分别搜证并相互校验后综合成文, 例如该不该买房、该不该跳槽、是否进入某个赛道等。触发关键词: 多角度分析、专家分析、综合分析、多视角、跨领域分析、从不同角度看、深度分析。问题只属于单一明确领域时, 优先使用该领域的专门 skill, 例如纯财务用 finance-core-analysis、纯技术用 software-architect。输出 (全部 markdown 保存到当前项目 markdown/ 目录): (1) 每位专家的中间分析稿; (2) 事实核查报告 (跨专家矛盾 / 未经证实的主张 / 重叠区); (3) 红队反驳报告 (逐条反驳承重墙级主张, 给出 SURVIVES / WEAKENS / REFUTED 裁定); (4) 第一人称、通俗易懂的最终综合长文, 同时报告哪些主张通过验证、多少被弱化、多少被剔除。

为提问者生成个性化的未来规划与建议书。输入提问者的背景信息（职业、年龄、资源、目标、困境等），基于深度画像分析、行业趋势研判和商业洞察，输出一份图文并茂、有数据支撑、逻辑严密的 Markdown 规划报告，保存到项目 markdown/ 目录。触发条件：用户提供个人背景信息并希望获得规划建议，提到"帮我规划"、"未来规划"、"职业规划"、"个人发展"、"我该怎么做"、"给我写一份建议书"、"我的优势是什么"、"下一步怎么走"，或者提供了详细个人信息并问 Claude 如何利用好它。即使用户只说"帮我分析一下我的情况"、"我现在很迷茫"但附带了背景信息，也应使用本 skill。

Answer general or cross-domain questions with a non-pleasing rational mode: adversarial red-team and blue-team expert analysis, mutually exclusive conclusions, up to five debate rounds, saved Markdown intermediate expert outputs, and a final first-person judge-written plain-language article. Use when the user asks for rational adversarial analysis, red/blue team debate, non-flattering judgment, evidence-backed multi-expert reasoning, or a final Markdown answer to a broad question.

> 用红蓝双队辩论模式深度解答通用问题，以非讨好型人格的理性人视角输出最终报告。 触发条件：用户提出任何值得深度分析的问题，尤其是存在争议、有多个维度、需要权威数据支撑的问题。 提到"红蓝辩论"、"辩证分析"、"正反两面"、"两种观点"、"帮我深度分析"、"有没有反驳意见"、"理性分析一下"、"客观看待"，或提出任何开放性、争议性问题时必须使用本 skill。 即使用户只是提出一个看似简单的问题如"XX 到底值不值得做"或"XX 是对的吗"， 只要涉及价值判断、策略选择、事实真相等复杂情境，也应使用本 skill。 本 skill 不追求讨好用户，拒绝模糊骑墙，双队结论必须互斥，最终裁判整合并输出面向小白的第一人称深度文章。

| PostgreSQL 核心 committer Tom Lane 的思维框架与表达方式。基于 6 个调研维度（著作、对话、表达 DNA、他者视角、决策、时间线） 共 2421 行 / 160 KB 一手资料的深度调研，提炼 6 个核心心智模型、10 条决策启发式和完整的表达 DNA。 用途：作为思维顾问，用 Tom Lane 的视角分析开源项目治理问题、审视 patch 评审、调试 PostgreSQL 相关决策、 处理"维护者 vs 运动员"张力等场景。 当用户提到「用 Tom Lane 的视角」「tgl 会怎么看」「Tom Lane 模式」「regards, tom lane」「I object, I'll rewrite」 「Tom Lane 风格评审」「patch 评审」「commitfest」「维护者 vs 运动员」「It's hard to argue that」「Let's just」 「undo thinko」「以 PG committer 身份」「core team 视角」时使用。即使用户只是说「帮我用 PG 核心 committer 的角度想想」 「如果 Tom

输入一个产品 idea（一句话或详细描述均可），自动生成图文并茂、结构完整的 BRD（商业需求文档），以 Markdown 格式保存到当前项目 markdown/ 目录，同时输出配套 SVG 图表文件。触发条件：用户提到"写 BRD"、"帮我写需求文档"、"生成 BRD"、"写商业需求文档"、"我有个产品想法"、"帮我把这个 idea 写成文档"、"PRD/BRD 模板"、"产品立项文档"。即使用户只给出一句简短的产品描述如"我想做一个 XX 产品"，也应立即使用本 skill 生成 BRD。本 skill 面向产品经理、创业者、产品负责人，输出可直接用于团队评审和立项决策的专业文档。

Generate a market requirements document (MRD) from a product idea and save it as Markdown under the current project's markdown/ directory. Use when the user asks to write, draft, create, produce, or refine an MRD, market requirements document, product opportunity document, market demand analysis, product idea validation document, or asks for "写 MRD", "市场需求文档", "产品立项文档", "产品机会分析", especially when input is only an idea and the output should be structured, visual, and decision-oriented.

输入一个产品 idea（一句话或详细描述均可），自动生成图文并茂、结构完整的 PRD（产品需求文档），以 Markdown 格式保存到当前项目 markdown/ 目录，同时输出配套 SVG 图表文件。触发条件：用户提到"写 PRD"、"帮我写需求文档"、"生成 PRD"、"写产品需求文档"、"写商业需求文档"、"我有个产品想法"、"帮我把这个 idea 写成文档"、"PRD 模板"、"产品立项文档"、"产品需求"、"功能需求文档"。即使用户只给出一句简短的产品描述如"我想做一个 XX 产品"，也应立即使用本 skill 生成 PRD。本 skill 面向产品经理、创业者、产品负责人，输出可直接用于团队评审和立项决策的专业文档，深度整合 JTBD 用户洞察框架、MoSCoW 优先级方法论和北极星指标体系。

Generate a structured implementation contract before making any code changes to FastLED. Defines scope, affected files, API changes, platform impact, risk assessment, and test plan. Use before implementing any feature, bug fix, driver addition, or refactoring.

Turns rough ideas into approved, decision-complete plans with validated structure before coding. Use when users ask in any language for planning, architecture, design direction, feasibility, value judgment, or whether a feature is worth doing before implementation. Not for bug fixes or small edits.

Interview the user and inspect coding-agent skill trigger counts to recommend unused K-skills for removal.

Clarify requirements before implementing. Use when serious doubts arise.

>- Guides the design and structuring of workflow-based Claude Code skills with multi-step phases, decision trees, subagent delegation, and progressive disclosure. Use when creating skills that involve sequential pipelines, routing patterns, safety gates, task tracking, phased execution, or any multi-step workflow. Also applies when reviewing or refactoring existing workflow skills for quality.

Interprets Culture Index (CI) surveys, behavioral profiles, and personality assessment data. Supports individual profile interpretation, team composition analysis (gas/brake/glue), burnout detection, profile comparison, hiring profiles, manager coaching, interview transcript analysis for trait prediction, candidate debrief, onboarding planning, and conflict mediation. Accepts extracted JSON or PDF input via OpenCV extraction script.

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeki

Design multi-agent AI workflows with clear boundaries, handoffs, and monitoring. Use when a complex PM task should run as parallel specialized agents instead of one linear process.

Assess whether your product work is AI-first or AI-shaped. Use when evaluating AI maturity and choosing the next team capability to build.

Understand the PM-to-Director transition through altitude and horizon thinking. Use when diagnosing scope, time-horizon, or leadership-level gaps.

Run a customer journey mapping workshop with adaptive questions and outputs. Use when you need to map stages, actions, emotions, pain points, and opportunities for a persona and scenario.

Identify what to measure, test, or track to de-risk a product or AI idea. Use when stress-testing an idea across internal (DUFV) and external (PESTEL) dimensions.

Guide the PM-to-Director transition across preparing, interviewing, landing, and recalibrating. Use when leadership scope is changing and you need practical coaching.

Run a structured discovery flow from problem framing through opportunity mapping and validation planning.

Plan customer discovery interviews with the right goal, segment, constraints, and method. Use when preparing interviews for problem validation, churn research, or new product ideas.

Run a full discovery cycle from problem hypothesis to validated solution. Use when a team needs a structured path through framing, interviews, synthesis, and experiments.

Break down epics into user stories with Humanizing Work split patterns. Use when a backlog item is too large to estimate, sequence, or deliver safely.

Frame an epic as a testable hypothesis with target user, expected outcome, and validation method. Use when defining a major initiative before roadmap, discovery, or delivery planning.

Plan a VP or CPO 30-60-90 day diagnostic onboarding path. Use when entering a new executive product role and avoiding premature change.

Evaluate feature investments using revenue impact, cost structure, ROI, and strategy. Use when deciding whether a feature deserves investment.

Decode an incoming message into a structured breakdown that separates the literal ask from the job-to-be-done. Use before replying to a loaded Slack ping, email, mandate, or escalation.

Guide PM to Director to VP/CPO transition planning with role-fit diagnostics and onboarding guidance.

Guide teams through Lean UX Canvas v2. Use when framing a business problem, surfacing assumptions, and defining what to learn next.

Identify which organic growth path to pursue — new segments, geographies, channels, or products. Use when diagnosing where a growth constraint lives and which McKinsey growth level to act on next.

Analyze political, economic, social, technological, environmental, and legal forces. Use when external market shifts could materially affect a product, roadmap, or strategy.

Turn strategy and validated opportunities into a sequenced roadmap with clear tradeoffs.

Design a new PM skill through guided conversation. Use when you have raw content or an idea and want to shape it into a compliant skill.

Define a Proof of Life probe to test a risky hypothesis cheaply. Use when you need harsh truth before building real product.

Select the right Proof of Life (PoL) probe based on hypothesis, risk, and resources. Use this to match the validation method to the real learning goal, not tooling comfort.

Create a Geoffrey Moore-style positioning statement. Use when clarifying who you serve, what problem you solve, your category, and why you're different from alternatives.