sdd-tasks

To break down a change proposal into implementation tasks, you provide the orchestrator with a change name and artifact store mode. It extracts and structures work items from proposals and designs into a clear, phased task breakdown with dependencies.

Generating a phased task checklist from software design specifications involves synthesizing specs into structured work items organized by phase. This process produces a ready-to-persist tasks.md file or an Engram entry to ensure traceability from definition to execution.

Yes, you can use OpenSpec or Hybrid rules to persist project task breakdown artifacts. The system applies orchestrator-driven constraints to generate persistence artifacts according to your configured Engram, OpenSpec, or Hybrid mode.

You need an orchestrator-driven environment to structure implementation steps from change proposals effectively. The system relies on this orchestrator to apply retrieval and persistence contracts, ensuring your task list generates the correct inline tasks or artifacts.

Task synthesis handles dependencies by extracting and structuring implementation tasks from specs into a clear task breakdown organized by phase. It translates designs into concrete work items while maintaining clear dependencies for seamless execution handoff.

Task breakdown output differs between Engram and OpenSpec configurations because the system applies distinct persistence constraints per mode. Engram mode produces inline tasks, while OpenSpec or Hybrid modes generate ready-to-persist tasks.md artifacts.