aidlc-for-claude

AI-DLC for Claude Code

A Claude Code plugin that implements the AI-DLC (AI-Driven Development Life Cycle) methodology -- a structured, adaptive software development workflow that guides AI assistants through disciplined three-phase development.

AI-DLC intelligently adapts to your project: simple changes execute only essential stages, while complex projects receive comprehensive treatment with full safeguards.

Documentation | Apache-2.0 License

Installation

In the Claude Code chat, run these two commands:

/plugin marketplace add mateon01/aidlc-for-claude
/plugin install aidlc-for-claude

Quick Start

/aidlc

That's it. The orchestrator detects your workspace (greenfield or brownfield), gathers requirements through interactive Q&A, and walks through each phase with you. Every stage requires your approval before proceeding.

To run a specific stage independently:

/aidlc-requirements-analysis
/aidlc-code-generation

How It Works

AI-DLC has three phases. Each phase contains stages that may execute conditionally based on your project's needs.

+-----------------------------------------------------------------------+
|                     INCEPTION (WHAT and WHY)                          |
|                                                                       |
|  Workspace Detection --> [Scope Assessment (brownfield)]              |
|  --> Reverse Engineering --> Requirements Analysis                    |
|  --> User Stories --> Workflow Planning --> Application Design         |
|  --> Units Generation                                                 |
+-----------------------------------+-----------------------------------+
                                    |
                                    v
+-----------------------------------------------------------------------+
|                     CONSTRUCTION (HOW)                                |
|                                                                       |
|  System NFR Assessment -->                                            |
|  FOR each unit (sequential or parallel):                              |
|    Functional Design --> NFR Requirements --> NFR Design               |
|    --> Infrastructure Design --> Code Generation                      |
|                                                                       |
|  Build and Test (after all units) + security scan + coverage          |
|  Operations (CI/CD, PR Review, Dockerfile, .env, README, deploy)     |
+-----------------------------------+-----------------------------------+
                                    |
                                    v
+-----------------------------------------------------------------------+
|                     OPERATIONS (SHIP)                                 |
|                                                                       |
|  Deployment Checklist --> CI/CD Pipeline --> Dockerfile                |
|  --> .env Template --> Developer README --> Verification Script        |
+-----------------------------------------------------------------------+

Stage Execution

Not every stage runs every time. After Workflow Planning, an execution plan determines which stages are needed:

Condition	Stages Executed
Simple bug fix	Workspace Detection, Requirements, Workflow Planning, Code Generation, Build and Test
Simple brownfield (fast path)	Workspace Detection, Reverse Engineering, Workflow Planning (minimal), Code Generation, Build and Test
New feature (greenfield)	All INCEPTION + all CONSTRUCTION stages
Brownfield modification	Adds Reverse Engineering, adapts scope based on existing codebase
Infrastructure-only change	Skips User Stories, Functional Design; includes Infrastructure Design

You can override any recommendation at the Workflow Planning approval gate.

Commands