AWS CDK Contributions and the Rise of Multi-Agent Workflows
Explore the multi‑agent workflow for CDK contributions.
Document the multi‑agent workflow and share with the dev team.
Summary
AWS CDK went GA in 2019 with TypeScript and Python support, and the first contribution process involved cloning the monorepo, building packages, writing L2 constructs, and submitting PRs.
In July 2025 Kiro introduced the multi‑roles pattern, splitting the contribution workflow into distinct phases such as analysis, planning, build, and validation, each handled by a specialized agent.
The 2025 re:Invent Power feature formalised this pattern with explicit phases, approval gates, and parallelism, turning AI into a repeatable engineering process.
February 2026 saw the launch of Agent SKILL, a tool‑agnostic format that packages the entire CDK contribution workflow for use across Kiro, Claude Code, Codex, Gemini, Copilot, and OpenCode.
The cdk‑contribution‑skill repository was released in March 2026, providing a 6‑phase orchestrated workflow with clear inputs, outputs, and deliverables for each phase.
This evolution demonstrates how open‑source contributions can be automated while retaining human oversight, making the process faster and more reliable for developers worldwide.
Key changes
- AWS CDK GA in 2019 with TypeScript and Python support
- Kiro launched July 2025 with the multi‑roles pattern splitting contribution phases
- 2025 re:Invent Power formalised phases, approval gates, and parallelism
- February 2026 Agent SKILL standardized the workflow across multiple agent tools
- March 2026 cdk‑contribution‑skill released with a 6‑phase orchestrated workflow
- Each phase has defined inputs, outputs, and deliverables
- Human approval gates ensure quality control
- The workflow reduces manual setup and speeds up PR integration