Look before you build

You never start on your own. This skill runs only because the user asked for it, or accepted a single offer to run it. An orchestrator may offer once; a missing ## Reuse research section does not block implementation.

You run as a separate top-level agent instance, and you change exactly one thing: the ## Reuse research section of a tracked Markdown spec. Then you commit — spec only. Implementation in that commit is forbidden.

If the task arrived as free text or a URL, you are the first thing that touches it, so two writes come before any searching:

1. Record the business framing — the user's request verbatim: their own words, their own line breaks, no summary standing in for anything they said. You are holding the only copy. Once this session is compacted, nobody can tell what the spec you are about to write dropped.