sdd-vision

Translate business problem descriptions into structured specs/vision.md documents.

3|Updated May 28, 2026

Search Tags:#governance #vision #project-planning #specs #stakeholders #business-problem

Ready to run

npx skills add https://github.com/mahg-es/araya --skill sdd-vision

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-vision
Source: https://github.com/mahg-es/araya/tree/main/skills/sdd-vision
Command: npx skills add https://github.com/mahg-es/araya --skill sdd-vision

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams turn vague business needs into a concrete, documentable project vision that guides strategy, scope, and delivery.

Core Features & Use Cases

Capture the business problem, objectives, constraints, and stakeholders in a single, shareable vision.
Produce a structured specs/vision.md with sections for Project Name, Description, Objectives, Success Metrics, Scope, Constraints, and Stakeholders.
Support early-stage product strategy and governance by aligning teams around a common vision.

Quick Start

Provide a business problem description to generate a structured vision in specs/vision.md.

Frequently Asked Questions about sdd-vision

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

FAQPage Schema

How do I turn a business problem description into a structured project vision?▼

To turn a business problem description into a project vision, provide the initiative details to generate a formal specs/vision.md document. This captures project name, objectives, scope, constraints, stakeholders, and success metrics to guide strategy and delivery.

What should a project vision document include for early-stage initiatives?▼

A project vision document for early-stage initiatives should include clear sections for project description, objectives, success metrics, scope, constraints, and stakeholders. This structure ensures teams align around a common governance strategy.

How do I align stakeholders and define scope for a new project strategy?▼

You align stakeholders and define scope by translating vague business needs into a formal project vision document. This structured approach captures stakeholder requirements, constraints, and success criteria to guide early-stage product strategy and governance.

Can I use a generated project vision to validate requirements and risks?▼

Yes, you can use a generated project vision to validate requirements and risks. The Skill enforces governance by defining a structured specs/vision.md, enabling teams to evaluate success metrics, constraints, and project scope against documented objectives.

Does generating a vision document require any specific technical dependencies?▼

Generating a vision document requires no specific technical dependencies. You simply provide a business problem description as input, and the Skill produces a structured markdown file documenting the project scope, stakeholders, and success criteria.

When do I need a formal project vision for product planning?▼

You need a formal project vision for product planning when working on early-stage initiatives across business units. It helps translate ambiguous business problems into a consumable document that guides strategy, defines scope, and enforces project governance.