2.2 KiB
2.2 KiB
Task Orchestration Protocols (tasks/path.md)
This index maps out the standardized engineering workflow and action protocols
in the tasks/ directory.
🔄 The 4-Step Engineering Lifecycle
The standard task pipeline follows a strict, sequential 4-step lifecycle:
[1. plan] ──► [2. audit-1] ──► [3. do] ──► [4. audit-2]
| Step | Protocol File | Role | Purpose | Direct Command | Prompt Prep Command |
|---|---|---|---|---|---|
| 1 | tasks/plan.md |
System Analyst | Research codebase & draft task in tasks/new/ |
"tasks/plan XYZ" | "tasks/plan a prompt for Jules" |
| 2 | tasks/audit-1.md |
Plan Critic | Audit, grade, and refine task plan | "tasks/audit-1 task #1" | "tasks/audit-1 prompt for Jules" |
| 3 | tasks/do.md |
Developer | Execute task, run gates, move to complete/ |
"tasks/do task #1" | "tasks/do a prompt for Jules" |
| 4 | tasks/audit-2.md |
QA Auditor | Audit code quality & verify zero regressions | "tasks/audit-2 branch" | "tasks/audit-2 prompt for Jules" |
🔬 Standalone / On-Demand Protocol
Use this protocol out-of-band at any time to diagnose complex bugs or anomalies without modifying production code.
| Protocol File | Role | Purpose | Direct Command | Prompt Prep Command |
|---|---|---|---|---|
tasks/debug.md |
Investigator | Root-cause analysis & experiments in scratch/ |
"tasks/debug issue" | "tasks/debug a prompt for Jules" |
📋 Task File Formatting & Naming Rules
For exact task file naming conventions, sequence numbering, and
# TASK METADATA header requirements, refer to
tasks/GUIDELINES.md.