AI generated a large refactor
Do not accept it as one giant change. Route it as Brownfield Flow and force a smaller boundary.
- Map current behavior.
- Split broad refactor from product intent.
- Require regression evidence.
AI SDLC playbook
These playbooks show how to route common AI coding assistant situations through AIDLC Studio without overthinking the whole framework.
Scenarios
Each scenario names the route, evidence, and Starter Kit item to use first.
Do not accept it as one giant change. Route it as Brownfield Flow and force a smaller boundary.
Route config, IAM, deployment, policy, and guardrail changes through Config/Infra Flow.
Pause before merging. Review license, maintenance, security, bundle, and architecture impact.
Use Greenfield Flow to keep the MVP, architecture, data contracts, and pilot evidence visible.
Use the evidence ledger to show intent, context, generated output, verification, acceptance, and release signals.
Use the maturity assessment and shareable score to compare teams over time.
Weekly material ideas
These are built as short evergreen prompts for future pages, workshops, or posts.
Show how reviewers inspect scope, tests, dependencies, security, and evidence.
Publish one example ledger each week for Brownfield, Greenfield, and Config/Infra work.
Compare AWS, Azure, Google Cloud, GitHub, Claude, Codex, and Copilot workflows.
Support the resource
Small donations help maintain free workflows, tutorials, references, and public learning material for product and engineering teams.