write-technical-brieflisted

# Technical Brief Writer ## When to Use Use this skill when a feature has been specced and needs to be handed to engineering in a form they can act on. It adds the most value when: - **After an FR is written and ACs are verified** — the feature request describes the problem and the expected outcomes; the technical brief translates that into what engineering needs to start work without ambiguity - **Before handing to engineering** — prevents the classic "this spec has gaps" discovery mid-sprint by surfacing open questions while there is still time to resolve them with the PM - **When starting a sprint and realising the spec has gaps** — if engineering finds unanswered questions during sprint planning, use this skill to structure those gaps and route them back to the PM quickly - **After a feature request authoring session** — run this skill at the end of a `write-feature-request` session to produce both the FR and the engineering handoff in a single workflow - **When an existing spec needs a structured review** — use this skill to audit a spec written without a template and surface what is missing before engineering reads it ## Input Format The skill works best with a Feature Request markdown document produced by the `write-feature-request` skill, but accepts any structured or unstructured spec. Provide one of the following: **A Feature Request markdown file (preferred):** ``` Path: ./feature-requests/FR-0042-export-filters.md ``` **A pasted FR description:** ``` Featur