Documentation
README
Flow interview
Conduct an extremely thorough interview about a task/spec and write refined details back.
.flow/ is the only task tracker. A run that recorded task state in a markdown TODO, a plan file, TodoWrite, or any other tracker has broken this β all task state is read and written via flowctl.
Chart boundary (fn-135)
Existing-spec clarification stays primary. Interview refines a valid spec with unresolved judgment questions. Do not reopen discovery as /flow-next:chart unless the answers reveal that the effort itself is not yet specifiable - only then route backward to chart. Clear work that never needed a chart stays out of chart. Unsure of the hop: /flow-next:guide.
Preamble
This is the opening of the README. Read the full README on GitHub.