Start here

Use AIDLC Studio in the first ten minutes.

If you are new to AI DLC or AI SDLC workflows, do not start by reading everything. Pick your situation, preview the route, and run one real change through the workflow.

One path

First-time visitor flow

Follow these steps before exploring the full toolkit.

By role

Choose the path that matches your job

AIDLC works best when each role sees its own responsibility clearly.

Product

Start with user problem, success metric, non-goals, risk, and acceptance criteria.

  1. Run the workflow generator.
  2. Preview the AI Feature Brief in the Starter Kit.
  3. Approve the demo against acceptance criteria.
Generate product packet

Engineering

Start with context, allowed scope, prompt contract, verification, and review notes.

  1. Preview AGENTS.md or CLAUDE.md.
  2. Use the Starter Kit for the model-agnostic prompt contract.
  3. Record tests and evidence before merge.
Get the Starter Kit

Governance

Start with risk route, required gates, evidence ledger, and exception handling.

  1. Run the maturity assessment.
  2. Review market references.
  3. Use the Starter Kit for the evidence ledger and review gate.
Assess maturity

Leadership

Start with why this is different from generic AI governance or MLOps.

  1. Read the references comparison.
  2. Pick one pilot team.
  3. Measure adoption with the maturity score.
Compare references

More ways to use AIDLC Studio

Guides for teams working by tool, platform, or workflow

Plain language

What AIDLC Studio is, and what it is not

It is

  1. A practical workflow for teams using AI coding assistants.
  2. Model-agnostic: usable with Claude, Codex, Copilot, or other tools.
  3. Evidence-first: every AI output remains a proposal until reviewed and verified.
  4. Built for product and engineering collaboration, not just engineering prompts.

It is not

  1. A replacement for NIST, ISO, OWASP, or company governance policy.
  2. A model training lifecycle or MLOps platform.
  3. A promise that AI-generated code is safe by default.
  4. A vendor-specific prompt library.