菜单
Generate an HTML report of an Epic's currently-implemented spec and its upcoming planned features, reconciled from the backlog snapshot and the repo's actual state. Use when the user wants a "what exists now vs what's coming" summary, 仕様まとめ, or a feature-status overview for stakeholders.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | report-epic-spec |
| description | Generate an HTML report of an Epic's currently-implemented spec and its upcoming planned features, reconciled from the backlog snapshot and the repo's actual state. Use when the user wants a "what exists now vs what's coming" summary, 仕様まとめ, or a feature-status overview for stakeholders. |
| disable-model-invocation | true |
Turn an Epic's .pm/ data into a stakeholder-readable answer to two
questions: what does the product do today, and what is planned next —
grounded in the code, not just the board.
Confirm the Epic (monday group title in mondayEpics); ask if unclear.
Refresh data like load-epic-context step 2: save-all.mjs +
sync-repo.mjs if stale (>60 min) or missing; run
migrate-epic-layout.mjs if the legacy-layout guard fires. Without a
configured repo, still proceed — the report is then board-only; say so in
the report header.
Gather the two sides:
.pm/backlog/items/*.json grouped by status — Done items are
implemented-capability candidates; In Progress / not-started items are
the plan. prd/prd.md gives the framing and intended scope. Read item
files in bulk only for {name, status, points}; open full items only
where the report needs the detail..pm/repo/branch-diff.json (what the epic branch actually
changed), the tail of commits.jsonl, and targeted reads in the
dedicated clone (repo-state.json → mirrorPath) to describe real
behavior where the board is vague. Flag Done items with no visible
implementation trace, and implemented behavior no item records — do not
silently trust either side.Write the report to .pm/reports/spec/spec-report-<YYYY-MM-DD>.html —
self-contained HTML (inline CSS, no external assets, same conventions as
the progress report), in the workspace's document language, with:
Report back: the report path, the counts per section, and any
board↔code discrepancies found (these are also audit-epic-consistency
fodder — suggest it when discrepancies are numerous).
items/ missing or legacy layout → run snapshot-pbl-to-drive /
migrate-epic-layout.mjs first (the scripts' guard messages say which).MONDAY_TOKEN missing → save-all.mjs exits 1; point to the plugin README.Cross-check an Epic's user stories, PBIs, and acceptance criteria against the actual implementation in its repo, and propose fixes for mismatches, missing/unfinished descriptions, and unclear wording. Use when the user wants a consistency check between backlog and code, 整合性チェック, or asks whether the backlog still reflects what is really implemented.
Investigate a spike task from an Epic's backlog using the Epic's dedicated repo clone, and save a findings report the team can decide from. Use when the user mentions a spike, スパイク調査, or wants a technical question from the backlog researched against the actual codebase.
Load a PBL Epic's working context — backlog snapshot, repo sync data, and the Epic summary — refreshing stale data first, so the conversation can start from the Epic's current state. Use when the user wants to load/open an Epic, asks "where are we on <Epic>", Epicをロード, or starts a session about a specific Epic's status.
Read or update the product backlog on monday.com. Use when the user asks about backlog items, monday.com boards, tickets, or tasks tracked in monday.com.
Generate a sprint-review HTML document for a PBL Epic — done items with demo pointers, sprint metrics, and an agenda — from the monday.com board and its Drive snapshot. Use when the user wants sprint review material, a demo agenda, or to prepare for a sprint review / スプリントレビュー.
Generate a PBL Epic's progress & completion-forecast HTML report from its Drive snapshot. Use when the user wants a progress/status report, or a burndown/completion forecast for a PBL Epic.