Ask me what skills you need
What are you building?
Tell me what you're working on and I'll find the best agent skills for you.
Use when batch-resolving approved todos, especially after code review or triage sessions
Resolve approved todos using parallel processing, document lessons learned, then clean up.
Only ready todos are resolved. pending todos are skipped — they haven't been triaged yet. If pending todos exist, list them at the end so the user knows what was left behind.
Scan .context/compound-engineering/todos/*.md and legacy todos/*.md. Partition by status:
ready (status field or -ready- in filename): resolve these.pending: skip. Report them at the end.complete: ignore, already done.If a specific todo ID or pattern was passed as an argument, filter to matching todos only (still must be ready).
Residual actionable work from ce-code-review mode:autofix after its safe_auto pass will already be ready.
Skip any todo that recommends deleting, removing, or gitignoring files in docs/brainstorms/, docs/plans/, or docs/solutions/ — these are intentional pipeline artifacts.
Create a task list grouped by type (e.g., TaskCreate in Claude Code, update_plan in Codex). Analyze dependencies -- items that others depend on run first. Output a mermaid diagram showing execution order and parallelism.
npx skills add EveryInc/compound-engineering-plugin --skill ce-todo-resolveHow clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
Mostly clear, but there are still a few confusing or poorly structured parts.
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
Partially actionable with several concrete steps, but still missing important details.