a7b15298e0
Brings 47 local-only files from backup-local-main into the merge-upstream
branch at their pre-rename paths. Subsequent steps will rename these to
the ce-* convention and port shared-file merges.
Includes:
- Custom skills: john-voice, jira-ticket-writer, hugo-blog-publisher,
weekly-shipped, proof-push, ship-it, story-lens, sync-confluence,
excalidraw-png-export, python-package-writer, fastapi-style,
upstream-merge
- Custom agents: design-conformance-reviewer, tiangolo-fastapi-reviewer,
zip-agent-validator, python-package-readme-writer, lint
- Custom commands: essay-edit, essay-outline, pr-comments-to-todos,
resolve_todo_parallel, workflows/{plan,review,work}
- Local mods to ce-review/SKILL.md + review-output-template.md (will be
ported to ce-code-review in a later step)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
37 lines
1.5 KiB
Markdown
37 lines
1.5 KiB
Markdown
---
|
||
name: resolve_todo_parallel
|
||
description: Resolve all pending CLI todos using parallel processing
|
||
argument-hint: "[optional: specific todo ID or pattern]"
|
||
---
|
||
|
||
Resolve all TODO comments using parallel processing.
|
||
|
||
## Workflow
|
||
|
||
### 1. Analyze
|
||
|
||
Get all unresolved TODOs from the /todos/\*.md directory
|
||
|
||
If any todo recommends deleting, removing, or gitignoring files in `docs/plans/` or `docs/solutions/`, skip it and mark it as `wont_fix`. These are compound-engineering pipeline artifacts that are intentional and permanent.
|
||
|
||
### 2. Plan
|
||
|
||
Create a TodoWrite list of all unresolved items grouped by type.Make sure to look at dependencies that might occur and prioritize the ones needed by others. For example, if you need to change a name, you must wait to do the others. Output a mermaid flow diagram showing how we can do this. Can we do everything in parallel? Do we need to do one first that leads to others in parallel? I'll put the to-dos in the mermaid diagram flow‑wise so the agent knows how to proceed in order.
|
||
|
||
### 3. Implement (PARALLEL)
|
||
|
||
Spawn a pr-comment-resolver agent for each unresolved item in parallel.
|
||
|
||
So if there are 3 comments, it will spawn 3 pr-comment-resolver agents in parallel. liek this
|
||
|
||
1. Task pr-comment-resolver(comment1)
|
||
2. Task pr-comment-resolver(comment2)
|
||
3. Task pr-comment-resolver(comment3)
|
||
|
||
Always run all in parallel subagents/Tasks for each Todo item.
|
||
|
||
### 4. Commit & Resolve
|
||
|
||
- Commit changes
|
||
- Remove the TODO from the file, and mark it as resolved.
|