AI-DLC Core Workflow
AI-DLC is an adaptive software development workflow that intelligently tailors itself to your specific needs.
Activation Triggers
Use this skill when:
- User request starts with "Using AI-DLC, ..."
- Complex software development requiring structured planning
- Projects needing requirements analysis, design, and implementation
MANDATORY: Rule Details Loading
CRITICAL: When performing any phase, you MUST read and use relevant content from references/ directory.
Common Rules: ALWAYS load at workflow start:
- Load
references/common/process-overview.mdfor workflow overview - Load
references/common/session-continuity.mdfor session resumption - Load
references/common/content-validation.mdfor validation requirements - Load
references/common/question-format-guide.mdfor question formatting
The Three-Phase Lifecycle
INCEPTION PHASE - Planning & Architecture
Purpose: Determines WHAT to build and WHY
| Stage | Execution | Details |
|---|---|---|
| Workspace Detection | ALWAYS | references/inception/workspace-detection.md |
| Reverse Engineering | CONDITIONAL | references/inception/reverse-engineering.md |
| Requirements Analysis | ALWAYS | references/inception/requirements-analysis.md |
| User Stories | CONDITIONAL | references/inception/user-stories.md |
| Workflow Planning | ALWAYS | references/inception/workflow-planning.md |
| Application Design | CONDITIONAL | references/inception/application-design.md |
| Units Generation | CONDITIONAL | references/inception/units-generation.md |
CONSTRUCTION PHASE - Design, Implementation & Test
Purpose: Determines HOW to build it
| Stage | Execution | Details |
|---|---|---|
| Functional Design | CONDITIONAL | references/construction/functional-design.md |
| NFR Requirements | CONDITIONAL | references/construction/nfr-requirements.md |
| NFR Design | CONDITIONAL | references/construction/nfr-design.md |
| Infrastructure Design | CONDITIONAL | references/construction/infrastructure-design.md |
| Code Generation | ALWAYS | references/construction/code-generation.md |
| Build and Test | ALWAYS | references/construction/build-and-test.md |
OPERATIONS PHASE - Placeholder
Purpose: How to DEPLOY and RUN it (future expansion)
See references/operations/operations.md for details.
Key Principles
- Adaptive Execution: Only execute stages that add value
- Flexible Depth: Adjust depth based on complexity (minimal/standard/comprehensive)
- Human-in-the-Loop: Explicit approval required at every critical decision point
- Complete Audit Trail: Log ALL interactions with ISO 8601 timestamps
- User Control: User can request stage inclusion/exclusion
Workflow Initialization
- Create
aidlc-docs/aidlc-state.mdusingreferences/common/state-template.md - Create
aidlc-docs/audit.mdusingreferences/common/audit-template.md - Display welcome message from
references/common/welcome-message.md(once per workflow) - Execute Workspace Detection
- Proceed through phases based on workflow plan
Directory Structure
<WORKSPACE-ROOT>/
├── [project-specific structure]
│
└── aidlc-docs/
├── inception/
│ ├── plans/
│ ├── reverse-engineering/
│ ├── requirements/
│ ├── user-stories/
│ └── application-design/
├── construction/
│ ├── plans/
│ ├── {unit-name}/
│ └── build-and-test/
├── operations/
├── aidlc-state.md
└── audit.md
Stage Execution Pattern
All stages follow the Planning → Generation pattern:
Part 1: Planning
- Create plan with checkboxes for each step
- Generate context-appropriate questions using [Answer]: tags
- Collect user answers
- Analyze answers for ambiguities
- Create follow-up questions if ambiguities found
- Wait for explicit approval
Part 2: Generation
- Load approved plan
- Execute each step sequentially
- Mark checkboxes [x] immediately after completion
- Generate artifacts
- Present completion message
- Wait for explicit approval
Critical Rules
- NEVER proceed without explicit user approval
- ALWAYS log interactions in audit.md
- NEVER summarize user input in audit log - capture complete raw input
- Application code goes to workspace root, NEVER to aidlc-docs/
- ALWAYS use multiple choice question format with [Answer]: tags
- ALWAYS validate content before file creation
Reference Files
For detailed guidance, load the appropriate reference file:
Common
references/common/process-overview.mdreferences/common/question-format-guide.mdreferences/common/content-validation.mdreferences/common/depth-levels.mdreferences/common/terminology.mdreferences/common/session-continuity.mdreferences/common/error-handling.mdreferences/common/overconfidence-prevention.mdreferences/common/ascii-diagram-standards.mdreferences/common/state-template.mdreferences/common/audit-template.mdreferences/common/welcome-message.mdreferences/common/workflow-changes.md
Inception
references/inception/workspace-detection.mdreferences/inception/reverse-engineering.mdreferences/inception/requirements-analysis.mdreferences/inception/user-stories.mdreferences/inception/workflow-planning.mdreferences/inception/application-design.mdreferences/inception/units-generation.md
Construction
references/construction/functional-design.mdreferences/construction/nfr-requirements.mdreferences/construction/nfr-design.mdreferences/construction/infrastructure-design.mdreferences/construction/code-generation.mdreferences/construction/build-and-test.md
Operations
references/operations/operations.md