KodingDev

Run a task autonomously with reversible defaults and a reviewable handback.

Turn an idea into an approved implementation spec through collaborative design.

Inspect and commit the intended local changes cleanly.

Diagnose bugs, test failures, and unexpected behavior from evidence before changing code.

Isolate independent or context-heavy work when parallelism or fresh context materially improves the task.

Capture hard-won engineering knowledge in durable project documentation.

Implement an approved spec or clearly defined piece of work.

Verify unstable or unfamiliar external API and library contracts that materially affect the task.

Golden-from-the-start engineering: build the durable version of anything new. Use when designing or building a new feature, API, module, or package, when professionalizing a prototype, or when the user says "golden", "gorgeous", "prod grade", or "built to last".

Orchestrate multi-agent work. Use when dispatching subagents or parallel agents, running a workflow, fanning out over many files or chunks, mining, migrating, or auditing at scale, or choosing which model tier runs each stage.

Turn ideas and design docs into a sprint-ready, dependency-linked backlog — reconcile intake, break down, write tickets, sequence, assign, and shape for Jira or Linear.

Audit an AWS CDK module, construct, stack, or package against AWS CDK best practices (project structure, IAM/grants, constructs, testing, CDK Nag, removal policies, anti-patterns). Use when the user asks to review/check/audit CDK code, a CDK construct or stack, a cdk module, or asks "is this CDK code following best practices".