requirement-to-spec — business document → spec + task breakdown

Turn a business requirement document into a spec and an ordered task breakdown, filed wherever the team tracks work. This is the first half of a two-skill pipeline:

/arkandia:requirement-to-spec <doc>          → the spec, plus subissues/work items ready to build
/arkandia:linear-plan-build <ISSUE> → one of those items, read it → PR open, CI green
/arkandia:ado-plan-build <id>       →   ...same, on Azure Boards

linear-plan-build/ado-plan-build never create subissues — by contract they only write status and comments on the ticket they are actively building. This skill is what fills the parent issue they consume. It is not "summarize this Word doc": a summary restates what is written; this skill also surfaces what the document does not say — the impact on a public contract nobody mentioned, the attachment that never arrived, the paragraph that quietly widens scope — and turns the resolved decisions into an ordered, buildable list.

Philosophy (hold these throughout)