autoloop-vision

Create and migrate project vision wikis with markdown pages and JSON validation.

Updated Jun 1, 2026
One-click install
npx skills add https://github.com/openloopagentics/autoloop --skill autoloop-vision
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autoloop-vision
Source: https://github.com/openloopagentics/autoloop/tree/main/plugins/autoloop/skills/autoloop-vision
Command: npx skills add https://github.com/openloopagentics/autoloop --skill autoloop-vision

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill simplifies the process of authoring and maintaining the vision of a software project, helping you articulate goals, scenarios, and scoring rubrics in a structured wiki format.

Core Features & Use Cases

  • Vision Wiki Authoring: Create a vision wiki with markdown pages for goals, scenarios, scoring rubrics, and optional test commands.
  • Legacy Support: Migrate from legacy vision.json files.
  • Validation: Local validation to ensure the wiki's structure and content are correct before syncing.

Quick Start

Run 'autoloop vision init' to create a new vision wiki in the current directory, or 'autoloop vision migrate' to convert a legacy vision.json file to a wiki.

Frequently Asked Questions about autoloop-vision

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

FAQPage Schema
How do I create structured project vision documentation for Agile software development?

You can create a vision wiki by running the 'autoloop vision init' command in your directory. This sets up structured markdown pages for goals, scenarios, and scoring rubrics for your software project.

Can I migrate a legacy vision.json file to a wiki format?

Yes, legacy vision.json files can be converted into a wiki format. Run the 'autoloop vision migrate' command to automatically transition your existing project configuration into structured markdown wiki pages.

Does this tool validate scenario planning and goals before syncing documentation?

Yes, the tool performs local validation to ensure the wiki's structure and content are correct before syncing. This requires markdown processing and JSON validation to verify your project goals and scenarios.

What is the best way to define user stories and acceptance criteria for a software project?

The best way to define user stories and acceptance criteria is through a structured vision wiki. This Skill provides embedded goals, scenarios, and rubrics within markdown pages to formalize your Agile or Lean project definitions.

Do I need markdown processing to manage project vision wikis?

Yes, markdown processing is required to author and maintain the vision wiki pages. The tool relies on markdown formatting to structure goals, scenarios, and scoring rubrics alongside JSON validation.