52 lines
977 B
Markdown
52 lines
977 B
Markdown
# loop-build Task Template
|
|
|
|
Use this file to record each task and planned execution notes.
|
|
|
|
- Task file format: one block per task, one per line or section.
|
|
- Keep task scope tight; avoid changing unrelated files.
|
|
|
|
## Required fields
|
|
|
|
- `goal`
|
|
- `constraints`
|
|
- `plan_source`
|
|
- `planner.md` output source / timestamp
|
|
- `status`
|
|
- `current_task_file`
|
|
|
|
## Current Task Header
|
|
|
|
```text
|
|
Task ID:
|
|
Goal:
|
|
Owner:
|
|
Status:
|
|
Created:
|
|
Updated:
|
|
Constraints:
|
|
Repo context hint:
|
|
Verify policy:
|
|
```
|
|
|
|
## Running Notes
|
|
|
|
- `PLAN` generated from `prompts/planner.md` (3~7 steps)
|
|
- approvals: `APPROVE_PLAN -> step loop -> APPROVE_NEXT`
|
|
- verify targets per step
|
|
- rollback notes per step
|
|
- decision points / open questions
|
|
|
|
## Log (manual)
|
|
|
|
- Step 1: result + summary
|
|
- Step 2: result + summary
|
|
- Step n: result + summary
|
|
|
|
## Completion Check
|
|
|
|
- expected acceptance criteria met:
|
|
- diff size policy followed (<=2 files/step):
|
|
- `current_task.json` synchronized:
|
|
- history.ndjson rows appended:
|
|
|