Decompose implementation plans into atomic tasks with dependencies and references.
npx skills add https://github.com/quitgenius/ai-engineering --skill beads-quitgenius
Please help me install this Agent Skill. Skill: beads Source: https://github.com/quitgenius/ai-engineering/tree/main/claude-skills/beads Command: npx skills add https://github.com/quitgenius/ai-engineering --skill beads-quitgenius
This Skill breaks down complex project specifications and implementation plans into small, manageable, and independently verifiable tasks optimized for AI agent workflows, ensuring efficient and structured development.
Use the beads skill to decompose the implementation plan for ticket PAN-123 into atomic tasks.
High-intent search queries and answers about installing and using this skill.
Task decomposition for AI workflows converts high-level specs into atomic, verifiable units of work. It creates small tasks sized for AI context windows with clear goals, defined dependencies, and references to existing code patterns and architecture decision records.
Breaking down an implementation plan involves processing it through the beads issue tracker to generate small, actionable tasks. Each resulting task receives defined success criteria and references to existing code patterns, ensuring alignment with project scope and architectural decisions.
Yes, managing task dependencies for AI agent workflows is supported during decomposition. The system establishes dependencies between atomic tasks to enforce a logical execution order, ensuring independently verifiable units of work follow architectural requirements.
Yes, task decomposition works with existing architecture decision records. The generated atomic tasks include explicit references to ADRs and existing code patterns, managing the task lifecycle from creation to completion while ensuring alignment with architectural decisions.
Tracking the lifecycle of AI development tasks is best handled by an issue tracker managing them from creation to completion. This ensures each atomic unit of work remains aligned with project scope and architectural decisions throughout the structured development process.
You should avoid atomic task decomposition when your implementation plan already lacks defined architectural decisions. The process relies on creating small, verifiable units with dependencies and references to ADRs, making it less suited for simple or undefined project scopes.
JunHyuk-KangGenerate developer implementation instructions from planning documents and design specifications.
jeremy-newhouseExecute tracker-defined engineering sprints in dependency order with state recovery.
AnveioBuild autonomous coding agents with the Claude Agent SDK for TypeScript.
flowelConvert project plans, specifications, or PRDs into independently demoable issues via vertical slicing.
