Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts, with complexity analysis
Generates a dependency-ordered tasks.md file for your feature branch. Use this after creating design artifacts (plan.md, spec.md) to break down implementation work into actionable steps.
/plugin marketplace add NeoLabHQ/context-engineering-kit/plugin install sdd@context-engineering-kitOptional task creation guidance or specific areas to focus on$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Setup: Get the current git branch, if it written in format feature/<number-padded-to-3-digits>-<kebab-case-title>, part after feature/ is defined as FEATURE_NAME. Consuquently, FEATURE_DIR is defined as specs/FEATURE_NAME.
Load context: Read specs/constitution.md, also read files from FEATURE_DIR:
Copy specs/templates/tasks-template.md to FEATURE_DIR/tasks.md using cp command, in future refered as TASKS_FILE.
Continue with stage 6
Launch tech-lead agent to create tasks, using provided prompt exactly, while prefiling required variables:
**Goal**: Create tasks for the implementation.
User Input: {provide user input here if it exists}
FEATURE_NAME: {FEATURE_NAME}
FEATURE_DIR: {FEATURE_DIR}
TASKS_FILE: {TASKS_FILE}
Please, fill/improve tasks.md file based on the task generation workflow.
Provide user with agent output and ask to answer on questions if any require clarification and repeat step 1, while adding questions and answers list as user input. Repeat until all questions are answered, no more than 2 times.