visionera

Create and refine a VISION.md north star document from codebase and domain research.

3|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/jgabor/agentera --skill visionera
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: visionera
Source: https://github.com/jgabor/agentera/tree/main/skills/visionera
Command: npx skills add https://github.com/jgabor/agentera --skill visionera

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Visionera guides teams to create and maintain a compelling north-star vision (VISION.md) for a project by synthesizing codebase insights, domain understanding, and aspirational challenge.

Core Features & Use Cases

  • Create or refine a project Vision.md that defines north star, personas, principles, direction, and identity.
  • Read and align with existing artifacts (PROGRESS.md, DECISIONS.md, HEALTH.md, DESIGN.md) to ensure the vision stays grounded in reality.
  • Provide a repeatable process for mode switching (Create/Refine) and artifact mapping with .agentera contracts to sustain autonomous development.
  • Real-world use: a team defines a multi-month product vision with concrete personas and guiding principles to steer architecture and roadmap.

Quick Start

Initiate the Create mode to draft a new VISION.md that defines the north star, personas, principles, and direction.

Frequently Asked Questions about visionera

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

FAQPage Schema
How do I create a north star vision document for a software project?

A project north star document defines long-term product direction, personas, and guiding principles. It is needed when steering autonomous development over multiple months to ensure architecture and roadmap alignment.

How do I refine an existing project vision to align with current architecture?

To refine an existing project vision, use Refine mode to read artifacts like DESIGN.md, HEALTH.md, PROGRESS.md, and DECISIONS.md, ensuring the updated VISION.md stays grounded in actual codebase reality.

Can I align product strategy with existing design and progress artifacts?

Yes, you can align product strategy by reading existing artifacts such as DESIGN.md, PROGRESS.md, HEALTH.md, and DECISIONS.md to ensure the project vision remains grounded and aligned with current architecture and plans.

What is the best way to maintain a product vision during long-term autonomous development?

The best way to maintain a product vision during autonomous development is using a repeatable process with Create and Refine modes and .agentera contracts to map artifacts, sustaining continuous architecture and roadmap alignment.

Does maintaining a project vision document require existing codebase artifacts?

Maintaining a project vision does not strictly require existing artifacts for initial creation, but reading DESIGN.md, HEALTH.md, PROGRESS.md, and DECISIONS.md is essential for Refine mode to keep the vision grounded in reality.