epic-update

Records resolved tickets against Notion epics by filing follow-ups, refreshing task lists, and closing completed epics.

Updated Jul 19, 2026
One-click install
npx skills add https://github.com/forhas/pure-dev --skill epic-update-forhas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epic-update
Source: https://github.com/forhas/pure-dev/tree/main/plugins/notion-dev/skills/epic-update
Command: npx skills add https://github.com/forhas/pure-dev --skill epic-update-forhas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a ticket reaches Implemented status, its parent Epic in Notion needs bookkeeping: deferred follow-ups from the review must be filed as new tickets, the Epic's task list must be refreshed, a resolution log entry must be appended, and the Epic should auto-close when everything under it is resolved. Doing this manually after every merge is error-prone and easy to skip. ## Core Features & Use Cases - Deferred follow-up filing: Creates follow-up tickets from the review report's FILED list with deterministic titles and provenance markers, deduplicating against existing Epic children to prevent duplicates after interrupted runs. - Idempotent recovery: Detects prior partial invocations via the Epic's Resolution Log, retries transiently failed filings, and re-evaluates unknown states when a review report becomes available. - Automatic Epic closure: Closes the Epic only when all children are resolved, no follow-ups were just filed, and no failed filings remain outstanding. - Use Case: After /notion-dev:ticket merges a PR for ticket STO-67, this skill files two deferred review findings as new tickets under the STO Epic, refreshes the Epic's task list, appends a dated log entry, and closes the Epic if STO-67 was its last open child. ## Quick Start Invoke this skill with a resolved ticket ID after its PR merges, for example by running epic-update with ticket STO-67 and the review report in context.

Frequently Asked Questions about epic-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update a Notion epic after a ticket is resolved?

Invoke epic-update with the resolved ticket's ID after its PR merges. It files deferred follow-ups from the review report, refreshes the Epic's task list, appends a dated resolution log entry, and closes the Epic when all children are resolved.

How does epic-update prevent duplicate follow-up tickets?

It derives a deterministic title and a provenance marker (ticket key plus a hash of the finding text) for each follow-up. Before creating a ticket, it checks existing Epic children for a title match and confirms the provenance line in the candidate's Context section.

What happens if epic-update is interrupted mid-run?

A later invocation parses the Epic's Resolution Log to detect prior partial work. It retries only transiently failed filings using persisted context packets, skips already-filed items via provenance dedup, and re-runs the idempotent task-list refresh and close check.

When does epic-update close a Notion epic automatically?

The Epic closes only when every other child ticket is in a resolved status, no new follow-ups were filed this run, and no failed filings remain outstanding. Dropped follow-ups are recorded user decisions and do not block closure.

What happens when the review report is missing?

The skill records the dropped and failed follow-up lists as an explicit UNKNOWN sentinel rather than empty lists, so a later recovery invocation with a report available re-evaluates and files them instead of treating the state as settled.