flow-strategy

Runs a collaborative strategy session to triage, rank, and manage project candidates in OpenSpec.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deciding what to work on next in a project is hard when ideas, in-flight changes, and retros are scattered across files. This Skill structures that decision-making into a guided strategy session that reads project state, surfaces candidates, and keeps the backlog ranked and current. ## Core Features & Use Cases - Project state digest: Delegates to an Explore agent to summarize CLAUDE.md, OpenSpec specs, in-flight changes, candidates, retros, and recent commits into a one-page snapshot. - Branching question bank: Provides targeted prompt sets for triaging new ideas, re-ranking candidates, reflecting on retros, and detecting vision drift. - Candidate lifecycle management: Proposes creating, updating, re-ranking, or archiving candidate files in openspec/candidates/ with user approval before any write. - Use Case: You have a vague idea for improving your project and several stale backlog items. Run a strategy session to place the idea, re-rank existing candidates by impact and effort, and get a recommendation on which candidate to promote to a full change proposal. ## Quick Start Ask the assistant to run a flow-strategy session to figure out what to work on next in this project.

Frequently Asked Questions about flow-strategy

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

FAQPage Schema
How do I decide what to work on next in an OpenSpec project?

Run a strategy session that digests your project state (specs, in-flight changes, candidates, retros, recent commits) into a snapshot, then uses targeted questions to surface, triage, and rank candidates by impact and effort before recommending a next step.

What is the difference between flow-strategy and flow-plan?

Strategy decides which change to do next at the project level, while plan designs how to implement one specific change. If you need implementation detail or design for a known change, use flow-plan instead.

How do I manage a candidate backlog in openspec/candidates?

Candidates are Markdown files with frontmatter tracking status, impact, effort, dependencies, and last-reviewed date. The session proposes creating, updating, re-ranking, or archiving candidates, and every file write requires your explicit approval.

What happens if openspec/candidates does not exist in my project?

The skill proposes scaffolding the directory, including an archive subfolder and a _template.md file with the standard candidate structure. It will not fail silently when the directory is missing.

When should I not use a strategy session?

Skip it when you need implementation details for a specific change (use flow-plan), when vision itself feels stale (use flow-vision), or for hotfixes and urgent one-offs that can go straight to a change proposal.