← ClaudeAtlas

visionlisted

Work out why a project should exist at all and write the case down: who it is for, what it is for, what it displaces, and whether it belongs in this org. Use it when the thing in front of you is not yet a project — "should this be its own project?", "who is this even for?", "convince me this is worth doing", "what's the north star here?", "write the pitch", "we're starting something new" — including when someone asks for a README intro or the elevator version and the justification underneath has never been argued anywhere. Write it and the reasoning survives; answer in chat and the next person relitigates it. Do NOT use it when the thesis is settled and what is missing is the medium-term bet under it (`/strategy`) or the order things get built (`/roadmap`). A vision with nothing under it is rarely what someone wants: if the conversation is going to run down into the bet and the sequence anyway, `/charter` walks all three in one sitting.
tsukumogami/shirabe · ★ 0 · AI & Automation · score 67
Install: claude install-skill tsukumogami/shirabe
!`bash ${CLAUDE_PLUGIN_ROOT}/scripts/skill-preflight.sh vision 2>&1 || true` @.claude/shirabe-extensions/vision.md @.claude/shirabe-extensions/vision.local.md # Vision Documents Vision documents capture WHY a project or organization should exist -- the core thesis, audience, value proposition, org fit, and success criteria. They sit at the head of the strategic chain -- VISION -> STRATEGY -> ROADMAP -- and are the strategic foundation that justifies writing requirements in the first place. A VISION's immediate downstream neighbour is a STRATEGY, and that is the only artifact type its Downstream Artifacts section lists. The chain links one level at a time so a reader walking it hits every altitude in order; the PRDs and designs under a VISION are reached through its STRATEGY and that STRATEGY's ROADMAP, not linked directly. See `references/vision-format.md` for the full rule. **Writing style:** Read `skills/writing-style/SKILL.md` for guidance. ## Artifact Lifecycle **Lifecycle:** Durable. Stays in `docs/visions/` after completion. VISION is durable because the long-term thesis a project commits to stays in the audit trail. Future readers asking why a project exists at all need the VISION to remain in place even as the project evolves. ## Vision Format See `references/vision-format.md` for the full format specification: frontmatter schema, required and optional sections, visibility-gated sections, section matrix, content boundaries, lifecycle states, validation rules