Skip to main content
aifeatures.ai
Teams who want CDK and property tests before application code

The Kiro spec-to-CDK stack

Notion holds the PRD, Bedrock checks policy, Kiro writes specs, tests, and CDK. Not a v0 mock and not a Lovable sandbox.

Who owns what

  1. Notion AI

    The PRD — invariants, entities. Not CDK and not the test runner.

    Try Notion AI (opens in a new tab)

  2. Zapier

    The sign-off — Notion approved → Kiro. Not the compiler.

    Try Zapier (opens in a new tab)

  3. Amazon Bedrock

    The guardrail — internal KB, what cloud may not do. Not git.

    Try Amazon Bedrock (opens in a new tab)

  4. Kiro

    The contract — properties, microservice, CDK. Not the company wiki.

    Try Kiro (opens in a new tab)

How to use this stack

  1. Lock the invariants in Notion. Zapier fires on approve — not on a chat prompt.
  2. Bedrock scores the spec against the internal KB. Fail closed if policy is silent.
  3. Kiro emits properties, then code and CDK until those tests pass.
  4. This is not spec-to-prototype (Eraser + v0). Not mvp-to-production-refactor (Lovable).