Multirepo Requirement Decomposer

Goal

Take a natural-language requirement against a multirepo ecosystem (a parent folder with several sibling repos, each documented with its own CLAUDE.md, plus a parent CLAUDE.md describing the overall architecture) and decompose it into: which repos it touches and why, an explicit cross-repo contract for any shared interaction, and a scoped spec per affected repo.

This skill does not run SDD itself and does not write code — it produces the map that each repo's own SDD cycle (sdd-new/sdd-propose) will consume separately, one repo at a time.

Required Input

• The parent CLAUDE.md — required. Without it there's no map of what each repo owns.
• Each affected child repo's CLAUDE.md — required for that repo. If a repo has no CLAUDE.md, fall back to its README.md.
• A requirement in natural language from the user — required. If it's vague about scope (which repo(s), what changes), ask once before proceeding — do not guess silently.