elicit

Eliciting stakeholder requirements involves guiding process discovery to capture actors, entities, and transitions, then distilling intent into structured rules and surfaces. This transforms vague ideas into concrete lifecycle specifications with verifiable assumptions.

Defining scope and edge cases from existing discussions requires distilling stakeholder mental models through assumption checking. You extract happy paths and validation rules to ensure data dependencies and actor roles align with the intended lifecycle.

Process discovery captures rules and surfaces for new systems by detailing data dependencies and fields. Starting from a high-level description, you construct the happy path and fill in lifecycle details to flesh out the full specification.

Stakeholder intent distillation works by reviewing and validating collected rules and surfaces against original assumptions. This refinement process ensures the final specification accurately reflects stakeholder mental models and verifiable lifecycle behaviors.

Assumption checking is needed during specification elicitation to validate that rules, fields, and actor roles align with stakeholder mental models. It supports review and refinement to ensure the captured lifecycle details remain verifiable.

The elicit skill supports documenting open questions during process discovery. It captures actors, entities, transitions, and unresolved queries to ensure all stakeholder intent is tracked and addressed within the final specification.