vision

Codify project vision into a structured VISION.md document with frontmatter and defined sections.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/rodacato/kwik-e-dev --skill vision-rodacato
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vision
Source: https://github.com/rodacato/kwik-e-dev/tree/main/plugins/launchpad/skills/vision
Command: npx skills add https://github.com/rodacato/kwik-e-dev --skill vision-rodacato

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams codify and maintain a project’s compass, ensuring decisions stay aligned with a shared vision and reducing scope drift during development.

Core Features & Use Cases

  • Central Vision document: captures the problem, philosophy, audience, success criteria, and what this is not to guide every decision.
  • Alignment moments: used during project initiation, conflict resolution, or onboarding to converge on priorities.
  • Facilitates future work: serves as the foundation for ROADMAP.md, ARCHITECTURE.md, or identity and governance workflows.

Quick Start

Create or update docs/VISION.md to establish a shared project compass and guide future decisions.

Frequently Asked Questions about vision

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

FAQPage Schema
How do I create a project vision document to prevent scope drift?

To prevent scope drift, create a project vision document that codifies the problem, philosophy, audience, and success criteria. This shared compass ensures development decisions stay aligned with governance priorities and reduces conflicting features.

What sections should be included in project governance documentation for alignment?

Project governance documentation for alignment should include sections for the core problem, philosophy, target audience, success criteria, what the project is not, and a litmus test, alongside frontmatter metadata for version and description.

When should I establish a project compass for my development team?

You should establish a project compass during new project initiation, when onboarding members, or when resolving conflicting features and unclear direction. It converges team priorities and anchors future architectural decisions.

How do I resolve conflicting features during project management?

To resolve conflicting features during project management, apply a litmus test against a central vision document. By checking disputed features versus codified success criteria and philosophy, teams can converge on aligned priorities.

What is the best way to document project philosophy and success criteria?

The best way to document project philosophy and success criteria is by maintaining a dedicated VISION.md file. This central document captures governance rules and audience definitions to guide every development decision.

What foundational documents are needed before creating a project roadmap?

Before creating a project roadmap, you need a foundational vision document defining the project compass. This establishes the shared philosophy and success criteria required to guide subsequent roadmap and architecture planning.