reconcile

name	reconcile
description	Checks the active sprint for merged PRs and cascades Notion task/story/epic statuses according to the lifecycle rules. Use after merging PRs or to sync stale statuses.

Reconcile Skill

Scan the active sprint and reconcile Notion statuses based on git/GitHub state and the task lifecycle rules in AGENTS.md.

Notion Database IDs

Database	ID
Sprints	a89cc7a7-ab1a-4e3f-945d-d42028c75f00
Stories	9ec44d56-966b-4c3e-ba98-637b128c99a8
Tasks	2e0b6b31-d3bd-4e32-a127-3eedf257f228
Epics	a040ab6d-10bb-4575-8c80-d4e827238b03
Bugs	e6b8eb47-ddcd-4dba-b5fd-c631763ac5bd

Steps

Follow these steps in order.

1. Find the active sprint

Query the Sprints database (notion db query <sprints-id> -f json --all) and find the sprint whose date range covers today (or the most recent one). Fetch it to get linked stories and bugs.

If no active sprint exists, tell the user and stop.

2. Gather sprint data

For each story in the sprint:

1. Fetch the story props via notion page props <id> -f json to get its status and linked tasks
2. Fetch each task to get its status

Build a map of: story → [tasks] with statuses for each.

3. Check local work in progress

Run git status and git diff --stat to check for uncommitted local changes. If changes exist, match them to sprint tasks by examining which files were modified and what they relate to. Any matching tasks still in TODO should be marked for In Progress.

Also check for open (unmerged) feature branches with gh pr list --state open --json number,title,headRefName and git branch --list 'feat/*' --list 'fix/*' --list 'docs/*'. Match open branches/PRs to tasks — any matching tasks still in TODO should be marked for In Progress.

4. Check merged PRs

Run gh pr list --state merged --base main --limit 50 --json number,title,mergedAt,headRefName to find recently merged PRs.

5. Apply lifecycle rules

Tasks have a simplified lifecycle: TODO → In Progress → Done. Stories, epics, and milestones keep the full lifecycle.

Walk through each story and its tasks, applying these rules in order. Collect all needed updates, then report them before making changes.

Rule 0: Task TODO → In Progress (local work detected)

For each task matched in step 3:

• If the task is in TODO, mark it for In Progress
• Apply Rule 5 (cascade In Progress) for its parent story/epic/milestone

Rule 1: Task In Progress → Done (work pushed)

For each task in In Progress:

• Check if its work has been pushed to a feature branch (match branch name or PR title to task/story)
• If pushed, mark the task for Done

Rule 2: Story → In Review

For each story where all tasks are Done:

• If the story is not already in In Review, In Test, or Done, mark it for In Review

Rule 3: Story → In Test (after merge)

For each story in In Review:

• Check if its feature branch PR has been merged into main
• If merged, mark the story for In Test

Rule 4: Epic → In Review

For each parent epic of the sprint's stories:

• Fetch the epic and all its stories
• If all stories are in In Test or Done, mark the epic for In Review

Rule 5: Cascade In Progress

For each story in In Progress:

• If parent epic is in TODO, mark it for In Progress
• If parent milestone is in TODO, mark it for In Progress

6. Report proposed changes

Present all proposed status changes to the user in a table:

| Entity       | Current Status | New Status  | Reason                     |
|--------------|---------------|-------------|----------------------------|
| Task: ...    | In Progress   | Done        | Work pushed in feat/branch |
| Story: ...   | In Progress   | In Review   | All tasks Done             |
| Story: ...   | In Review     | In Test     | PR #42 merged              |
| Epic: ...    | In Progress   | In Review   | All stories in Test/Done   |

If no changes are needed, tell the user everything is in sync and stop.

7. Apply changes

After the user confirms (or if no ambiguity exists), apply all updates via notion page set <id> "Status=<new-status>".

Only move tasks to Done automatically (per the lifecycle rules). Do not move stories, epics, or milestones to Done — those are set manually by the user.

8. Summary

Report what was updated and the final state of the sprint.