SKILL.md--- name: kiro-impl description: Implement approved tasks using TDD with native subagent dispatch. Runs all pending tasks autonomously or selected tasks manually. disable-model-invocation: true allowed-tools: Read, Write, Edit, MultiEdit, Bash, Glob, Grep, Agent, WebSearch, WebFetch argument-hint: <feature-name> [task-numbers] [--review required|inline|off] --- # kiro-impl Skill ## Role You operate in two modes: - **Autonomous mode** (no task numbers): Dispatch a fresh subagent per task, with independent review after each - **Manual mode** (task numbers provided): Execute selected tasks directly in the main context ## Core Mission - **Success Criteria**: - All tests written before implementation code - Code passes all tests with no regressions - Tasks marked as completed in tasks.md - Implementation aligns with design and requirements - Task completion follows the selected review mode ## Review Mode - Default review mode is `required` - Accept explicit forms: `--review required|inline|off` - Also accept clear natural-language opt-outs such as `skip review` or `without review` as `off` - If the request is ambiguous, keep `required` ## Execution Steps ### Step 1: Gather Context Reuse steering/spec context already available from conversation; load missing context below. Select skills for the current task even when steering/spec context is already available: - `{{KIRO_DIR}}/specs/{feature}/spec.json` and `tasks.md` for approvals, task selection, and dependencies - Referenced sections of `requirements.md` and `design.md`, expanding to related contracts as needed for the selected task - Core steering context: `product.md`, `tech.md`, `structure.md` - Additional steering files only when directly relevant to the selected task's boundary, runtime prerequisites, integrations, domain rules, security/performance constraints, or team conventions that affect implementation or validation - Use explicitly requested skills and task-relevant local skills/playbooks, including design, accessibility, and UX. Select by description and read only needed guidance, even for small tasks; preserve required checks and host/project rules. #### Preflight **Validate approvals**: - Verify tasks are approved in spec.json (stop if not, see Safety & Fallback) **Discover validation commands**: - Inspect repository-local sources of truth in this order: project scripts/manifests (`package.json`, `pyproject.toml`, `go.mod`, `Cargo.toml`, app manifests), task runners (`Makefile`, `justfile`), CI/workflow files, existing e2e/integration configs, then `README*` - Derive a canonical validation set for this repo: `TEST_COMMANDS`, `BUILD_COMMANDS`, and `SMOKE_COMMANDS` - Prefer commands already used by repo automation over ad hoc shell pipelines - For `SMOKE_COMMANDS`, choose the lightest trustworthy runtime-liveness check for the app shape (for example: root URL load, Electron launch, CLI `--