marcusrbrown/todo-resolve
skills/todo-resolve/SKILL.md
Use when batch-resolving approved todos, especially after code review or triage sessions
$ install --global
skillsauthnpx skillsauth add marcusrbrown/systematic todo-resolveInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 22, 2026, 6:26 AM121.8s1 file scanned
SKILL.md
- name:
- todo-resolve
- description:
- Use when batch-resolving approved todos, especially after code review or triage sessions
- argument-hint:
- [optional: specific todo ID or pattern]
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.
Workflow
1. Analyze
Scan .context/systematic/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: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.
2. Plan
Create a task list grouped by type (e.g., todowrite in OpenCode, update_plan in Codex). Analyze dependencies -- items that others depend on run first. Output a mermaid diagram showing execution order and parallelism.
3. Implement (PARALLEL)
Spawn a systematic:workflow:pr-comment-resolver agent per item. Prefer parallel; fall back to sequential respecting dependency order.
Batching: 1-4 items: direct parallel returns. 5+ items: batches of 4, each returning only a short status summary (todo handled, files changed, tests run/skipped, blockers).
For large sets, use a scratch directory at .context/systematic/todo-resolve/<run-id>/ for per-resolver artifacts. Return only completion summaries to parent.
4. Commit & Resolve
Commit changes, mark todos resolved, push to remote.
GATE: STOP. Verify todos resolved and changes committed before proceeding.
5. Compound on Lessons Learned
Load the ce:compound skill to document what was learned. Todo resolutions often surface patterns and architectural insights worth capturing.
GATE: STOP. Verify the compound skill produced a solution document in docs/solutions/. If none (user declined or no learnings), continue.
6. Clean Up
Delete completed/resolved todo files from both paths. If a scratch directory was created at .context/systematic/todo-resolve/<run-id>/, delete it (unless user asked to inspect).
Todos resolved: [count]
Pending (skipped): [count, or "none"]
Lessons documented: [path to solution doc, or "skipped"]
Todos cleaned up: [count deleted]
If pending todos were skipped, list them:
Skipped pending todos (run `/systematic:todo-triage` to approve):
- 003-pending-p2-missing-index.md
- 005-pending-p3-rename-variable.md
Related Skills
marcusrbrown/orchestrating-subagents
development
VerifiedTrustedCommunity
Use when dispatching parallel or serial subagents in OpenCode, coordinating multi-unit plan execution, synthesizing results from independent subagent runs, or handling subagent failure and retry. Triggers on requests to run tasks in parallel, divide work across subagents, orchestrate a pipeline of dependent steps, or coordinate multiple agents without shared-file conflicts.
22SKILL.mdUpdated Jun 6, 2026
marcusrbrown/writing-skills
testing
VerifiedTrustedCommunity
Use when creating new skills, editing existing skills, or verifying skills work before deployment
22SKILL.mdUpdated May 18, 2026
marcusrbrown/writing-systematic-skills
testing
VerifiedTrustedCommunity
Use when creating, editing, auditing, or fixing bundled Systematic skills, especially when authoring SKILL.md files, adding skill reference files, resolving content-integrity frontmatter failures, or deciding which Systematic conventions apply beyond the general writing-skills guidance.
22SKILL.mdUpdated May 2, 2026
marcusrbrown/onboarding
development
VerifiedTrustedCommunity
Generate or regenerate ONBOARDING.md to help new contributors understand a codebase. Use when the user asks to 'create onboarding docs', 'generate ONBOARDING.md', 'document this project for new developers', 'write onboarding documentation', 'vonboard', 'vonboarding', 'prepare this repo for a new contributor', 'refresh the onboarding doc', or 'update ONBOARDING.md'. Also use when someone needs to onboard a new team member and wants a written artifact, or when a codebase lacks onboarding documentation and the user wants to generate one.
22SKILL.mdUpdated Apr 6, 2026