sdd-tasks

Breaking down software design specs requires loading change context from memory and analyzing design artifacts. This produces a phase-structured tasks.md containing concrete, actionable implementation items with enforced dependency order and verification checks.

Generating a phase-structured task checklist for change management involves stepwise processing of design artifacts. The system loads change context, analyzes proposals, and outputs a tasks.md file enforcing dependency order and verification checks for engineering tasks.

Yes, you can persist generated engineering tasks to Engram or the filesystem. The persistence target depends on the active mode, ensuring the phase-based tasks are stored according to your specific OpenCode-like change workflow and orchestrator requirements.

Yes, an orchestrator is required for phase-based task breakdown in OpenCode-like workflows. The system applies to environments where an orchestrator requires a phase-structured tasks plan and alignment with Engram or Openspec modes to manage engineering tasks.

Task breakdown handles dependency order and verification checks by enforcing stepwise generation. It analyzes design artifacts to produce a structured tasks.md where phase-based items are ordered sequentially to ensure proper implementation flow and validation.

A limitation when generating a tasks.md is that the system requires existing change context loaded from memory and design artifacts. Without prior proposals, specs, or designs, it cannot produce phase-based implementation tasks or enforce dependency order.