vision

Create, revise, or mirror project vision in vision.md and README front-matter.

3|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/xiongxianfei/rigorloop --skill vision-xiongxianfei
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vision
Source: https://github.com/xiongxianfei/rigorloop/tree/main/.codex/skills/vision
Command: npx skills add https://github.com/xiongxianfei/rigorloop --skill vision-xiongxianfei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aligning a project's direction across proposals, specs, and governance is often inconsistent and hard to audit over time. This skill centralizes vision work, ensuring a single canonical narrative and a consistent README front-matter that reflects current intent.

Core Features & Use Cases

  • Create the initial project vision at genesis by translating the strategic intent into a concise document.
  • Revise or mirror the vision when scope shifts, proposals evolve, or governance requires alignment, propagating updates to vision.md and README front-matter.
  • Validate artifacts against the vision to gate changes, ensuring consistency between proposals, specs, and delivery.

Quick Start

Create or revise the project vision from canonical sources and refresh the README front-matter.

Frequently Asked Questions about vision

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

FAQPage Schema
How do I define and align a project vision at genesis?

To define a project vision at genesis, translate your strategic intent into a concise canonical document. This process creates a vision.md file and updates the README front-matter to establish a single, auditable narrative for governance.

What is the best way to maintain project vision consistency across evolving proposals?

Maintaining project vision consistency requires validating artifacts against the canonical vision to gate changes. By mirroring or revising the vision when scope shifts, you ensure proposals and specs align with the current intent.

How does mirroring a project vision propagate updates to the README front-matter?

Mirroring a project vision propagates updates by using vision.md as the canonical source. It automatically synchronizes the current narrative and enforces name and description requirements directly into the README front-matter.

Can I use a canonical vision document to gate proposals and scope changes?

Yes, you can use a canonical vision document to gate proposals and scope changes. Validating artifacts against the vision ensures strict consistency between proposals, specs, and actual delivery before any changes are accepted.

When do I need to revise a project vision versus creating a new one?

Revise a project vision when scope shifts, proposals evolve, or governance requires alignment, updating the existing canonical source. Create a new vision only at project genesis to articulate the initial strategic intent.

What are the limitations of using vision.md as the sole canonical source for governance?

Using vision.md as the canonical source requires strict front-matter enforcement for name and description fields. Limitations arise if artifacts are not continuously validated against it, risking inconsistency between proposals and delivery.