john/claude-engineering-plugin
1
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases Wiki Activity

refactor: consolidate todo storage under .context/compound-engineering/todos/ (#361)

Browse Source
This commit is contained in:
Trevin Chow
2026-03-24 09:54:30 -07:00
committed by GitHub
parent 18d22afde2
commit 65e5621dbe
11 changed files with 306 additions and 120 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
plugins/compound-engineering/skills/resolve-todo-parallel/SKILL.md
View File

@@ -10,7 +10,7 @@ Resolve all TODO comments using parallel processing, document lessons learned, t
### 1. Analyze
Get all unresolved TODOs from the /todos/*.md directory
Get all unresolved TODOs from `.context/compound-engineering/todos/*.md` and legacy `todos/*.md`
Residual actionable work may come from `ce:review-beta mode:autonomous` after its in-skill `safe_auto` pass. Treat those todos as normal unresolved work items; the review skill has already decided they should not be auto-fixed inline.
@@ -54,9 +54,9 @@ GATE: STOP. Verify that the compound skill produced a solution document in `docs
### 6. Clean Up Completed Todos
List all todos and identify those with `done` or `resolved` status, then delete them to keep the todo list clean and actionable.
Search both `.context/compound-engineering/todos/` and legacy `todos/` for files with `done`, `resolved`, or `complete` 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.
If a per-run scratch directory was created at `.context/compound-engineering/resolve-todo-parallel/<run-id>/`, and the user did not ask to inspect it, delete that specific `<run-id>/` directory after todo cleanup succeeds. Do not delete any other `.context/` subdirectories.
After cleanup, output a summary: