Create 100-150 line vision documents through a five-phase discovery process.
npx skills add https://github.com/steveclarke/dotfiles --skill vision-document
Please help me install this Agent Skill. Skill: vision-document Source: https://github.com/steveclarke/dotfiles/tree/main/ai/skills/vision-document Command: npx skills add https://github.com/steveclarke/dotfiles --skill vision-document
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.
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".
High-intent search queries and answers about installing and using this skill.
Create a vision document by following a five-phase discovery process: Problem Discovery, Solution Exploration, User Needs Analysis, Future & Scope, and Document Generation. Start with a TODO list marking Phase 1 in_progress, then work through each phase to produce a lean 100–150 line vision.md artifact that captures problem, solution, user needs, and scope before design and coding.
A lean vision document includes vision statement, table of contents, problem statement, solution overview, user needs analysis, future possibilities, and scope boundaries. The artifact stays focused on WHAT and WHY rather than implementation details, typically spanning 100–150 lines to guide discovery phases without heavy overhead.
Write a vision document when starting a feature project or defining strategic context and high-level goals before technical decisions. Vision documents resolve misalignment and wasted effort by establishing shared understanding of the problem, solution, and user needs across teams before design and coding begin.
The process outputs three artifacts: vision.md containing the core vision statement and strategic framework, future.md documenting future possibilities and scope boundaries, and vision-discussion-summary.md preserving context from the discovery phases for team alignment.
Vision documents work both at project initiation and when you need to define or redefine strategic context for existing feature work. Use them whenever teams lack shared understanding of why a feature exists, what problems it solves, or what user needs drive it—not just at launch.
cvillamarp-lgtmArticulate user problems with explicit type, scope, and validation criteria.
LeandroBenjaminLConvert technical specifications into structured implementation plans and architecture documentation.
apolosanDraft the System Vision Document using the vision template and save it as docs/up/01-vision.md.
abhishek2chikunDesign structured consulting workshop agendas with activities, timings, and outputs.
