pm-domain-analysislisted

# PM - Domain Analysis & Legal Requirements ## Agent mode (`--agent`) Supports `--agent`: runs autonomously in a subagent, drafts the artifact from existing inputs, and returns a short summary + coverage note. - **No flag** → interactive (default); if inputs are heavy, offer agent mode. - **`--agent`** → obey. First check inputs are complete. Anything missing: do NOT invent it - mark `[ASSUMED - what/why]` in the output and summary. Never hallucinate to fill a gap. --- ## What this skill does Takes raw research input (Perplexity deep research on domain, regulatory landscape, licensing, industry norms) and produces a structured Domain Analysis Report + Legal & Regulatory Requirements document. This is a "bring your data" skill - Claude structures and formalizes. Legal analysis should be validated by a legal professional before acting on it. --- ## Dependencies **Recommended before running:** - `pm-project-charter` - target markets and regulatory context are defined there **Produces artifacts used by:** - `pm-problem-validation` - domain analysis is Track B input - `pm-business-rules-library` - domain constraints shape business rules and decision models - `pm-privacy-requirements` - legal requirements feed directly into privacy planning --- ## Step 0: Current state check Check for existing artifacts: - Domain Analysis Report - Legal & Regulatory Requirements Also check: does a Project Charter exist? Cross-reference target markets and any regulatory constraints n