skills.rest
YougLin-dev
YougLin-devCOMMUNITY
Explore all skills by this author →
GitHub

vision

Analyzes project.vision.md to generate a standardized project.vision-analysis.md with MVP features and technical implications.

182|33|Updated Feb 1, 2026
Search Tags:#planning#architecture#requirements#validation#analysis#vision#project-management
One-click install
npx skills add https://github.com/YougLin-dev/Aha-Loop --skill vision-youglin-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vision
Source: https://github.com/YougLin-dev/Aha-Loop/tree/main/.agents/skills/vision
Command: npx skills add https://github.com/YougLin-dev/Aha-Loop --skill vision-youglin-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Vision Skill helps teams validate and structure a project vision, turning a high-level idea into a concrete, testable plan for architecture and planning.

Core Features & Use Cases

  • Vision Validation: Ensure the vision document contains required sections (What, Why, Target Users, Success Criteria) and is sufficiently detailed.
  • Project Type & Scope Inference: Classify the project as CLI Tool, Web App, API Service, Library, etc., and estimate scale.
  • Output Vision Analysis: Produce a structured analysis (Must-have MVP features, technical implications, deployment needs) for downstream skills like Architects.
  • Use Case Example: Given a vision for a new data dashboard, extract core features and constraints to guide architecture choices.

Quick Start

  • Run vision analysis on project.vision.md to generate project.vision-analysis.md

Frequently Asked Questions about vision

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

FAQPage Schema
How do I validate project vision requirements before starting architecture planning?▼

Project vision validation requires structuring your project.vision.md across What, Why, Target Users, and Success Criteria sections to ensure the idea is testable and sufficiently detailed for architecture planning.

What is the best way to analyze a project vision document for MVP features and technical implications?▼

Analyzing a project vision document involves parsing the defined sections to infer project type and scope, outputting a standardized vision analysis that details MVP must-have features, technical implications, and deployment constraints.

Can I infer project scope and type from an initial idea for a data dashboard?▼

Yes, you can infer project scope and type by classifying the project as a CLI Tool, Web App, API Service, or Library based on the vision document, which then guides the extraction of core features and constraints for the data dashboard.

How do I generate a structured vision analysis for downstream architecture decisions?▼

To generate a structured vision analysis, run the vision analysis process on your project.vision.md to produce a project.vision-analysis.md file containing deployment needs, constraints, and open questions for downstream architects.

Does project vision analysis work without defining success criteria and target users?▼

Project vision analysis does not work optimally without defining success criteria and target users, as it validates these required sections to ensure the project vision is sufficiently detailed to guide architecture choices.

Related Skills

Explore More Product & Management Skills→
CassiiopeiaCassiiopeia
7

pro-plan

Extract project objectives, constraints, and success criteria into a strategic plan document.

Community
Advanced
Gentleman-ProgrammingGentleman-Programming
1.3k

sdd-design

Generate formal design documents from proposals and specifications.

Official
Advanced
Andy-HNUAndy-HNU

scoping-cutting

Frame a fixed time budget and identify must-have features for MVP scope.

Community
Intermediate
ZateZate
9

project-context

Detect project technology stack and write .devloop/context.json.

Community
Advanced