vision

Draft and maintain a VISION.md file at the repository root.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/kennykankush/skillpack --skill vision-kennykankush
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vision
Source: https://github.com/kennykankush/skillpack/tree/main/plugins/workbench/skills/vision
Command: npx skills add https://github.com/kennykankush/skillpack --skill vision-kennykankush

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keep a project's vision written down and alive at the repository root to provide a stable north star that informs decisions, aligns stakeholders, and prevents drift between intent and implementation.

Core Features & Use Cases

  • Birth — carry the distilled intent from exploration into a new repo by creating a committed VISION.md at the root.
  • Backfill — for an existing project with no vision, read the building, interview the visionary, draft from evidence, and write or update VISION.md with open questions captured.
  • Refresh — when direction shifts, surface deltas, append updates with dates, and preserve the spark for traceability.

Quick Start

Create or update VISION.md at the repo root, dating the spark and recording the current intent for future reference.

Frequently Asked Questions about vision

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

FAQPage Schema
How do I document a project vision at the repository root to align stakeholders?

Document a project vision by drafting a VISION.md file at the repository root to codify core intent. This provides a stable north star informing decisions and aligning stakeholders to prevent drift between intent and implementation.

What is the best way to backfill a vision document for an existing project?

Backfill a vision document by reading the existing codebase, interviewing the visionary, and drafting from evidence. This updates VISION.md with captured open questions to preserve intent for projects lacking a formal vision.

How do I refresh project vision documentation without losing the original intent?

Refresh project vision documentation by surfacing direction deltas and appending updates with dates to VISION.md. This preserves the verbatim spark through append-only history, maintaining traceability of the original intent.

When do I need to create a VISION.md file for my repository?

Create a VISION.md file during project birth to carry distilled intent into a new repo, during backfill for existing projects lacking vision, and during refresh moments when direction shifts to ensure alignment.

Does project vision documentation require a user-voice validation process?

Project vision documentation requires a user-voice validation process with Open Questions to preserve intent. This ensures the VISION.md accurately reflects stakeholder needs and surfaces unresolved alignment issues.

Why does my project drift from its original roadmap and how can I prevent it?

Projects drift without a stable north star codified at the repository root. Maintaining an append-only VISION.md with verbatim spark and open questions prevents drift between intent and current development.