flow-vision

Refines project intent in CLAUDE.md through guided thought-partner conversations.

Updated Nov 7, 2023
One-click install
npx skills add https://github.com/lstellway/nixfiles --skill flow-vision-lstellway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-vision
Source: https://github.com/lstellway/nixfiles/tree/main/modules/home-manager/claude/skills/flow-vision
Command: npx skills add https://github.com/lstellway/nixfiles --skill flow-vision-lstellway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Project intent documents drift out of sync with reality over time, and teams rarely pause to deliberately re-examine why a project exists. This Skill provides a structured, conversational process for keeping a project's north star, values, and non-goals honest and current. ## Core Features & Use Cases - Guided vision sessions: Acts as a thought partner using a curated question bank covering north star, values, non-goals, failure modes, drift detection, and external shifts. - Targeted CLAUDE.md edits: Produces small, user-gated edits to CLAUDE.md (or the right surface such as rules, specs, or skill guardrails) rather than a separate vision document. - Drift detection: Reads recent retros, commits, and memory to surface contradictions between stated intent and actual project behavior. - Use Case: Run a quarterly health check where the skill digests CLAUDE.md and recent retros, presents a snapshot of stated intent and drift signals, then walks you through refining non-goals that no longer hold. ## Quick Start Ask the assistant to run a flow-vision session to review whether the project's stated intent in CLAUDE.md still matches reality.

Frequently Asked Questions about flow-vision

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep my project's CLAUDE.md vision section up to date?

Run a flow-vision session, which reads your current CLAUDE.md, recent retros, and memory, then presents a snapshot of stated intent and drift signals. It guides a conversation and proposes small, user-approved edits rather than rewriting the file.

How often should I run a project vision review?

Roughly quarterly is the recommended cadence. Running it more often usually signals that strategy, planning, or implementation is the actual problem rather than vision drift.

Does flow-vision create a separate vision document?

No. The skill deliberately avoids creating a separate vision doc. CLAUDE.md is the primary home for project intent, and refinements land as targeted edits there or in the appropriate surface such as rules, specs, or skill guardrails.

When should I use flow-vision instead of flow-strategy?

Use flow-vision when the question is why the project exists or whether stated intent still holds. Use flow-strategy when deciding what to work on next; strategy sits downstream of vision and may flag drift that triggers a vision pass.

What are the limitations of a vision refinement session?

The skill only makes small, sentence-level edits and never rewrites whole sections. If a full rewrite seems needed, that signals a larger strategy-scoped change that should become a candidate instead of landing inline.