cdk-dev

Automating AWS CDK implementation from design documents involves extracting issue specifications, referencing design docs, generating CDK code, running tests, and synthesizing CloudFormation templates. This Skill executes that end-to-end workflow across six phases.

CDK synthesis automation works by reading issue files from docs/issues/, extracting target files and labels, determining implementation policy from design docs, generating code, and running npx cdk synth to produce CloudFormation templates with recommended next actions.

The best way to translate issue specifications into CDK code is using a six-phase workflow that enforces CDK rules, generates code updates, validates with npm test, and synthesizes templates, providing phase-by-phase results and next actions.

Yes, you need issue files under docs/issues/ and design documents to automate infrastructure synthesis with CDK. The workflow reads these inputs to determine implementation policy, target files, and labels before generating code and running synthesis.

You can automate test execution and CloudFormation synthesis for AWS infrastructure projects by running npm test to validate generated CDK code and npx cdk synth to generate templates, with the workflow reporting results and recommended actions.

CDK synthesis can fail after automated code generation if the generated code violates CDK rules or design specifications. The workflow enforces CDK rules during generation and validates via npm test before executing npx cdk synth to catch errors.