vision

To create a project vision document, you need a guided conversational flow that captures project goals and scope. This process generates a structured vision.md file with YAML frontmatter to align stakeholders and streamline onboarding.

Yes, you can update an existing project vision while preserving historical context. The modification process outputs changes to .context/vision.md and maintains a detailed changelog, ensuring full traceability of strategic updates.

To extract a vision document from an existing project, you derive vision insights from current project data and convert them into a structured vision.md file. This is ideal for onboarding new members or handling project pivots.

Yes, this project vision workflow requires a vision.md file containing YAML frontmatter and structured content. The system processes this input and outputs updates directly to .context/vision.md.

You need a structured vision document for project management when starting new projects, executing strategic pivots, or handling ongoing scope revisions. It guides decisions, aligns stakeholders, and streamlines team onboarding.

Using markdown for project vision limits you to text-based structured content and YAML frontmatter. It does not natively support dynamic stakeholder collaboration features, relying entirely on manual updates and extraction notes for revisions.