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

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

View File

@@ -6,7 +6,7 @@ disable-model-invocation: true
---
- First set the /model to Haiku
- Then read all pending todos in the todos/ directory
- Then read all pending todos from `.context/compound-engineering/todos/` and legacy `todos/` directories
Present all findings, decisions, or issues here one by one for triage. The goal is to go through each item and decide whether to add it to the CLI todo system.
@@ -149,7 +149,7 @@ Do you want to add this to the todo list?
**When user says "next":**
- **Delete the todo file** - Remove it from todos/ directory since it's not relevant
- **Delete the todo file** - Remove it from its current location since it's not relevant
- Skip to the next item
- Track skipped items for summary
@@ -182,22 +182,22 @@ After all items processed:
### Skipped Items (Deleted):
- Item #5: [reason] - Removed from todos/
- Item #12: [reason] - Removed from todos/
- Item #5: [reason] - Removed
- Item #12: [reason] - Removed
### Summary of Changes Made:
During triage, the following status updates occurred:
- **Pending → Ready:** Filenames and frontmatter updated to reflect approved status
- **Deleted:** Todo files for skipped findings removed from todos/ directory
- **Deleted:** Todo files for skipped findings removed
- Each approved file now has `status: ready` in YAML frontmatter
### Next Steps:
1. View approved todos ready for work:
```bash
ls todos/*-ready-*.md
ls .context/compound-engineering/todos/*-ready-*.md todos/*-ready-*.md 2>/dev/null
```
````
@@ -272,7 +272,7 @@ Do you want to add this to the todo list?
4. Confirm: "✅ Approved: `{filename}` (Issue #{issue_id}) - Status: **ready**"
**When "next" is selected:**
1. Delete the todo file from todos/ directory
1. Delete the todo file from its current location
2. Skip to next item
3. No file remains in the system