skills.rest
4tikhonov
4tikhonovCOMMUNITY
Explore all skills by this author →
Website𝕏@4tykhonovGitHub

intent-capture

Guide exploratory conversations to capture goals, constraints, and success criteria.

3|1|Updated Jan 23, 2026
Search Tags:#stakeholders#clarifying-questions#intent-capture#guided-conversation#requirements-elicitation#product-planning
One-click install
npx skills add https://github.com/4tikhonov/the-minority-report --skill intent-capture
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: intent-capture
Source: https://github.com/4tikhonov/the-minority-report/tree/main/ontologies/.specsmd/fire/agents/planner/skills/intent-capture
Command: npx skills add https://github.com/4tikhonov/the-minority-report --skill intent-capture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, guided dialogue to capture user goals, constraints, and success criteria, preventing premature assumptions and scope creep.

Core Features & Use Cases

  • Exploratory dialogue: Guides users to articulate goals, stakeholders, problems, and success metrics.
  • Intent brief generation: Produces a clear, actionable brief and persists it in the project state for subsequent work items.
  • Iterative clarification: Re-prompts to resolve ambiguities and align stakeholders on a shared understanding.

Quick Start

To begin, start a session by describing the high-level goal. The assistant will ask clarifying questions, summarize the understanding, and generate an intent brief ready for handoff to planning and execution.

Frequently Asked Questions about intent-capture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture user intent during exploratory product planning?▼

Capture user intent by engaging in a guided conversation that elicits goals, stakeholders, and success criteria. This structured dialogue prevents premature assumptions and ensures you record exactly what to build, why, and for whom before downstream execution.

What is the best way to elicit requirements and prevent scope creep?▼

Elicit requirements through iterative clarification and guided questions that align stakeholders on a shared understanding. By surfacing constraints and success metrics early, you prevent scope creep and avoid building features based on unvalidated assumptions.

How do I start a guided conversation to define project goals and constraints?▼

Start a session by describing your high-level goal. The assistant will ask targeted clarifying questions, summarize the understanding, and generate an actionable intent brief ready for handoff to planning and execution.

Does requirements elicitation work for resolving ambiguities across multiple stakeholders?▼

Yes, requirements elicitation works for resolving ambiguities by re-prompting to align multiple stakeholders. It enforces clarifying questions to surface hidden constraints and ensures a shared understanding of the project's success metrics.

What format does the intent brief generate for downstream planning work?▼

The intent brief generates a clear, actionable summary that persists in the project state. This format records the confirmed what and why, ensuring downstream planning and execution work items have a validated reference point.

Related Skills

Explore More Product & Management Skills→
epieczkoepieczko

epic.write

Generate structured Agile Epic Markdown documents from initiative details.

Community
Intermediate
fabriqaaifabriqaai
201

work-item-decompose

Decompose intents into executable work items with acceptance criteria.

Official
Advanced
coco-researchcoco-research
264

prd-generator

Generate structured product requirements documents with user stories and success metrics.

Community
Advanced
phraphra

intent-capture

Capture user intent through guided conversations and generate intent briefs.

Community
Intermediate