Skip to main content

Overview

Simple Flow uses a single agent (/specsmd-agent) that guides you through all three phases: Requirements, Design, and Tasks.

Invoking the Agent

These are NOT command-line commands. These are prompts you type in your AI coding tool’s chat interface.

Agent Capabilities

The Simple Flow agent handles:

Spec Creation

Generate requirements, design, and task documents from a feature idea

Phase Navigation

Move through Requirements → Design → Tasks with explicit approval gates

Task Execution

Execute implementation tasks one at a time with review

Context Loading

Resume work on existing specs by reading saved documents

Commands

Workflow

1. Create a Spec

The agent:
  1. Derives a feature name (user-dashboard)
  2. Generates requirements.md
  3. Waits for approval

2. Approve or Revise

To approve: Say “yes”, “approved”, or “looks good” To revise: Provide specific feedback like “Add a requirement for export functionality”

3. Progress Through Phases

After approving requirements:
  • Agent generates design.md
  • Wait for approval
  • Agent generates tasks.md
  • Wait for approval

4. Execute Tasks

The agent executes one task, then waits for review before continuing.

Agent Session Lifecycle

1

Context Loading

Agent reads existing spec files from specs/{feature-name}/
2

Phase Detection

Agent determines current phase based on which files exist and their status
3

Generation or Execution

Agent generates the next document or executes the next task
4

Approval Gate

Agent waits for explicit approval before proceeding
The agent is stateless. It reads spec files at startup. Ensure documents are saved after each step.

Best Practices

Good: “User auth with email/password and session management”Too vague: “Login feature”The more specific you are, the better the generated specs.
Don’t rush through approvals. The design phase influences task generation, and tasks influence implementation quality.
The agent pauses after each task for review. If you’re confident, say “continue until done” or “go yolo”.
Checkpoint tasks run the test suite. Don’t skip them—they catch issues early.

Comparison with Other Flows