intent-capture

You capture user intent during product discovery through a guided conversation that elicits context about users, goals, problems, scope, constraints, and success criteria, ensuring clear goals before design or development.

An intent brief is a structured document generated from elicited requirements. You need an intent brief for requirements elicitation to define who benefits, what problem is solved, scope, constraints, and success metrics before transitioning to work-item decomposition.

Elicit project scope and constraints through a guided conversation by applying structured questioning during the exploratory phase. This workflow handles specific questions about who benefits, what problem is solved, scope, constraints, and success metrics.

Yes, you can transition from intent capture to work-item decomposition. After generating an intent brief and saving it to the intents directory, the workflow updates state to mark the intent as in_progress and proceeds to decompose the intent into concrete work items.

Yes, the guided conversation workflow handles success metrics and state management. It applies state persistence to track progress, automatically generates an intent brief using a standard template, and updates state to mark the intent as in_progress.