auth-yes/tasks/path.md

41 lines
2.2 KiB
Markdown

# 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`](./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`](./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`](./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`](./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`](./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`](./GUIDELINES.md).