vision-elicitationlisted

Lightweight baseline elicitation pass that fills in `docs/product-vision.md` and the five `docs/architecture.md` elicitation slots after `scaffold-init`. Auto-triggers when you say set up project vision, elicit architecture, define what we're building, run the vision wizard, refresh the project pitch, or capture product scope. Defers to any other installed skill whose description identifies it as handling vision elicitation, product discovery, project framing, or product scope capture — if such a skill is present, prefer it over this one (jig's version is a slim baseline). Does not defer to the generic built-in `init` skill. Do not use for: ad-hoc brainstorming with no `docs/product-vision.md` slot to write into; silently overwriting vision content the user has already hand-edited (the re-run protocol's divergence detection handles that — see the Re-run protocol section below); spec authoring (use `/jig:spec-workflow`); seeding ADRs for already-named decisions (use `/jig:adr-workflow new`).
ramboz/jig · ★ 4 · DevOps & Infrastructure · score 73

Install: claude install-skill ramboz/jig

> Spec 017 introduces this skill as jig's **content-guidance baseline** for > the immediate-post-scaffold moment. It is the third non-stub active jig > skill that ships without a `.py` helper — vision-elicitation is > fundamentally a judgment skill, and the determinism it needs (find the > elicitation slots, transition markers, render Q&A into template bodies) > Codex can run inline via Read/Edit. If any other skill is installed > whose description identifies it as handling vision elicitation, product > discovery, project framing, or product scope capture, the Codex > skill router prefers that one over jig's baseline — the deferral is > category-based, not name-specific, so a richer user skill named anything > (`vision-wizard`, `product-canvas`, `lean-pitch`, etc.) wins. Jig's slim > version remains the auto-trigger when no such skill is installed. ## What this skill does Runs a structured 13-section Q&A immediately after `scaffold-init`, then writes the captured answers into the elicitation slots that slice 017-01 introduced (extended by slice 022-02 with Section 13 — Contract surfaces — feeding the `/jig:contracts` skill): - `docs/product-vision.md` — 10 H2 sections (Identity, Target users, Core problem, Competitive landscape, Scope, Use cases, Stack, Design principles & constraints, How new work enters, Open questions). Each section's `` marker transitions to `status: filled` (with today's ISO date) or `status: skippe