37 lines
1.2 KiB
Markdown
37 lines
1.2 KiB
Markdown
|
{{ conventions }}
|
||
|
|
|
||
|
|
## Task
|
||
|
|
|
||
|
|
Advance this repository: find what is open, implement what is ready, then commit
|
||
|
|
and sync.
|
||
|
|
|
||
|
|
### 1. Find the open work
|
||
|
|
|
||
|
|
Two sources, and check both: uncommitted changes in the working tree, and open
|
||
|
|
tasks in the workplan files. They often disagree — half-finished work in the
|
||
|
|
tree that no task mentions, or a task marked `progress` with nothing to show.
|
||
|
|
Report the disagreement; it is usually informative.
|
||
|
|
|
||
|
|
### 2. Decide what is actually ready
|
||
|
|
|
||
|
|
Not everything open is ready. A task is ready when its premises still hold and
|
||
|
|
nothing it depends on is unresolved. A task that needs a decision from me is not
|
||
|
|
ready — surface it instead of guessing.
|
||
|
|
|
||
|
|
Say what you chose to work on and what you deliberately left.
|
||
|
|
|
||
|
|
### 3. Implement
|
||
|
|
|
||
|
|
Implement the ready work. Verify each piece before calling it done: run the
|
||
|
|
tests, exercise the path, show the output. If something fails, report the
|
||
|
|
failure rather than working around it silently.
|
||
|
|
|
||
|
|
Update task statuses in the workplan files as you go, not in a batch at the end.
|
||
|
|
|
||
|
|
{{ commit_and_sync }}
|
||
|
|
|
||
|
|
### 5. Report
|
||
|
|
|
||
|
|
What was implemented and verified, what was left and why, and anything that
|
||
|
|
needs a decision before the next session.
|