vision-elicitation

Run a structured 13-section Q&A to populate project vision and architecture docs.

5|Updated May 12, 2026

Search Tags:#workflow #templates #documentation #scaffolding #vision #elicitation

Ready to run

npx skills add https://github.com/ramboz/jig --skill vision-elicitation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vision-elicitation
Source: https://github.com/ramboz/jig/tree/main/skills/vision-elicitation
Command: npx skills add https://github.com/ramboz/jig --skill vision-elicitation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Elicit and populate project vision and architecture slots by running a structured 13-section Q&A against the template.

Core Features & Use Cases

Structured 13-section Q&A for vision and architecture slots.
Writes filled markers into docs/product-vision.md and docs/architecture.md, with optional deferral to other vision/discovery skills.
Use cases capture is supported via a conversational loop after the Scope slot.

Quick Start

Run the vision elicitation flow after scaffold-init to populate the template docs/product-vision.md and docs/architecture.md.

Frequently Asked Questions about vision-elicitation

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

FAQPage Schema

How do I elicit and document project vision and architecture during scaffolding?▼

To document project vision, run a structured 13-section Q&A flow that populates docs/product-vision.md and docs/architecture.md, writing filled, unfilled, or skipped markers for each section directly into your scaffolding docs.

What is the best way to capture product scope and use cases for a new project template?▼

Capturing product scope is supported through a conversational loop that follows the Scope slot in the elicitation flow, allowing you to define and document specific use cases within your project template.

Do I need any external runtime dependencies to run vision elicitation on my documentation?▼

No external runtime dependencies are required for vision elicitation. The Skill operates independently to populate your documentation templates using its internal structured Q&A logic and markers.

Can I re-run vision elicitation to refresh only specific sections of my product vision docs?▼

You can re-run vision elicitation using a hash-based divergence check protocol that supports optional per-section refresh, allowing targeted updates to docs/product-vision.md without overwriting previously filled content.

Does vision elicitation work with other installed product discovery or framing skills?▼

Vision elicitation supports deferral to any other installed vision or discovery skill. If another skill claims handling for vision elicitation, product discovery, or project framing, the flow can defer to it.

When should I run vision elicitation in my project scaffolding workflow?▼

You should run vision elicitation after scaffold-init. It applies directly to the initialized project structure to fill docs/product-vision.md and docs/architecture.md with structured vision and architecture data.