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.

2026-07-081

investigate-spike

atman-33/atman-marketplace

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.

2026-07-081

load-epic-context

atman-33/atman-marketplace

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.

2026-07-081

report-epic-spec

atman-33/atman-marketplace

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.

2026-07-081

manage-monday-backlog

atman-33/atman-marketplace

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.

2026-07-081

prepare-sprint-review

atman-33/atman-marketplace

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 / スプリントレビュー.

2026-07-081

name	snapshot-pbl-to-drive
description	Snapshot a monday.com PBL Epic's items (PBIs), docs, and updates into its mapped Google Drive folder in one script run.
disable-model-invocation	true

Snapshot a PBL Epic to Drive

One script call refreshes an entire Epic's Google Drive snapshot — no per-item tool calls needed.

Steps

Confirm the target Epic (the monday.com group title) from the conversation; ask the user if it isn't already clear.
Run once:
```
node "${CLAUDE_PLUGIN_ROOT}/scripts/monday/save-all.mjs" "<groupName>"
```
boardId and the Drive folder path auto-resolve from mondayBoardId / mondayEpics["<groupName>"] in .claude/scrum-context.json. Only pass them explicitly (save-all.mjs <boardId> "<groupName>" <epicFolderPath>) when not configured there.
Report the script's JSON summary (itemCount, itemsSaved, docsSaved, updatesSaved, prd, errors) back to the user. Do not open or verify individual snapshot files — reading them one by one is exactly the token cost this skill exists to avoid. Only investigate further if errors is non-empty or the user asks for detail on a specific item.

Reference

This runs the same save-all.mjs script documented in the manage-monday-backlog skill — see that skill's "Epic snapshot layout" section for the folder structure produced (.pm/backlog/, prd/) and its "Failure modes" section for MONDAY_TOKEN / board / group errors. This skill only adds a dedicated trigger for snapshot/backup-to-Drive requests; it does not change behaviour.

Once a snapshot exists, the report-pbl-progress skill turns it into a progress & completion-forecast HTML report — a natural next step after snapshotting.