BACK_TO_SYSTEM_INDEX

From Plan to Ship

Your AI agent workflow — from requirements to production code, with full context at every step.

01 // The Workflow Loop

Agiflow provides MCP skills (prompts) for each phase of your development workflow. Your AI agent uses these to manage projects, refine tasks, and execute work systematically.

Plan
Refine
Groom
Execute
Triage

02 // Core Operations

Planning

Skill: project_plan

Break high-level requirements into concrete tasks.

// Key Actions

  • > Create 5-15 focused tasks
  • > Define acceptance criteria
  • > Group related tasks into Work Units
  • > Assign priorities and dependencies

Task Refinement

Skill: refine_task

Add detail and context to tasks before execution.

// Key Actions

  • > Add detailed acceptance criteria
  • > Document technical context
  • > Link related tasks and set dependencies
  • > Assign to team members or agents

Backlog Grooming

Skill: backlog_grooming

Prioritize and organize your backlog.

// Key Actions

  • > Review and reorder tasks by priority
  • > Move tasks between work units
  • > Identify blockers and dependencies
  • > Archive or close stale tasks

Triage & Review

Skills: triage, review_work

Review completed work, provide feedback, and iterate.

// Key Actions

  • > Review agent output and artifacts
  • > Add comments for feedback
  • > Move tasks through status columns
  • > Track progress via devInfo

03 // Execution Pipeline

Execution

Skills: run_work and run_task

1

Load Task Context

Agent loads the task via MCP — reads acceptance criteria, devInfo, and related context.

2

Understand Conventions

Before coding, calls get-file-design-pattern (Architect MCP) to understand project conventions.

3

Implement

Implements the task following acceptance criteria and discovered patterns.

4

Validate

After coding, calls review-code-change (Architect MCP) to validate against project rules.

5

Update & Commit

Updates task status and devInfo, then commits changes.

04 // Data Persistence

Session Continuity (devInfo)

Work Units maintain structured devInfo metadata that agents access via MCP. This means agents resume with full context — files changed, test results, progress.

DEVINFO_STRUCTURE
{ "devInfo": { "executionPlan": "Backend → Frontend → Tests", "progress": { "completedTasks": 2, "totalTasks": 6 }, "filesChanged": [ "backend/migrations/003_cart.sql", "backend/src/repos/CartRepo.ts" ], "testResults": { "passed": 12, "coverage": "85%" } } }

05 // Related Modules