create-tasks

Break down high-level requirements by decomposing work using Example Mapping and SPIDR techniques. This process ensures each engineering task forms a vertical slice with clear deliverables, context, acceptance criteria, dependencies, and verification steps.

The best way to structure tasks for agile sprint planning is to apply INVEST principles to ensure proper task sizing and quality. Each task should contain structured information like deliverables, context, decisions, and clear acceptance criteria.

The SPIDR technique works for software engineering task decomposition by splitting large requirements into smaller, manageable tasks. It ensures each resulting task is a vertical slice with well-defined context, dependencies, and verification steps.

Yes, you can generate tasks directly from a PRD. The system transforms high-level requirements or feature descriptions into well-defined, actionable tasks that engineers can implement without needing extensive prior context.

Actionable engineering tasks should include the deliverable, context, decisions, acceptance criteria, dependencies, and related code. This structured task creation prevents engineers from needing extensive prior context to implement the work.

Automated task decomposition may not be suitable when high-level requirements lack sufficient detail for Example Mapping, or when a project requires horizontal architectural slicing instead of vertical feature slices adhering to INVEST principles.