Tasks-Template
Section titled “Tasks-Template”SSoT template for task files. Copy this to create a new task:
Task-Name.md(no date prefix)Usage: append Claude Response and Talbot Response sections to the END. Never delete history.
---title: [Task Name]date: YYYY-MM-DDmodel: default # light | default | high | highestmodel-type: auto # auto | free | localtask-type: # code | research | brainstorm | planning | writing | review | opsrisk: low # low | medium | high | criticalstatus: # (blank) | ready | active | blocked | completeprerequisites: none # none | TaskName | Phase2/TaskNameassignee: claude # claude | cursor | talbot | tbd---
# [Task Name]
**Date:** YYYY-MM-DD
## Background[optional — prior context, why this matters, related sessions]
## Tasks[what needs to be done]
---
## Claude Response — YYYY-MM-DD
### Summary- [x] Done item 1- [x] Done item 2
### Next Steps for Talbot- [ ] Decision or action needed 1.
## Talbot Response
---
## Claude Response — YYYY-MM-DD ← always append here
### Summary...
### Next Steps for Talbot- [ ] ... 1.
## Talbot Response
---Key rules:
- New sections always append to END — never delete prior history
- Claude always appends
## Talbot Response+---after its own section /task-continue [filename]— Claude processes latest Talbot Response, appends new Claude Response/task-complete [filename]— close task: LESSONS.md candidates, purge, log/delete, commit offer
Frontmatter params (all optional — omit any you don’t need):
| Param | Values | Default |
|---|---|---|
date | YYYY-MM-DD | creation date |
model | light / default / high / highest | default |
model-type | auto / free / local | auto |
task-type | code / research / brainstorm / planning / writing / review / ops | — |
risk | low / medium / high / critical | low |
status | (blank) / ready / active / blocked / complete | — |
prerequisites | none / TaskName / Phase2/TaskName | none |
assignee | claude / cursor / talbot / tbd | claude |
Status lifecycle: (blank) → ready (set by /task-prep) → active (set by /task-start) → blocked / complete