clarify

To elicit tacit requirements before drafting a formal specification, this Skill conducts a structured discovery dialogue to surface unstated user intents and early constraints, reducing ambiguity and misalignment. It outputs a structured summary for spec handoff.

The best way to capture trade-offs during requirements discovery is to run a guided dialogue that identifies technical and business constraints. This Skill generates a dedicated trade-off table and decisions summary to guide scope definition before spec drafting.

Prepare a structured handoff for formal spec drafting by running a guided discovery process that validates early constraints. This Skill produces a ready-to-transfer output containing user intents, a trade-off table, and decision summaries for direct spec integration.

You need to run requirements clarification in early specification workflows when you must uncover unstated business constraints before writing formal specs. It is applied across discovery, definition, and trade-off exploration to ensure user intents are fully articulated.

Yes, you can use this for early constraint validation before writing a spec. It identifies technical and business constraints through a structured dialogue, ensuring that scope is guided by validated user intents rather than assumptions during the discovery phase.

Tacit knowledge discovery is the process of surfing unstated user requirements through structured dialogue. It reduces ambiguity in specs by articulating hidden intents and constraints early, producing a clean set of validated requirements before formal drafting begins.