specflow-planlisted

# Specflow: Plan ## When to use Turn an agreed spec into a durable, executable plan — bite-sized tasks with exact paths, the acceptance criterion each satisfies, and the command that verifies it, written to a file a fresh agent could execute without ever seeing the conversation. The middle of the spec-first spine (brainstorm → plan → develop); it holds the planning half that used to live inside specflow-develop: explore, gap analysis, research, implementation plan, and the size check. Use when the user says "plan this", "how would we build this spec", "break this down", "what are the steps", or when a spec is agreed and implementation is next. Writes no code. ## The Iron Law NO PLAN THAT A FRESH AGENT COULD NOT EXECUTE BLIND Violating the letter of this law is violating the spirit. If you find yourself constructing a reading under which this plan is clear enough as it stands, that construction is the violation. The test is literal: an agent with no memory of the conversation that produced this plan, given only the plan and the repository, must be able to execute every task without asking you a question. That is what makes it an artefact instead of a summary. Hardening mechanisms per `skills/_conventions/hardening.md`. ## What this produces A plan file — the project's plan directory if one exists, else `plans/<YYYY-MM-DD>-<slug>.md` created at the project root. It is durable and reviewable: a plan that lives only in a transcript dies with the session, which is the fai