From solopreneur
Batch cleans up backlog todo files by scanning git history to classify completed, partial, or open items, then moves to done/doing/. Triggers on 'cleanup todos' or 'triage backlog'.
npx claudepluginhub hanamizuki/solopreneur --plugin neo4j-devThis skill uses the workspace's default tool permissions.
Scan the backlog directory and classify each item by checking git history for
Manages file-based todo tracking system in todos/ directory using markdown files: creates todos from feedback, updates status/dependencies, triages items, integrates with slash commands and code reviews.
Manages file-based todo tracking in todos/ directory: creates todos from feedback/findings, updates status/dependencies, triages items, integrates with slash commands and code reviews.
Periodically scans backlog and in-progress todos, cross-references GitHub PR status, reviews unhandled items, maintains worktrees, notifies via Discord or terminal, and auto-implements approved items.
Share bugs, ideas, or general feedback.
Scan the backlog directory and classify each item by checking git history for related commits. Present findings for user confirmation, then move files.
Before scanning, resolve the todo directory paths:
Check plugin config:
jq -r '.todos // empty' ~/.claude/solopreneur.json 2>/dev/null
If the todos key exists, use its backlog, done, doing, later values.
If no config — scan the project: Search for directories that look like todo/task storage:
# Common patterns
find . -maxdepth 3 -type d \( -name "todos" -o -name "todo" -o -name "TODO" \
-o -name "backlog" -o -name "tasks" -o -name ".todos" \) 2>/dev/null
For each candidate, count .md files inside. Present findings:
Found potential todo directories:
a) todos/backlog/ (12 .md files)
b) tasks/ (5 .md files)
Which is your backlog directory? (or enter a custom path)
Save to config after user confirms:
EXISTING=$(cat ~/.claude/solopreneur.json 2>/dev/null || echo '{}')
echo "$EXISTING" | jq --argjson todos '{
"backlog": "todos/backlog",
"done": "todos/done",
"doing": "todos/doing",
"later": "todos/later"
}' '.todos = $todos' > ~/.claude/solopreneur.json
Substitute user-confirmed paths into the JSON.
Use the resolved paths for all subsequent steps. Variables below:
$BACKLOG — backlog directory (e.g., todos/backlog)$DONE — done directory (e.g., todos/done)$DOING — doing directory (e.g., todos/doing)| Status | Criteria | Action |
|---|---|---|
| DONE | Found commits that fully implement the todo's requirements | Move to $DONE |
| PARTIAL | Some related commits exist, but not all requirements met | Move to $DOING |
| OPEN | No related commits found | Stay in $BACKLOG |
List all .md files in $BACKLOG. If empty, tell the user and stop.
Spawn a single sonnet subagent (model: "sonnet") with this prompt:
Read each todo file in {$BACKLOG} and determine its implementation status
by searching git history. For each file:
1. Read the file to understand what the task requires
2. Extract 3-5 search keywords from the title and content
3. Run `git log --oneline --all --grep="keyword"` for each keyword
4. If commits are found, read the commit messages to judge completeness
5. Classify as DONE / PARTIAL / OPEN
Files to check:
[list of file paths]
Report a markdown table:
| File | Status | Evidence |
|------|--------|----------|
| filename.md | DONE/PARTIAL/OPEN | commit hash + message, or "no related commits" |
Be conservative — only mark DONE if the commits clearly cover the full scope
described in the todo. If unsure, mark PARTIAL.
Show the subagent's table to the user. Ask for confirmation before moving files. The user may override individual classifications.
After confirmation:
$DONE$DOINGCreate target directories if they don't exist.
Report the final state:
todos/
├── backlog/ (N files remaining)
├── doing/ (N files)
├── done/ (N files)
└── later/ (N files)