Skip to main content

Overview

The AI-DLC flow in specs.md provides two bolt types, each optimized for different types of work. Choosing the right bolt type ensures you have the appropriate level of rigor and structure for your task.

Quick Decision Guide

The Inception Agent automatically selects the appropriate bolt type based on your requirements. If you disagree with its choice, you can change it during the human checkpoint review.
1

Does it involve complex business logic or domain rules?

Yes → Use DDD Construction BoltNo → Continue to next question
2

Is it UI, integration, utility, or straightforward CRUD?

Yes → Use Simple Construction Bolt

DDD Construction Bolt

When to Use

Complex domain logic requiring careful modeling and design decisions.

Best For

  • Core business logic with complex rules
  • Domain models with aggregates, entities, and value objects
  • Services that encode business knowledge
  • Features where incorrect logic has significant consequences
  • Bounded contexts with rich domain models

Stages

StagePurposeOutput
1. Domain ModelModel business logic using DDD principlesDomain model document
2. Technical DesignApply patterns, define interfacesTechnical design document
3. ADR AnalysisDocument significant decisionsArchitecture Decision Record
4. ImplementGenerate production codeImplementation
5. TestVerify correctnessTest suite

Example Use Cases

Orders involve complex state transitions, pricing rules, inventory checks, and payment processing. DDD helps model these business rules explicitly.
Interest calculations, fee structures, and compliance rules require careful domain modeling to ensure correctness.
Availability rules, conflict detection, and reservation logic benefit from explicit domain modeling.
State machines, transition rules, and approval chains require careful design.

Simple Construction Bolt

When to Use

Straightforward implementations that don’t require extensive domain modeling.

Best For

  • Frontend pages and components
  • Simple CRUD endpoints
  • External API integrations
  • Utilities and helper modules
  • CLI commands and scripts
  • Configuration and setup code

Stages

StagePurposeOutput
1. PlanDefine what to buildimplementation-plan.md
2. ImplementWrite the codeSource code + implementation-walkthrough.md
3. TestVerify the implementationTests + test-walkthrough.md

Example Use Cases

A React component displaying user information with edit capabilities. Clear requirements, no complex business logic.
Connecting to a third-party API with well-documented endpoints. Focus on correct integration, not domain modeling.
Data display and basic filtering. CRUD operations with straightforward UI.
A command-line utility for common operations. Clear inputs and outputs.

Comparison Table

AspectDDD ConstructionSimple Construction
Stages53
DurationHours to daysHours
DocumentationExtensiveLight
Design RigorHighLow
OutputProduction code + artifactsProduction code
Human Reviews5 checkpoint reviews3 checkpoint reviews

Common Mistakes

Choosing the wrong bolt type leads to either over-engineering simple tasks or under-designing complex ones.

Over-Engineering (DDD for Simple Tasks)

Symptom: Using DDD Construction for a simple settings page. Problem: Excessive ceremony for straightforward work. Domain modeling for CRUD operations wastes time without adding value. Solution: Use Simple Construction for UI, utilities, and integrations.

Under-Engineering (Simple for Complex Tasks)

Symptom: Using Simple Construction for complex pricing logic. Problem: Skipping domain modeling leads to implicit business rules scattered in code. Bugs emerge as edge cases are missed. Solution: Use DDD Construction when business logic is non-trivial.

Next Steps

Bolts Overview

Core concepts and bolt mechanics

Construction Agent

Learn how the agent executes bolts