visionlisted

@.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 upstream of PRDs (which capture WHAT to build) and are the strategic foundation that justifies writing requirements in the first place. **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, and quality guidance. Load it during Phases 3 and 4. ## File Location Vision documents live at `docs/visions/VISION-<topic>.md` (kebab-case). No directory movement until Sunset, which moves files to `docs/visions/sunset/`. Stable paths keep cross-references durable and git blame readable. ## Repo Visibility Before writing content, detect visibility from CLAUDE.md (`## Repo Visibility: Public|Private`). If not found, infer from repo path (`private/` -> Private, `public/` -> Public; defa