القائمة
Use when any workflow needs a product lens — user impact analysis, prioritization, scope discipline, or stakeholder framing. Triggers on product analysis, PM review, user impact, business value.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when a skill needs step tracking, progress visibility, and resume support within a single phase. Called by skills, not directly by users.
Use when breaking down a project phase into stories with acceptance criteria, creating ADRs, or planning infrastructure work. Triggers on /plan, story breakdown, detailed plan, architecture doc.
Use when generating, editing, or merging Low-Level Design (LLD) documents at `docs/lld/<component>.md` or `docs/shield/<feature>/lld-<component>.md`. Triggers on /lld command (Path A) and on /plan TRD-driven authoring (Path B, M2 plan). Owns the backend and infra templates, atomic write, provenance stamp, and §14 Changelog convention.
Use when authoring a new PRD or upgrading a lean PRD to standard. Walks user through 20-section problem-first scaffold (or 10-section lean), pre-populates from prior /research transcript if present, defers Terminologies (§2) until after the rest is drafted (auto-fills from research glossary + scan of body), invokes shield:story-coverage between Sections 6 and 8 and shield:milestone-coverage between Sections 8 and 15, prompts for story Type (new/enhancement/existing), supports custom team templates via .shield.json. Triggers on /prd, write a PRD, author a PRD.
Use when the user invokes /backlog or asks to capture, view, promote, or remove an idea from the project backlog at docs/shield/backlog.json. Triggers on /backlog add|view|remove|promote and on agent-side "capture this as a backlog entry" calls during research/PRD/plan/implement flows.
Use when a plan, architecture doc, or execution plan exists and needs expert review before implementation. Produces a scored analysis with a P0-gated verdict and an enhanced plan. Triggers on /plan-review, review my plan, document review.
| name | pm-analysis |
| description | Use when any workflow needs a product lens — user impact analysis, prioritization, scope discipline, or stakeholder framing. Triggers on product analysis, PM review, user impact, business value. |
Thin orchestrator that dispatches the appropriate focused subagent(s) based on mode. Post
pm-restructure-v0, the omnibus shield:product-manager agent has been decomposed; this skill
now routes to:
research-framing mode → shield:research-framerresearch-review mode → shield:research-reviewer-narrative + shield:user-impact-clarity (PM1) + ... + shield:business-value-alignment (PM10) + shield:framing-coverage-honored (PM11), dispatched in parallelplan-review mode → shield:user-impact-clarity (PM1) + ... + shield:business-value-alignment (PM10), dispatched in parallelstandalone mode → same as plan-review (PM1-PM10 in parallel)The domain knowledge lives in the focused subagents — this skill only determines the mode, gathers input, and dispatches.
research skill to frame questions before research or review findings after synthesisplan-review skill to add a PM perspective on plansshield:review instead| Context | Mode |
|---|---|
| Called from research skill before research agents run | research-framing |
| Called from research skill after synthesis | research-review |
| Called from plan-review skill | plan-review |
| Called directly or from any other workflow | standalone (default) |
The calling skill passes the mode explicitly. Standalone is the default when no mode is specified.
standalone.| Mode | Dispatches (parallel) | Inputs |
|---|---|---|
research-framing | shield:research-framer | topic, optional decision_context, optional urgency |
research-review | shield:research-reviewer-narrative + PM1-PM10 + shield:framing-coverage-honored (PM11) | findings_path, framing_brief_path |
plan-review | PM1-PM10 (10 parallel dispatches; no PM11) | doc_path |
standalone | PM1-PM10 | doc_path |
PM1-PM10 are the 10 global subagents shield:user-impact-clarity, shield:problem-solution-fit,
shield:scope-discipline-of-plan, shield:prioritization-rationale, shield:stakeholder- communicability, shield:market-competitive-awareness, shield:adoption-rollout-risk,
shield:success-metrics-defined, shield:reversibility-exit-cost, shield:business-value- alignment.
scoring.md) is loaded by each PM dim subagent's frontmatter context as
needed; this skill no longer inlines the rubric in the dispatch prompt.framing_brief_path should reference the markdown brief produced by shield:research-framer
upstream. PM11 returns N/A if no framing brief is supplied.| Mistake | Fix |
|---|---|
Dispatching shield:product-manager | That agent was deleted in pm-restructure-v0. Route by mode per the table above. |
| Dispatching subagents sequentially in research-review / plan-review / standalone modes | Always dispatch PM1-PM10 in PARALLEL — sequential calls throw away the depth gains from decomposition. |
| Skipping framing in research because "the topic is clear enough" | Always run framing — it shapes research agent prompts, not just the user's understanding. |
Omitting framing_brief_path from research-review mode | PM11 returns N/A without it; provide it whenever a framing brief was produced upstream. |
| Treating PM review output as optional | The Product Lens section is a required part of the research document. |