idd-team
Skill0 starsChanged 4 months agoNo licenceView on GitHub
Multi-agent Issue Driven Development（マルチエージェント実装フロー）skill for AgentVillage. Use this skill whenever the user wants to implement a GitHub Issue using a team of subagents — an orchestrator/reviewer plus a dedicated design agent and an implementation agent — or invokes "/idd-team", "/idd-team 42", or says "チームで実装して", "オーケストレータで回して", "サブエージェントに分担させて", "マルチエージェントで Issue やって" など。既存 Issue を「オーケストレータ兼レビューア」が司令塔となり、設計担当・実装担当のサブエージェントに分担させて branch → 設計承認 → 実装 → テスト → PR まで進める。Always use this skill when the user invokes /idd-team (with or without an issue number). 単一セッションで Claude が全フェーズを直接こなす従来フローは `/idd`。本スキルはそれをサブエージェントに分業させたマルチエージェント版で、`/idd` を置き換えず併存する。新規 Issue 作成・revise・import は `/issue`、バックログ refinement は `/backlog`。
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- backlogSkill
- iddSkill
- issueSkill
- pr-reviewSkill
- self-reflection-reviewSkill
- type-lineageSkill
- ventSkill
- wisdom-captureSkill
The file
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.