- Read
gitvow why <file>for the files those sessions touched before writing code. - If a previous session tried the same approach and a person changed it afterwards, take that as feedback on the approach.
- If nothing is recorded, say so and proceed; do not invent history.
gitvow-skills
Has this been worked on before?
Each hit is a session with its date, commit count and the plan it stated. (ledger only) marks a session that ended without committing; its work may survive in snapshots
Run with the concrete words of the task, not generic ones:
How to use the answer: