Requirements Map

Create a decision-support map for scope review before implementation. Do not inspect Git diffs, collect implementation evidence, persist approval, or modify the target repository.

Workflow

1. Read the supplied requirements in any format.
2. Normalize every requirement into the manifest below. Preserve source wording in fullText; do not invent behavior.
3. Ask for clarification when uncertainty changes scope. Otherwise record uncertainty in assumptions or openQuestions and choose the matching non-ready status.
4. Add hierarchy edges. Add cross-links only when explicit or high-confidence; set inferred: true for inferred links.
5. Save the manifest outside the target repository.
6. Run node scripts/render-requirements-map.mjs manifest.json.
7. Return the two absolute paths printed by the renderer. Do not open a browser.

The report uses the Tailwind v4 Play CDN and therefore needs internet access to compile its embedded Tailwind source in the browser. The remote script can read report content, so do not use this skill for confidential requirements. tailwind.css is also emitted as an editable copy of that exact source.

Semantic Model

Use goal → scenario → given → when → then. Represent an And clause as its inherited clause type: an And after Given is given, after When is when, and after Then is then. Keep the original And wording in fullText.