53 lines
1.8 KiB
Markdown
53 lines
1.8 KiB
Markdown
|
{{ conventions }}
|
||
|
|
|
||
|
|
## Task
|
||
|
|
|
||
|
|
Find the gaps worth closing, plan them, and close them.
|
||
|
|
|
||
|
|
### 1. Rank the gaps honestly
|
||
|
|
|
||
|
|
Gather candidate gaps from the intent document, any scope assessment, open
|
||
|
|
questions, failing or missing tests, and defects you can demonstrate.
|
||
|
|
|
||
|
|
Rank by what closing each one unblocks — not by how easy it is. A gap that
|
||
|
|
blocks other work outranks three cosmetic ones. State the ranking criterion you
|
||
|
|
used, and name the gaps you considered and rejected, so the shortlist can be
|
||
|
|
argued with.
|
||
|
|
|
||
|
|
Where a gap is really a decision the operator must make, say so and ask rather
|
||
|
|
than deciding it inside an implementation task.
|
||
|
|
|
||
|
|
### 2. Write the workplan
|
||
|
|
|
||
|
|
One workplan file, one task per gap. Each task states the problem, what "done"
|
||
|
|
looks like, and — where the gap involves a design choice — the options with a
|
||
|
|
stated leaning rather than a silent decision.
|
||
|
|
|
||
|
|
Do not invent structure the work does not have. Three real tasks beat nine
|
||
|
|
padded ones.
|
||
|
|
|
||
|
|
### 3. Register it
|
||
|
|
|
||
|
|
Register through the sanctioned path: write the file, commit, and let the sync
|
||
|
|
assign ids and write them back. Never create the workplan or its tasks directly
|
||
|
|
against the hub.
|
||
|
|
|
||
|
|
### 4. Implement
|
||
|
|
|
||
|
|
Implement: **{{ implement }}**.
|
||
|
|
|
||
|
|
When implementing, work the tasks in order, updating each task's status in the
|
||
|
|
file as you go. After each task: verify it, commit it with reasoning, and sync.
|
||
|
|
Do not batch six tasks into one commit — the record is the point.
|
||
|
|
|
||
|
|
When a task turns out to be wrong once you are inside it, say so and revise the
|
||
|
|
plan rather than forcing the original shape.
|
||
|
|
|
||
|
|
When not implementing, stop after registering and report what the plan contains.
|
||
|
|
|
||
|
|
### 5. Close
|
||
|
|
|
||
|
|
Report which tasks are done, which are not and why, and what the work revealed
|
||
|
|
that the plan did not anticipate. Hand off leftovers as live work records. Log a
|
||
|
|
progress event.
|