gsd-cc-vision

Create a persistent VISION.md file in .gsd with user-defined goals and constraints.

3|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/0ui-labs/GSD-CC --skill gsd-cc-vision
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-cc-vision
Source: https://github.com/0ui-labs/GSD-CC/tree/main/gsd-cc/skills/vision
Command: npx skills add https://github.com/0ui-labs/GSD-CC --skill gsd-cc-vision

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Solves the problem of lost project intent by creating a persistent VISION.md.

Core Features & Use Cases

  • Vision capture: Collects the user's detailed goals, constraints, and success criteria into a single document.
  • Language alignment: Ensures output uses the user's language and references CLAUDE.md cues to stay consistent.
  • Auto-mode guardrails: Provides a north-star reference to check alignment during planning and execution.

Quick Start

Create or update the .gsd/VISION.md by describing your project and preferences in your own words.

Frequently Asked Questions about gsd-cc-vision

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

FAQPage Schema
How do I capture and persist project intent before planning tasks?

To capture project intent, you describe your project goals and preferences in your own words to generate a persistent VISION.md document in the .gsd directory, serving as a north-star reference.

What is a vision document used for in auto-mode project execution?

A vision document provides auto-mode guardrails by acting as a north-star reference to check alignment during planning and execution, ensuring automated tasks never lose the original project intent.

How do I ensure my project documentation is written in my preferred language?

You ensure documentation matches your language by providing your goals in your own words; the output references CLAUDE.md cues to guarantee the generated vision document stays consistent with your preferred language.

Can I use a persistent vision file to prevent automated planning from drifting off track?

Yes, creating a persistent vision file prevents automated planning drift by locking in detailed goals and success criteria, which the system checks against to maintain alignment across all tasks.

Will the system auto-modify my vision document without my permission?

No, the system never auto-modifies the vision document without your updates; the file is never automatically changed by the system without user updates, ensuring your defined constraints remain persistent.