specifying-and-implementinglisted

# Specifying and Implementing Two phases on the same artifact: **Spec** synthesizes the current conversation into `.sixth-sense/spec.md`; **Implementation** builds against it. ## Spec Synthesize the current conversation into a structured specification. Use the project's own domain vocabulary (reference `CONTEXT.md` if it exists). ### Where It Goes Write the finished spec to `.sixth-sense/spec.md` at the project root, overwriting any previous version there — this is the spec currently being implemented against, not a history of past ones. This gives the Implementation section's Heavy Workflow a file to reference by path in subagent dispatch prompts instead of re-pasting the full spec text into every one, and gives `dylan-dog`/`opus-review` a fixed artifact to read directly instead of a manually reconstructed summary. Still show the spec in the conversation as usual — the file is an additional artifact, not a replacement for discussing it with the user. ### Template #### Problem Statement [Describe the problem from the user's perspective, including why it is worth solving.] #### Solution [Outline the high-level shape of the fix, excluding low-level implementation details.] #### User Stories [Extensive, numbered list of concrete, independently checkable behaviors. Each story carries its own verification command — how the Implementation section/`verification-before-completion` will prove it's done — not just the top-level Testing Decisions section below.] 1. As a [actor]