vision

Create or update the root VISION.md to define project intent and philosophy.

13|3|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/misty-step/harness-kit --skill vision-misty-step
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vision
Source: https://github.com/misty-step/harness-kit/tree/main/skills/vision
Command: npx skills add https://github.com/misty-step/harness-kit --skill vision-misty-step

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Root VISION.md acts as the canonical north star for the project, ensuring consistent direction for maintainers, agents, and contributors by articulating intent, philosophy, audience, standards, and scope.

Core Features & Use Cases

  • Create or update the root VISION.md with the project's goals, philosophy, audience, and guiding standards.
  • Serve as a decision-making anchor during onboarding, planning, and major changes to keep work aligned with the north star.
  • Wire governance and automation prompts to reference VISION.md so tools and agents act with a shared understanding.

Quick Start

Update the root VISION.md to capture the current project direction and maintain alignment with AGENTS.md and vision-quality references.

Frequently Asked Questions about vision

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

FAQPage Schema
What is a project vision document and when do I need to create one?

A project vision document defines the north star for your repo by articulating intent, philosophy, audience, and scope. You need one for new repos, major refactors, or onboarding contexts to ensure maintainers, agents, and contributors share a consistent direction.

How do I write a VISION.md file to align my repo's project direction?

To write a VISION.md file, create the document at your repo root to capture goals, philosophy, audience, and guiding standards. You must consult your existing AGENTS.md and reference vision-quality guidance to ensure consistency across the project.

Can I use a vision document to align AI agents with my project direction?

Yes, you can use a vision document to align AI agents by writing a root VISION.md that wires governance and automation prompts to reference it. This ensures tools and agents act with a shared understanding of your project's intent and standards.

What's the best way to update an existing VISION.md during a major refactor?

The best way to update an existing VISION.md during a major refactor is to revise the root file while consulting your current AGENTS.md. Apply the vision-quality reference guidance to ensure the updated intent, philosophy, and scope still anchor decision-making.

Do I need an AGENTS.md file before defining my project's north star?

You do not need an AGENTS.md file to start defining your north star, but the Skill must consult any existing AGENTS.md present. Consulting AGENTS.md ensures the VISION.md you create maintains alignment with established agent instructions and standards.