50 lines
2.1 KiB
Markdown
50 lines
2.1 KiB
Markdown
# Task Implementation Execution Protocol (`tasks/do.md`)
|
|
|
|
This protocol defines the standard for executing an approved task from
|
|
`tasks/new/`.
|
|
|
|
---
|
|
|
|
## 1. Direct Execution Protocol (When You Are Doing the Task)
|
|
|
|
When commanded to **"tasks/do `[TASK_FILE]`"**:
|
|
|
|
1. **Move to WIP:** Move the task file from `tasks/new/` to `tasks/wip/` before
|
|
starting work.
|
|
2. **Follow the 4-Step State Machine:**
|
|
- **Step 1 (Research):** Inspect the target files and verify architectural
|
|
assumptions.
|
|
- **Step 2 (Implementation):** Apply minimal, pure functional modifications.
|
|
Preserve existing docstrings and comments.
|
|
- **Step 3 (Quality Gates):** Run all verification gates:
|
|
- `deno fmt`
|
|
- `deno task lint`
|
|
- `deno task check`
|
|
- `deno test --allow-all` (Run ONLY hermetic unit tests; NEVER run
|
|
`deno task start` in container sandboxes).
|
|
- **Step 4 (Review & Move):** Upon all gates passing, move the task file to
|
|
`tasks/complete/YYYY-MMDD.XX.agent.type.scope.title-HHMM.md`.
|
|
3. **Commit & Sync:** Commit with standard conventional commit syntax and push
|
|
to both remotes (`origin` and `gitea`).
|
|
|
|
---
|
|
|
|
## 2. Dispatch Template (When Preparing a Prompt for Jules or External Agents)
|
|
|
|
When commanded to **"tasks/do a prompt for Jules on `[TASK_FILE]`"**, fill in
|
|
and provide the following block:
|
|
|
|
```text
|
|
**Role:** Act as an Implementation Engineer.
|
|
|
|
**The Task:** Please review and execute the approved task plan in `[tasks/new/TASK_FILENAME.md]`.
|
|
|
|
**Directives:**
|
|
1. Follow the strict 4-step state machine (Research -> Implementation -> Quality Gates -> Review).
|
|
2. Move the task file from `tasks/new/` to `tasks/wip/` before starting, and to `tasks/complete/` upon verification.
|
|
3. Apply minimal, pure functional modifications adhering to `AGENTS.md`.
|
|
4. Run all quality gates: `deno fmt`, `deno task lint`, `deno task check`, and `deno test --allow-all`.
|
|
5. Run ONLY unit tests (`deno test --allow-all`). Do NOT run `deno task start` or `deno task dev` (database daemons are not running in container sandboxes).
|
|
6. Provide a concise summary of all modified files and verified test results upon completion.
|
|
```
|