Skip to content

feat(aidd-dev): add 10-todo skill for parallel todo fan-out#262

Open
alexsoyes wants to merge 1 commit into
mainfrom
feat/todo-skill
Open

feat(aidd-dev): add 10-todo skill for parallel todo fan-out#262
alexsoyes wants to merge 1 commit into
mainfrom
feat/todo-skill

Conversation

@alexsoyes

@alexsoyes alexsoyes commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

🎯 What & why

Adds aidd-dev:10-todo, a micro skill that splits one user prompt into independent todos, implements each via parallel implementer agents, and reports a single minimal table.

🛠️ How it works

  • SKILL.md is a one-action router; all logic lives in 01-todo.md.
  • Flow: read prompt ($ARGUMENTS, fallback latest user message) → categorize into independent todos inline (no agent) → spawn one implementer agent per todo in a single parallel batch → print exactly one Category | Launched | Output table.
  • Each agent must first run a refine step, discovering a refine-capable skill at runtime by description matching — no hardcoded plugin name, per the cross-plugin orthogonality rule.
  • No per-todo plan and no completeness loop, by design: one shot per todo keeps the skill micro.

🧪 How to verify

  • Invoke aidd-dev:10-todo with a multi-part prompt (e.g. "fix the header typo and add a /health endpoint").
  • Agents spawn in one parallel batch, each refining before implementing.
  • Output is a single table, nothing else.

✅ I certify

  • I DO CERTIFY I READ EACH LINE OF THE PULL REQUEST BECAUSE I AM A SOFTWARE ENGINEER, NOT A AI PUPPY.

🤖 Generated with Claude Code

@alexsoyes alexsoyes marked this pull request as ready for review June 11, 2026 11:11
@alexsoyes alexsoyes requested a review from a team as a code owner June 11, 2026 11:11
@alexsoyes alexsoyes enabled auto-merge (squash) June 11, 2026 11:11

## Process

1. **Read.** Take `prompt` from `$ARGUMENTS`; if empty, use the latest user message.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Peut être demander aussi ? Prendre le dernier message user ça va porter à confusion

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not, si t'as une idée tu peux faire une commit suggestion @blafourcade ?

@blafourcade

Copy link
Copy Markdown
Contributor

@alexsoyes tu dois signer tes commit de sang

Split a single user prompt into independent todos and run one
implementer agent per todo in parallel, each refining its todo via a
runtime-discovered refine skill before coding. Keeps the report to a
single minimal table so the skill stays micro.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: alexsoyes <contact.alexsoyes@gmail.com>
```markdown
1. Refine the todo first - discover at runtime a skill whose description covers refining or clarifying a request (never a hardcoded plugin name) and run it on the todo.
2. Implement the refined todo.
3. Return a one-line output summary.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Et si on veut le détail on a quand même accès au run de l'agent spawned en parallèle?
Sur claude et cursor oui il me semble. sur copilot pas sûr.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants