From gumbo
Retroactively extracts findings from completed plan phases by reviewing git commits, task lists, and plan states. Use when notes were missed during implementation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/gumbo:plan-findings-createThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Retroactively extract findings from completed plan phases when findings weren't recorded during implementation.
Retroactively extract findings from completed plan phases when findings weren't recorded during implementation.
Identify the target plan:
/plan-findings-create 0018), use that plan directly.gumbo/plans/*/task-list.md files (exclude .gumbo/plans/archive/)findings/ directory (or sparse findings).gumbo/plans/archive/ and offer thoseGather implementation context:
Read the plan's state to understand what was done:
implementation-plan.md for the intended approachtask-list.md to identify completed phases and tasks.plan-state.json for:
commits array — commit SHAs from completed phaseslast_session_notes — notes about what happenedcurrent_task — where work stoppedtasks/ for what was planned vs. what may have changedReview commits for each completed phase:
For each commit SHA in .plan-state.json:
git log --format='%H %s' <sha> to get the commit messagegit diff <sha>~1..<sha> --stat to see what files changedgit diff <sha>~1..<sha> to review the actual changesIf no commits are recorded but tasks are checked off:
git log --oneline to find likely commits by message pattern (feat(plan-NNNN))Identify findings by comparing plan vs. reality:
For each completed task/phase, look for:
TODO, FIXME, HACK, or WORKAROUND in the committed code.Also search the committed code:
TODO, FIXME, HACK, WORKAROUND, XXX in changed files#[ignore] or @skip markersPresent findings to the user:
**Plan:** `.gumbo/plans/NNNN-feature-name/`
**Phases reviewed:** N completed phases (M commits)
**Findings identified:** K total
| # | Finding | Type | Phase/Task | Source |
|---|---------|------|------------|--------|
| 1 | [Short title] | diversion | Phase 2 / Task 2.1 | Commit abc1234 |
| 2 | [Short title] | todo | Phase 3 / Task 3.2 | TODO in src/foo.rs:42 |
| 3 | [Short title] | discovery | Phase 1 / Task 1.3 | Commit def5678 |
Should I write these as finding files in `.gumbo/plans/NNNN-name/findings/`?
You can adjust, add, or remove findings before I write them.
Wait for user approval before writing findings.
Write finding files:
Create .gumbo/plans/NNNN-name/findings/ directory if it doesn't exist
Write each finding as an individual markdown file
Use descriptive filenames: findings/todo-cleanup-unused-helpers.md
Follow the standard finding format:
# Finding: Short Title
**Type:** discovery | diversion | plan-error | note | todo | cleanup
**Task:** 2.1
**Date:** YYYY-MM-DD
**Source:** Commit abc1234 | TODO in src/foo.rs:42 | Observed during review
## Details
[What was found/changed/wrong]
## Impact
[How this affects the current plan or future work]
## Action Items
- [ ] Concrete next step (if any)
Report results:
**Findings written:** N files in `.gumbo/plans/NNNN-name/findings/`
- findings/diversion-changed-routing-approach.md
- findings/todo-cleanup-unused-helpers.md
- findings/discovery-diamond-attachment-behavior.md
Run `/plan-findings-resume NNNN` to triage these into issues and research.
findings/ directoryPlan: .gumbo/plans/0018-lr-rl-remaining-fixes/
Phases reviewed: 3 completed phases (3 commits)
Findings identified: 4 total
| # | Finding | Type | Phase/Task | Source |
|---|---|---|---|---|
| 1 | Router needed separate LR/RL backward path | diversion | Phase 2 / Task 2.1 | Commit 9b85567 |
| 2 | render_edge has TODO for multi-segment labels | todo | Phase 3 / Task 3.2 | TODO in src/render/edge.rs:187 |
| 3 | Plan assumed waypoints always ordered top-to-bottom | plan-error | Phase 2 / Task 2.3 | Commit 7b7e7f0 |
| 4 | Diamond attachment points need rank-aware sorting | discovery | Phase 1 / Task 1.2 | Commit 0d66d6c |
Should I write these as finding files in .gumbo/plans/0018-lr-rl-remaining-fixes/findings/?
npx claudepluginhub kevinswiber/gumbo --plugin gumboCompares approved plans against actual implementation to detect unimplemented items, out-of-scope changes, and design drift. Invoked via /drift-check.
Audits post-implementation plans against changes by parsing checkboxes for completeness and accuracy. Supports autonomy modes (Autopilot, Critical, Verbose) and file-review. Invoke via /verify-plan.
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.