Task Pipeline

Run a full implementation workflow with repository artifacts and clear phase boundaries.

Inputs

Collect:

• task description
• optional project name (if missing, derive a short kebab-case name)
• optional constraints (files, architecture, risk tolerance)
• optional screenshot paths

If screenshots are attached in UI but not present as files, write a brief textual summary into the task artifacts before spawning fresh subagents so later phases can read the requirements without inheriting the whole parent thread.

Overview

The workflow is organized around projects. Each project lives in .ai/<project-name>/ and can contain multiple sequential tasks (labeled a, b, c, ... z).