visionlisted
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