gumbo

Draft or amend an Architecture Decision Record (ADR) from a research synthesis or a design decision. Use when a decision needs to become a durable, reviewable record — and when extending or correcting a decision that has already landed.

Review an Architecture Decision Record (or coupled ADR set + cover) for grounding, decisiveness, completeness, and internal consistency before it is approved or landed — and to catch the drift that iteration introduces across coupled drafts and the cover. Reports findings; does not auto-fix unless asked.

Create and maintain a roadmap that sequences milestones and the plans, research, and decisions that fulfill them. Use when work spans many artifacts over time and needs one living place that shows the sequence, status, dependencies, and risks.

Create implementation plans following project conventions. Use when planning new features, refactors, or significant changes.

Resume working on an in-progress implementation plan. Finds incomplete plans and provides context to continue.

Review an implementation plan for correctness, feasibility, completeness, and internal consistency before it is approved or implemented — and to catch the reference drift that iteration introduces. Reports findings; does not auto-fix unless asked.

Resume a research plan. Spawns parallel agents if not started, checks progress, or synthesizes findings.

Review a research effort for grounding, internal consistency, and synthesis fidelity before its conclusions are relied on — and to catch the contradictions that iteration introduces across question files and the synthesis. Reports findings; does not auto-fix unless asked.

Operate or resume a long-lived cross-project coordinator role over gumbo plans, research, issues, and ADRs. Use when you are tracking and sequencing work across one or more repos rather than implementing it — creating plans/research, processing external reviews, recording landings, and keeping roadmaps true.

Generate a paste-ready resume prompt for continuing work in a fresh session when context grows large. Use when wrapping up a long session so the next one picks up cleanly with one well-defined next action.

Initialize a gumbo directory for the current project, creating a template in ~/.gumbo and a symlink in the project repo

Triage findings from a plan into issues and research. Reads findings/ from a plan directory, decides what becomes an issue or research update, and writes them to the appropriate locations.

Archive a completed implementation plan. Moves the plan to archive/ and updates its status to COMPLETE.

Cancel an implementation plan. Moves the plan to archive/ with CANCELLED status. Use when a plan is superseded, abandoned, or no longer needed.

Retroactively create findings for a plan by reviewing completed phases. Use when findings weren't recorded during implementation and need to be extracted after the fact.

Archive completed research. Moves the research to archive/ and updates its status.

Cancel a research plan. Updates status to CANCELLED and moves to archive/. Use when research is no longer needed or has been superseded.

Create a research plan with parallel investigation tasks. Use when exploring a topic, analyzing external code, or gathering information to inform an implementation plan.