vision-document

What problem does it solve?

Vision documents guide teams to define the problem, solution, user needs, scope, and future plans before design and coding, reducing misalignment and wasted effort. This skill guides a lean discovery process to produce focused, actionable vision artifacts.

Core Features & Use Cases

• 5-phase discovery: Problem Discovery, Solution Exploration, User Needs Analysis, Future & Scope, and Document Generation.
• Lean document size: typically 100-150 lines, focusing on WHAT and WHY rather than implementation.
• Generates supporting artifacts (vision.md, future.md, and references) to preserve context.

Quick Start

Tell me to create a vision document for a feature (e.g., "Payments feature"), and I’ll start Phase 1: Problem Discovery and build the document.

IMPORTANT: Start by creating a TODO list to track the 5 phases of vision document creation. Mark the first phase as "in_progress" and others as "pending".