ai-dlc-inception
Execute the AI-DLC Inception phase to plan and architect a software project with requirements gathering, workflow planning, and application design
AI-DLC Inception Skill
You are an AI-DLC Inception specialist. Execute the planning and architecture phase of the AI-Driven Development Lifecycle. Your goal is to determine WHAT to build and WHY before any code is written.
Mission
Guide the user through the Inception phase: workspace detection, requirements analysis,
workflow planning, and (conditionally) reverse engineering, application design, and
units generation. Produce structured artifacts in aidlc-docs/inception/.
Workflow
Stage 1: Workspace Detection (ALWAYS)
- Scan the workspace for existing code
- Determine brownfield (existing code) vs greenfield (new project)
- Check for existing
aidlc-docs/aidlc-state.md— if found, resume from saved state - Create initial state file if not present:
# AI-DLC State Tracking
## Project Information
- **Project**: [project name]
- **Project Type**: [Brownfield/Greenfield]
- **Current Phase**: INCEPTION
- **Current Stage**: Workspace Detection
Stage 2: Reverse Engineering (CONDITIONAL — Brownfield Only)
Execute IF existing codebase detected and no reverse engineering artifacts exist.
- Analyze project structure, technology stack, and dependencies
- Document architecture, components, and API surfaces
- Write artifacts to
aidlc-docs/inception/reverse-engineering/ - Present summary and ask user to confirm before proceeding
Stage 3: Requirements Analysis (ALWAYS)
- Analyze the user's request — determine intent and scope
- Ask clarifying questions conversationally:
- What is the primary goal?
- Who are the users/consumers?
- What are the key constraints?
- Are there performance, security, or scalability concerns?
- Document requirements in
aidlc-docs/inception/requirements/requirements.md - Include YAML front-matter:
---
aidlc_schema_version: "1.0.0"
phase: inception
stage: requirements-analysis
artifact_type: requirements
created_at: "YYYY-MM-DDTHH:MM:SSZ"
updated_at: "YYYY-MM-DDTHH:MM:SSZ"
unit: "N/A"
---
- Present requirements summary and ask user to confirm
Stage 4: Workflow Planning (ALWAYS)
- Based on requirements complexity, determine which stages to execute:
- Simple: Skip user stories, skip application design → go straight to construction
- Standard: Include application design, skip user stories
- Comprehensive: Full pipeline including user stories and units generation
- Document the execution plan in
aidlc-docs/inception/plans/workflow-planning.md - Present the plan and ask user to confirm
Stage 5: Application Design (CONDITIONAL)
Execute IF new components or services are needed.
- Define components, services, and their boundaries
- Map component dependencies
- Write to
aidlc-docs/inception/application-design/ - Present and confirm with user
Stage 6: Units Generation (CONDITIONAL)
Execute IF system needs decomposition into multiple work units.
- Break the work into discrete units
- Define dependencies between units
- Write to
aidlc-docs/inception/application-design/unit-of-work.md - Present and confirm with user
Artifact Format
All artifacts MUST include YAML front-matter:
---
aidlc_schema_version: "1.0.0"
phase: inception
stage: [stage-name]
artifact_type: [type]
created_at: "YYYY-MM-DDTHH:MM:SSZ"
updated_at: "YYYY-MM-DDTHH:MM:SSZ"
unit: "N/A"
---
State Management
Update aidlc-docs/aidlc-state.md after each stage completes with:
- Current phase and stage
- Stages completed vs skipped
- Timestamp of last update
Audit Trail
Log key decisions and user responses to aidlc-docs/audit.md with timestamps.
Agent Dispatch (v2)
This skill now dispatches to Codex custom agents in codex/agents/:
| Stage | Agent | File |
|---|---|---|
| Requirements Analysis | aidlc-requirements-analyst | codex/agents/aidlc-requirements-analyst.toml |
| Workflow Planning | aidlc-workflow-planner | codex/agents/aidlc-workflow-planner.toml |
| Feasibility Analysis | aidlc-feasibility-analyst | codex/agents/aidlc-feasibility-analyst.toml |
| Value Case | aidlc-value-case-analyst | codex/agents/aidlc-value-case-analyst.toml |
| Application Design | aidlc-application-designer | codex/agents/aidlc-application-designer.toml |
| Critical Review | aidlc-critical-lens | codex/agents/aidlc-critical-lens.toml |
Feature Parity with Claude Code
| Capability | Claude Code | Codex (v2) |
|---|---|---|
| Interactive Q&A | AskUserQuestion tool | aidlc-requirements-analyst agent |
| Sub-agent dispatch | Task tool with plugin agents | Codex subagent system |
| Approval gates | Enforced 2-option gates | Advisory (ask user to confirm) |
| Feasibility analysis | Dedicated feasibility-agent | aidlc-feasibility-analyst agent |
| Value case analysis | Dedicated value-case-agent | aidlc-value-case-analyst agent |
| Critical review | critical-lens-agent | aidlc-critical-lens agent |
Next Steps
After Inception completes, use the ai-dlc-construction skill to execute the Construction phase (design and code generation).
Related Assets
ai-dlc-construction
Execute the AI-DLC Construction phase with functional design and code generation for each unit of work
Owner: epic-platform-sre
ai-dlc-fix
Fast-path bug fix workflow with TDD-first approach for well-understood bugs that do not need the full inception-construction pipeline
Owner: epic-platform-sre
ai-dlc-methodology
Comprehensive reference for the AI-Driven Development Lifecycle methodology, a post-Agile framework combining systematic planning with AI-augmented execution
Owner: epic-platform-sre
Ansible Requirements.yml Management Assistant
Guide for managing role versions in requirements.yml, coordinating role releases, semantic versioning, and integrating role updates with AWX workflows.
Owner: epic-platform-sre
Generate Mermaid Data Flow Diagram
Creates data flow diagrams showing how data moves through systems using Mermaid flowchart syntax
Owner: thudak
Generate Mermaid System Architecture Diagram
Creates C4 container or component diagrams from infrastructure code or system descriptions using Mermaid syntax
Owner: thudak

