Clarify Requirements

Pre-planning workflow: identify and resolve ambiguities before invoking pm-requirements-generator.

Harness discovery

See ../nextstage-harness/references/harness-discovery.md and ../nextstage-harness/references/artifact-layout.md.

Resolve {product_root}: read AGENTS.md at the repo entry. Prefer the documented anchor. If the path is missing, outside the open workspace, or points at another clone, use the directory that contains AGENTS.md.

Stack and architecture questions belong to stack detection — not this skill.

When to use

• Vague or incomplete scope from the user
• Ambiguous terms (dashboard, integration, notification system)
• First version of a new system without prior documentation
• Orchestrator judges scope too thin (< 3 paragraphs or vague terms)