From compound-engineering
Resolve all pending CLI todos using parallel processing, compound on lessons learned, then clean up completed todos.
npx claudepluginhub apollostreetcompany/codex-compound --plugin compound-engineeringThis skill uses the workspace's default tool permissions.
Resolve all TODO comments using parallel processing, document lessons learned, then clean up completed todos.
Batch-resolves approved 'ready' todos: scans directories, plans parallel execution with dependencies, commits changes, documents lessons learned, cleans up files. Reports skipped pendings.
Resolves all pending CLI TODOs from /todos/*.md using parallel pr-comment-resolver agents, dependency-aware Mermaid planning, commits changes, and marks resolved.
Share bugs, ideas, or general feedback.
Resolve all TODO comments using parallel processing, document lessons learned, then clean up completed todos.
Get all unresolved TODOs from the /todos/*.md directory
If any todo recommends deleting, removing, or gitignoring files in docs/brainstorms/, docs/plans/, or docs/solutions/, skip it and mark it as wont_fix. These are compound-engineering pipeline artifacts that are intentional and permanent.
Create a task list of all unresolved items grouped by type (e.g., TaskCreate in Claude Code, update_plan in Codex). Analyze dependencies and prioritize items that others depend on. For example, if a rename is needed, it must complete before dependent items. Output a mermaid flow diagram showing execution order — what can run in parallel, and what must run first.
Spawn a compound-engineering:workflow:pr-comment-resolver agent for each unresolved item.
If there are 3 items, spawn 3 agents — one per item. Prefer running all agents in parallel; if the platform does not support parallel dispatch, run them sequentially respecting the dependency order from step 2.
Keep parent-context pressure bounded:
If the todo set is large enough that even batched short returns are likely to get noisy, use a per-run scratch directory such as .context/compound-engineering/resolve-todo-parallel/<run-id>/:
GATE: STOP. Verify that todos have been resolved and changes committed. Do NOT proceed to step 5 if no todos were resolved.
Load the ce:compound skill to document what was learned from resolving the todos.
The todo resolutions often surface patterns, recurring issues, or architectural insights worth capturing. This step ensures that knowledge compounds rather than being lost.
GATE: STOP. Verify that the compound skill produced a solution document in docs/solutions/. If no document was created (user declined or no non-trivial learnings), continue to step 6.
List all todos and identify those with done or resolved status, then delete them to keep the todo list clean and actionable.
If a scratch directory was used and the user did not ask to inspect it, clean it up after todo cleanup succeeds.
After cleanup, output a summary:
Todos resolved: [count]
Lessons documented: [path to solution doc, or "skipped"]
Todos cleaned up: [count deleted]