Skip to content
New from the specs.md team — fabriqa orchestrates Claude Code, Codex, Gemini CLI & more in one workflow.Download free →
v1
Esc
navigateopen⌘Jpreview
On this page

Choose Your Flow

Compare Ideation, Simple, FIRE, and AI-DLC flows to find the right fit for your project

Four Flows, Every Use Case

specs.md offers four flows, each designed for a different stage and context. Choose the one that matches your current need.

Quick Decision Guide

Do you have a clear feature idea yet?

  • No, I’m still exploring → Use Ideation Flow (brainstorm → evaluate → shape a concept brief)
  • Yes, I know what I want to build → Continue to Step 2

Do you need execution tracking?

  • No → Use Simple Flow (spec generation only, like Kiro)
  • Yes → Continue to Step 3

Do you want adaptive or fixed ceremony?

  • Adaptive (right-size rigor based on task complexity) → FIRE Flow
  • Fixed (predictable checkpoints every time) → AI-DLC Flow

Do you hate unnecessary friction?

  • Yes (check when necessary, not everything) → FIRE Flow
  • No (prefer comprehensive documentation always) → AI-DLC Flow

Detailed Comparison

Aspect Ideation Simple FIRE AI-DLC
Optimized For Creative exploration Spec generation, prototypes Teams who hate friction Full traceability needs
Output Concept briefs Specs (req/design/tasks) Working code + walkthroughs Working code + full artifacts
Execution Planning N/A N/A Dynamic (recommends next run) Pre-planned (bolts)
Checkpoints 0 (non-blocking) 3 (phase gates) Adaptive (complexity + config) Comprehensive (fixed)
Agents 1 1 3 4
Execution Tracking No No Yes (runs, walkthroughs) Yes (bolts, stages)
Design Docs Concept briefs Basic specs When complexity warrants Always (DDD integral)
Monorepo Support No No First-class Limited
Brownfield Support No Basic First-class Alpha
Output Structure .specs-ideation/ specs/{feature}/ .specs-fire/ memory-bank/
Ceremony Style Zero friction Minimal Adaptive Comprehensive

When to Use Each Flow

Ideation Flow

  • Early-stage product discovery
  • Finding novel angles before writing a spec
  • Brainstorming sessions (solo or team)
  • Evaluating multiple feature directions before committing resources
  • When your first idea might not be the best idea

Output: spark-bank.md (ideas), flame-report.md (evaluations), concept-brief.md (shaped concepts)

Simple Flow

  • Building prototypes or MVPs
  • Generating specs for handoff to another team
  • Small features in established projects
  • Solo developers wanting structured documentation
  • Projects that don’t need AI-assisted execution

Output: requirements.md, design.md, tasks.md

FIRE Flow

FIRE is Adaptive Spec-Driven Development—it analyzes work complexity and your config to decide when to ask and when to burn through.

  • Teams who hate unnecessary friction
  • Brownfield projects with existing code
  • Monorepo architectures
  • Projects where implementation plan is often enough, but design docs when needed
  • Anyone wanting to ship fast without reckless code generation

Key Features:

  • Dynamic execution: No pre-planned runs—Builder scans work items and recommends what to run next
  • Change-friendly: Requirements changed? Just update specs, next run adapts automatically
  • Adaptive checkpoints: Based on work complexity + your autonomy preference
  • Walkthrough generation: AI documents every change for review
  • Hierarchical standards: Module-specific overrides in monorepos
  • Brownfield-first: Analyzes your existing structure and respects your patterns

AI-DLC Flow

  • Teams with multiple developers
  • Complex domain logic requiring DDD
  • Projects needing comprehensive documentation
  • Regulated environments requiring audit trails
  • Multi-stakeholder initiatives

Key Features:

  • Four specialized agents: Master, Inception, Construction, Operations
  • Domain-Driven Design: Full DDD stages in Construction
  • Complete traceability: Every decision documented
  • Mob rituals: Mob Elaboration, Mob Construction

Flow Comparison Matrix

Switching Between Flows

Flows are independent—they’re not an upgrade path. Choose based on your project needs:

However, you can:

  • Use Simple Flow to generate initial specs, then implement manually
  • Use FIRE Flow for rapid feature development within a project
  • Use AI-DLC Flow for major initiatives requiring full planning

Getting Started

Was this page helpful?