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 in .ai/<project-name>/about.md so child runs can consume the requirements.

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).