name	cdk-feedback-harness
description	Use for AWS CDK changes or failures in this repository, especially when you need to choose the leftmost feedback stage, prefer package scripts over raw commands, convert repeated failures into tests or validations, and report findings with templates/feedback-report.md. Do not use for generic non-CDK work.

CDK Feedback Harness

This skill packages the repository's AWS CDK "echolocation" workflow. Keep the skill lean and load only the references that match the current stage.

Read references/workflow.md for command selection, progression rules, and reporting requirements.
Read doc/cdk-lifecycle-feedback-map.md when you need to choose the current stage or decide how far right to move.
Read doc/feedback-model.md when you need to turn a deploy-side failure into a faster local guardrail.
Read templates/feedback-report.md only when you need to return a structured feedback report.

Identify the smallest affected stack or construct first.
Start at the leftmost stage that can validate the current change.
Stop at the first failing stage, isolate the first causal point, and fix that before moving on.
If the same kind of failure could recur, add a guardrail before considering the work done.
After a stage passes, move only one stage to the right.
Synthesize once and reuse cdk.out for downstream diff, publish-assets, and deploy commands.

Construct: template shape, resource counts, critical properties, constructor-time validation.
Prepare: cross-resource or org-wide rules enforced with Aspects or cdk-nag.
Validate: late-bound or synth-time constraints with node.addValidation().
Synthesize: Cloud Assembly generation and cdk.out inspection.
Difference: planned change review and environment drift checks.
Publish: asset build or upload isolation.
Deploy: CloudFormation events, hotswap behavior, or final environment application.

references/workflow.md: package manager detection, script priority, standard loop, dev/prod deploy rules, reporting expectations.
doc/cdk-lifecycle-feedback-map.md: what each stage checks and where fixes usually land.
doc/feedback-model.md: how to move failures left into tests, Aspects, validations, or asset steps.
templates/feedback-report.md: structured output for stage reports.

CDK Feedback Harness

This skill packages the repository's AWS CDK "echolocation" workflow. Keep the skill lean and load only the references that match the current stage.

Quick start

Read references/workflow.md for command selection, progression rules, and reporting requirements.

Read doc/cdk-lifecycle-feedback-map.md when you need to choose the current stage or decide how far right to move.

Read doc/feedback-model.md when you need to turn a deploy-side failure into a faster local guardrail.

Read templates/feedback-report.md only when you need to return a structured feedback report.

Core rules

Identify the smallest affected stack or construct first.

Start at the leftmost stage that can validate the current change.

Stop at the first failing stage, isolate the first causal point, and fix that before moving on.

If the same kind of failure could recur, add a guardrail before considering the work done.

After a stage passes, move only one stage to the right.

Synthesize once and reuse cdk.out for downstream diff, publish-assets, and deploy commands.

Stage routing

Construct: template shape, resource counts, critical properties, constructor-time validation.

Prepare: cross-resource or org-wide rules enforced with Aspects or cdk-nag.

Validate: late-bound or synth-time constraints with node.addValidation().

Synthesize: Cloud Assembly generation and cdk.out inspection.

Difference: planned change review and environment drift checks.

Publish: asset build or upload isolation.

Deploy: CloudFormation events, hotswap behavior, or final environment application.

References

references/workflow.md: package manager detection, script priority, standard loop, dev/prod deploy rules, reporting expectations.

doc/cdk-lifecycle-feedback-map.md: what each stage checks and where fixes usually land.

doc/feedback-model.md: how to move failures left into tests, Aspects, validations, or asset steps.

templates/feedback-report.md: structured output for stage reports.

cdk-feedback-harness