domain-to-speclisted

# Domain To Spec This is the first skill for a new project. It converts the user's domain knowledge into two repo-root files: - `AGENTS.md`: shared instructions for future coding agents - `PRD.md`: the product blueprint consumed by scaffold skills Do not scaffold application code in this skill. ## Preflight Check whether `AGENTS.md` or `PRD.md` already exist. If either exists, stop and ask whether to update specific sections, append new scope, or cancel. Never overwrite these files silently. ## Interview The Domain Expert Extract the sentence: ```text I am a {profession or role} building a tool to {outcome}. ``` Ask only for missing essentials: - Who will use the tool? - What is the painful or error-prone workflow today? - What rules, regulations, or professional constraints matter? - What information does the user provide? - What output should the tool produce? - Does the tool need accounts, stored data, file processing, paid APIs, email, or secrets? - What would make the MVP a success? Mirror the user's domain language back to them before translating it into software. ## Translate Domain Concepts Map domain ideas into software primitives: | Domain Concept | Software Equivalent | | --- | --- | | Form or checklist | Validated input form | | Decision tree | Wizard or conditional logic | | Reference document | Searchable knowledge base | | Approval process | Status workflow and roles | | Report or summary | Generated page, PDF, or export | | Compliance check | Rul