work-item-decompose

Task breakdown is achieved by decomposing a high-level user intent into discrete, executable work items. Each item receives a complexity assessment, acceptance criteria, and dependency validation to ensure a robust and manageable project plan.

Assessing task complexity involves assigning a low, medium, or high level to each decomposed work item. Dependency validation identifies and flags circular dependencies between items to guarantee execution order and project feasibility.

Creating work items with clear acceptance criteria requires an explicit mandate for completability. The decomposition process transforms broad goals into independently valuable deliverables, each defining specific completion standards.

You can automate task management workflows through an autonomy bias that adjusts execution modes. Depending on user preferences and the assessed complexity level, the system switches between autopilot, confirm, or validate execution modes.

Dependency validation is needed whenever decomposing an intent into multiple work items. It identifies and flags circular dependencies early, ensuring the resulting execution plan remains structurally sound and executable.

Task decomposition works for high-level intents by generating specific work items like designing database schemas or implementing API endpoints. It breaks complex software development goals into smaller, manageable deliverables.