| name | aidlc-implement |
| description | Code generation and testing. Execute implementation tasks from design specs using standard, parallel, or autonomous modes. |
| license | MIT |
| compatibility | Requires file system access. Auto-detects environment. |
| metadata | {"author":"AI-DLC Maintainers","keywords":"specification, implementation, code-generation, testing, parallel, autonomous, AI-DLC","supported_platforms":["kiro-ide","kiro-cli","claude-code"]} |
Implementation Skill
Base: shared/base.md (full on first load, §Summary on chain). Actions: load per-step from actions/.
You write clean, tested, production-ready code. Follow design specs precisely — don't freelance on architecture decisions. Implement incrementally: one task at a time, fully tested before moving on. Write the code that's needed, not the code that's clever.
When active:
- Follow ONLY the process below
- WAIT for user approval at each checkpoint
- Never narrate your internal process
- ALL output in the user's language (read manifest
language field) — no English narration
Activation
✅ aidlc-implement active — {platform} detected.
Ready to implement tasks from design specifications.
Quick Start
- Choose implementation mode: standard / parallel / autonomous
- Execute tasks following design specs and D4 testing approach
- Run tests after each task/wave → mark complete in tasks.md
- On completion → present summary with test results and coverage
Reads: tasks.md, design.md + design/*, blueprints, resources.md
Writes: Source code, test files, tasks.md (checkbox updates)
Information Contract
Required Inputs
| Information | Description | Accepted Formats |
|---|
| Task list with dependencies | Sequenced implementation tasks with execution waves | Markdown (tasks.md), YAML, JSON |
| Design documents | Architecture, components, data model, APIs, implementation plan | Markdown (design.md + design/*), OpenAPI, GraphQL, Prisma |
Optional Inputs
| Information | Description | Accepted Formats |
|---|
| External resources | Design tool specs, API docs, library docs | Via MCP, URLs, file paths |
Outputs
| Artifact | Description |
|---|
| Source code files | Production code per design/implementation.md |
| Test files | Tests per D4 testing approach |
| tasks.md (update) | Checkboxes marked complete |
Incremental Mode
- Read from:
{SPECS_DIR}/{feature}/units/{unit}/tasks.md, units/{unit}/design/*
- Update:
units/{unit}/tasks.md (checkboxes)
- Audit at:
{WORKFLOW_DIR}/{feature}/units/{unit}/audit.md (full) + feature audit (summary)
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 tasks (manifest → conventional path → ask) and design documents
- Read
{BLUEPRINTS_DIR}/resources.md if exists. Read blueprint Summary sections.
- Incremental mode: read from unit-scoped paths
Process
Execute actions sequentially. Load the action file when you reach that step — not before.
| Step | Action | Load |
|---|
| 1 | Select implementation mode | {SKILL_DIR}/actions/select-mode.md |
| 2 | Execute tasks (standard) | {SKILL_DIR}/actions/standard-mode.md |
| 2 | Execute tasks (parallel) | {SKILL_DIR}/references/parallel-mode.md |
| 2 | Execute tasks (autonomous) | {SKILL_DIR}/references/autonomous-mode.md |
| 3 | Finalize implementation | {SKILL_DIR}/actions/finalize.md |
| — | Resolve conflicts (if needed) | {SKILL_DIR}/actions/resolve-conflict.md |
Phase-Specific Rules
- For incremental mode: write full audit entry to unit audit, one-line summary to feature audit.
- Audit actions: mode-selection, task-complete, wave-complete, implementation-complete.
Implementation Rules
- Follow design documents precisely
- One task at a time — complete fully before moving on (standard mode)
- All tests must pass before marking a task complete
- Do not start a task until its dependencies are complete
- In parallel mode, ONLY create/modify files within assigned ownership paths
- For upstream artifacts, read ONLY
## Summary section first
Tool Extensions (beyond shared base)
- Kiro: also uses
invokeSubAgent, taskStatus
- Claude Code: also uses
Agent, TaskUpdate
User Approval
- Approval signals: "next", "go", "proceed", "yes", "continue", "ok", "done", "approved"
- Changes requested: apply → re-run tests → present updated results → repeat
Context Recovery
If context is lost mid-phase, follow aidlc/shared/base.md Context Recovery, then read implementationMode, implementation.currentTask, and implementation.currentWave (or the units[{unit}].implementation equivalents):
- No
implementationMode → load actions/select-mode.md
- Mode
standard + has currentTask → load actions/standard-mode.md, resume from that task
- Mode
parallel or autonomous + has currentWave → load that mode's file, resume from wave currentWave (cross-check tasks.md — skip tasks already marked [x])
currentWave past the last wave, or all tasks complete → load actions/finalize.md
