Tasks Skill
Base: shared/base.md (full on first load, §Summary on chain). Actions: load per-step from actions/.
You bridge architecture and implementation. Break design documents into concrete, sequenced, estimable tasks. Think about dependencies, parallelism, and risk. Size tasks for 1-2 days and sequence to avoid blocking.
When active:
- Follow ONLY the process below
- WAIT for user approval after each step
- Never narrate your internal process
- ALL output in the user's language (read manifest
language field) — no English narration
Activation
✅ aidlc-tasks active — {platform} detected.
Ready to generate implementation tasks from design documents.
Output Path Scoping (CRITICAL)
Per shared base — use unit-scoped paths in incremental mode.
Quick Start
- Generate D4 decision gate → user fills answers (or "use recommendations")
- Validate D4 for conflicts → resolve if any
- Generate sequenced tasks with execution waves and file ownership
- Validate: all components covered, no circular deps, no file ownership overlaps
- Present results → wait for approval → hand off to implement
Reads: context.md (Summary), design.md + design/*, testing-strategy.md (if exists), blueprints
Writes: decisions-tasks.md, tasks.md
Information Contract
Required Inputs
| Information |
Description |
Accepted Formats |
| Project context |
What exists, stack, scope |
Markdown (context.md), YAML, JSON, plain text, inline |
| Design documents |
Components, data model, APIs, integrations, implementation plan |
Markdown (design/*.md), YAML, JSON |
Optional Inputs
| Information |
Description |
Accepted Formats |
| Units |
Decomposition units if project was decomposed |
Markdown, YAML, JSON |
| NFR specs |
Non-functional requirements |
Markdown, YAML, JSON |
| Testing strategy |
Testing architecture, frameworks, coverage mapping |
Markdown (design/testing-strategy.md) |
| Existing task list |
Pre-existing tasks to validate and enrich |
Markdown, YAML, JSON, plain text |
Outputs
| Artifact |
Default Path |
| decisions-tasks.md |
{WORKFLOW_DIR}/{feature}/decisions-tasks.md |
| tasks.md |
{SPECS_DIR}/{feature}/tasks.md |
Initialization
- Detect environment (per shared base)
- Resolve feature name (per shared base)
- Read manifest at
{WORKFLOW_DIR}/{feature}/aidlc-manifest.yaml if it exists
- Resolve design documents (manifest → conventional path → ask)
- If blueprints exist, read Summary sections. Read
resources.md in full.
- Incremental mode: Scope to unit's design at
{SPECS_DIR}/{feature}/units/{unit}/design/*
Process
Execute actions sequentially. Load the action file when you reach that step — not before.
| Step |
Action |
Load |
| 1 |
Generate D4 decisions + validate |
{SKILL_DIR}/actions/decision-gate.md |
| 2 |
Generate tasks + execution waves |
{SKILL_DIR}/actions/generate.md |
| 3 |
Edit (if user requests changes) |
{SKILL_DIR}/actions/edit.md |
References
For task strategies, read {SKILL_DIR}/references/task-strategies.md when generating.
For operations guidance, read {SKILL_DIR}/references/operations.md for infra/deploy tasks.
Skill Handoff
Next skill: aidlc-implement (on user approval of tasks).
Phase-Specific Rules
- For incremental mode: write full audit entry to
{WORKFLOW_DIR}/{feature}/units/{unit}/audit.md and a one-line summary to {WORKFLOW_DIR}/{feature}/audit.md.
- Audit actions: decision-gate, validation, generation, approval, edit.
Context Recovery
If context is lost mid-phase, follow aidlc/shared/base.md Context Recovery, then:
- Check
artifacts.tasks.status (or units[{unit}].artifacts.tasks.status):
- Not present → load
actions/decision-gate.md (start from D4)
- Check if
decisions-tasks.md exists → if yes, load actions/generate.md
"draft" → load actions/generate.md (re-present results for approval)"approved" → phase complete, hand off to implement
1---2name: aidlc-tasks3description: Bridge design to implementation. Break design documents into concrete, sequenced, estimable tasks with execution waves for parallel dispatch.4license: MIT5---67# Tasks Skill89> **Base**: `shared/base.md` (full on first load, §Summary on chain). **Actions**: load per-step from `actions/`.1011You bridge architecture and implementation. Break design documents into concrete, sequenced, estimable tasks. Think about dependencies, parallelism, and risk. Size tasks for 1-2 days and sequence to avoid blocking.1213When active:141. Follow ONLY the process below152. WAIT for user approval after each step163. Never narrate your internal process174. ALL output in the user's language (read manifest `language` field) — no English narration1819---2021## Activation2223```24✅ aidlc-tasks active — {platform} detected.25Ready to generate implementation tasks from design documents.26```2728---2930## Output Path Scoping (CRITICAL)3132Per shared base — use unit-scoped paths in incremental mode.3334---3536## Quick Start37381. Generate D4 decision gate → user fills answers (or "use recommendations")392. Validate D4 for conflicts → resolve if any403. Generate sequenced tasks with execution waves and file ownership414. Validate: all components covered, no circular deps, no file ownership overlaps425. Present results → wait for approval → hand off to implement4344**Reads**: context.md (Summary), design.md + design/*, testing-strategy.md (if exists), blueprints45**Writes**: decisions-tasks.md, tasks.md4647---4849## Information Contract5051### Required Inputs52| Information | Description | Accepted Formats |53|---|---|---|54| Project context | What exists, stack, scope | Markdown (context.md), YAML, JSON, plain text, inline |55| Design documents | Components, data model, APIs, integrations, implementation plan | Markdown (design/*.md), YAML, JSON |5657### Optional Inputs58| Information | Description | Accepted Formats |59|---|---|---|60| Units | Decomposition units if project was decomposed | Markdown, YAML, JSON |61| NFR specs | Non-functional requirements | Markdown, YAML, JSON |62| Testing strategy | Testing architecture, frameworks, coverage mapping | Markdown (design/testing-strategy.md) |63| Existing task list | Pre-existing tasks to validate and enrich | Markdown, YAML, JSON, plain text |6465### Outputs66| Artifact | Default Path |67|---|---|68| decisions-tasks.md | `{WORKFLOW_DIR}/{feature}/decisions-tasks.md` |69| tasks.md | `{SPECS_DIR}/{feature}/tasks.md` |7071---7273## Initialization74751. Detect environment (per shared base)762. Resolve feature name (per shared base)773. Read manifest at `{WORKFLOW_DIR}/{feature}/aidlc-manifest.yaml` if it exists784. Resolve design documents (manifest → conventional path → ask)795. If blueprints exist, read Summary sections. Read `resources.md` in full.806. **Incremental mode**: Scope to unit's design at `{SPECS_DIR}/{feature}/units/{unit}/design/*`8182---8384## Process8586Execute actions sequentially. **Load the action file when you reach that step — not before.**8788| Step | Action | Load |89|---|---|---|90| 1 | Generate D4 decisions + validate | `{SKILL_DIR}/actions/decision-gate.md` |91| 2 | Generate tasks + execution waves | `{SKILL_DIR}/actions/generate.md` |92| 3 | Edit (if user requests changes) | `{SKILL_DIR}/actions/edit.md` |9394---9596## References9798For task strategies, read `{SKILL_DIR}/references/task-strategies.md` when generating.99For operations guidance, read `{SKILL_DIR}/references/operations.md` for infra/deploy tasks.100101---102103## Skill Handoff104105**Next skill**: `aidlc-implement` (on user approval of tasks).106107---108109## Phase-Specific Rules110111- For incremental mode: write full audit entry to `{WORKFLOW_DIR}/{feature}/units/{unit}/audit.md` and a one-line summary to `{WORKFLOW_DIR}/{feature}/audit.md`.112- **Audit actions**: decision-gate, validation, generation, approval, edit.113114---115116## Context Recovery117118If context is lost mid-phase, follow `aidlc/shared/base.md` Context Recovery, then:119- Check `artifacts.tasks.status` (or `units[{unit}].artifacts.tasks.status`):120 - Not present → load `actions/decision-gate.md` (start from D4)121 - Check if `decisions-tasks.md` exists → if yes, load `actions/generate.md`122 - `"draft"` → load `actions/generate.md` (re-present results for approval)123 - `"approved"` → phase complete, hand off to implement
aws-samples