Stats
Actions
Tags
From decaf-planning
Close a completed phase or plan by reconciling planned vs. actual, recording deviations and decisions, updating the parent work item, and creating follow-ups for deferred work. Use after finishing a phase or plan to prevent silent drift.
How this skill is triggered — by the user, by Claude, or both
Slash command
/decaf-planning:close-planThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Reconcile what was planned against what was actually built, then close the work item. Prevents orphaned plans and silent drift by forcing explicit closure with a durable summary.
Reconcile what was planned against what was actually built, then close the work item. Prevents orphaned plans and silent drift by forcing explicit closure with a durable summary.
Without explicit closure, the next session sees a phase with some acceptance criteria checked and no explanation of why — was it deferred deliberately or just forgotten? Decisions made mid-implementation live only in code and commits. Descoped work vanishes unless someone creates follow-up items.
This skill is the bookkeeping step the AI would otherwise skip.
The user provides a reference to a phase or plan:
If unclear, ask the user which phase or plan they want to close.
Read the work item or plan section to get:
Determine what was built by examining:
git log for the relevant time period or branch to see what commits were made. Look at commit messages for context.If the work was done in the current session, use conversation context as well. If it was done in prior sessions, rely on git history and the current state of the code.
Produce a structured summary:
## Closure Summary
**Status**: Completed | Partially completed
**Date**: <YYYY-MM-DD>
### Acceptance Criteria
- [x] Criterion 1
- [x] Criterion 2
- [ ] Criterion 3 — deferred: <reason>
### Deviations
Changes that differed from the original plan:
- <what changed and why>
### Decisions Made During Implementation
Architectural or design decisions not in the original plan:
- <decision and rationale>
### Deferred Work
Work that was planned but not completed:
- <what was deferred and why>
Keep it concise. A few bullet points per section is ideal. Don't pad sections that have nothing to report — omit empty sections entirely.
Present the draft summary before making any changes. The user may want to adjust, add context, or correct the assessment.
@../../../../conventions/work-items.md
Update the phase/plan work item:
Update the parent work item:
System-specific details:
| System | Close action |
|---|---|
| Beans | Append summary to body via beans edit, update status to done via beans update --status done |
| GitHub Issues | Add summary as a comment, close the issue |
| Azure DevOps | Append summary to description, update state to Closed/Done |
| Markdown | Append summary section under the phase in the plan file |
For each piece of deferred work identified in step 3, create a new work item:
Skip this step if nothing was deferred.
After all updates are made, inform the user:
Closed: <phase/plan reference>
- N/M acceptance criteria met
- N deviations recorded
- N follow-up items created: <references>
/decaf-planning:close-plan 3 # Close phase 3 from plan in context
/decaf-planning:close-plan BEAN-42 # Close a beans work item
/decaf-planning:close-plan ./plans/auth.md#2 # Close phase 2 in a plan file
npx claudepluginhub alphaleonis/decaf-claude-config --plugin decaf-planningBuilds a structured summary of a Planr scope after work, review, or status inspection, including changes, verification evidence, blockers, and recommended next commands.
Finalizes task or workflow closeout after completion gate approval by syncing state, generating release notes/changelogs, and creating handoff packs.
Reconciles Plans.md with git state and implementation progress. Detects drift between markers and actual work, updates statuses, and optionally saves snapshots. Useful for syncing status or checking progress.