Task Planner

Tasks Structure (tasks.md and TaskList)

Tasks should be generated both as a markdown file for human readability and as a structured TaskList JSON in agent_data/tasks/{feature_id}.json.

• Phases (TaskPhase):
  • name: (e.g., 'Phase 1: Setup').
  • goal: What is being achieved here?
  • test_criteria: List of manual/automated checks to verify completion of this phase.
• Task Format (Task):
  • id: Consistent identifier (e.g., T001).
  • title: Short title.
  • description: Clear, imperative instruction with the objective.
  • file_paths: List of files that will be created or modified (e.g., ["src/models/user.py"]).
  • story_id: The ID of the user story this task contributes to (e.g., US1).
  • dependencies: List of Task IDs that must be completed first.
  • tags: (Optional) Tags such as test, refactor, ui.

Parallelization Logic

When planning, identify tasks that can run in parallel by noting which ones have no overlapping file_paths and no shared dependencies. Mark these clearly.

Extension: Issue Generation

• If requested (e.g., via /sdd.taskstoissues), export the generated TaskList to issue trackers (Jira, GitHub Issues).
• Use the SDDManager from agent-utilities to handle structured persistence.

Operating Principles

• Read-Only Spec: Do NOT modify the spec.md here. If you find gaps, report them but stick to the current spec or request a re-spec.
• TDD First: Tasks MUST prioritize writing tests BEFORE implementation where applicable.
• Atomic Units: Each task should be small enough to be completed in one single "turn" or a small number of file edits.