What problem does it solve? When a project owner asks "what is the status" or "what are you doing now", ad-hoc prose answers drift between sessions, omit tasks, and state unverified claims. This rule defines a fixed reply shape so every status answer is consistent, complete, and backed by freshly run commands. ## Core Features & Use Cases - Fixed reply structure: A short paragraph describing the epic (why it exists, how many tasks, which one runs now), followed by a table listing every epic task in plan order plus tasks created outside the epic. - Command-backed state cells: Every cell about the repository state must cite a number from a command run in the same turn — run numbers, PR numbers, scenario counts — never the bare word "done". - Guard hooks: Companion hooks (claim-guard.sh, git-guard-draft-ready.sh) refuse turn endings where tree claims lack a backing command or a draft PR is left silent. - Use Case: The owner asks "where does the work stand?" mid-epic; the agent runs npm run epic:table, checks the branch tip and latest run, and replies with the epic paragraph, the full task table, and at most two closing lines about what is awaited. ## Quick Start Ask the agent "what is the status of the current epic" and it will assemble the command-backed task table reply defined by this rule.
