intent-guidance

Name: intent-guidance
Availability: InStock
Author: Driver

Capture feature development intent and generate a research reference document.

3|2|Updated Apr 13, 2026

Search Tags:#feature development #developer guidance #developer communication #software lifecycle #intent capture

Ready to run

npx skills add https://github.com/driver-ai/driver-sdlc-plugin --skill intent-guidance

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: intent-guidance
Source: https://github.com/driver-ai/driver-sdlc-plugin/tree/main/skills/intent-guidance
Command: npx skills add https://github.com/driver-ai/driver-sdlc-plugin --skill intent-guidance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures clear understanding of the author's intent at the start of a feature development, facilitating better documentation and structured feature development.

Core Features & Use Cases

Intent Capture: Guides a conversation with the author to capture their intent, context, and definition of done.
Document Creation: Generates a research/00-intent.md file that serves as the canonical reference for downstream phases.
Transition Facilitation: Smoothly transitions the conversation from intent to research when appropriate.

Quick Start

Capture the intent for your feature using the /drvr:capture_intent command.

Frequently Asked Questions about intent-guidance

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

FAQPage Schema

How do I capture feature development intent before starting coding?▼

You capture feature development intent by guiding a conversation with the author to extract their context and definition of done, which generates a canonical markdown reference document for downstream phases.

What is the best way to document author intent for software lifecycle phases?▼

Documenting author intent for the software lifecycle is best achieved by generating a structured markdown reference file at the feature start, ensuring downstream development phases have a clear canonical understanding of requirements.

How do I create a definition of done reference for downstream development?▼

To create a definition of done reference, capture the author's specific requirements and context at feature initiation, outputting a structured markdown file that explicitly guides the downstream development phases.

When do I need to use intent capture for feature development?▼

Intent capture for feature development is needed at the very start of the process, ensuring that the author's thoughts and requirements are clearly understood and documented before transitioning into downstream research.

Does intent capture work without integrating external dependencies?▼

Yes, intent capture works without external dependencies, relying solely on internal scripts to facilitate the conversation, extract the feature requirements, and generate the markdown reference document.