cdk-contribution-skill

To automate an AWS CDK contribution workflow, you can use an orchestrator that coordinates subagents and SOPs across issue analysis, planning, build, validation, and review phases to produce structured PR artifacts. It enforces human approval gates before implementation.

The best way to coordinate subagents for a CDK issue-to-PR pipeline is using a unified orchestration skill that dispatches specialized agents for solution design, testing, and documentation, while handing off outputs sequentially under a dedicated contributions directory.

The human approval gate in a CDK contribution pipeline pauses the automated workflow after issue analysis and planning phases, ensuring manual oversight before the implementation specialist subagent begins building the PR-ready changes.

Automated CDK contribution workflow outputs are stored under the .kiro/contributions/<ISSUE_NUMBER>/ directories, where deliverables from each phase are saved to hand off to the next phase and generate a final PR-ready summary.

Yes, you can use a contribution orchestrator to establish a repeatable and auditable CDK workflow. It coordinates multi-phase pipelines with subagents and standard operating procedures to streamline changes while preserving human oversight.

Subagents involved in an automated CDK contribution pipeline include the Issue Analyst, Solution Architect, Implementation Specialist, Test Engineer, QA, Documentation, and Security Review agents, all coordinated by a central orchestrator.