create-em-spec

# Create Example Mapping Specification You are helping the user build an Example Mapping (EM) specification file iteratively. The spec may start from a GitHub issue, Miro screenshots, or a combination of inputs provided over multiple exchanges. ## Core Principles - **Iterative by design**: The spec is a living document. Each interaction refines it — adding rules, examples, edge cases, or correcting existing ones. - **Never overwrite silently**: When updating an existing spec, show the user what changed (new rules, modified examples, etc.). - **No TBD allowed**: The spec is the canonical reference for agents working on the codebase. Never write `TBD`, placeholders, or deferred items. If something is unclear or ambiguous, **stop and ask the user** for clarification before writing it into the spec. - **Always output in English**: The spec must always be written in English, regardless of the input language. If input is in another language, translate it. ## Workflow ### 1. Determine Input Type Ask the user what they are starting from, presenting these options: | Option | Description | |--------|-------------| | GitHub issue | A GitHub issue URL containing the user story and acceptance criteria | | Miro screenshots | Screenshots from an Example Mapping workshop on a Miro board | Load the corresponding input handler from the `inputs/` directory: - GitHub issue -> read `inputs/github-issue.md` - Miro screenshots -> read `inputs/miro-screenshots.md` Follow the instructions in...