flow-plan

Promotes validated OpenSpec candidates into scaffolded change proposals with retro-ready metadata.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a validated product idea into an actionable change often loses context: the reasoning behind the decision, the expected outcome, and the signals to watch get scattered or forgotten. This Skill bridges that gap by promoting an active candidate from openspec/candidates/ into a full OpenSpec change while capturing the metadata a future retrospective needs. ## Core Features & Use Cases - Candidate-to-Change Promotion: Validates that a candidate is active and has un-promoted entries, then delegates scaffolding to /opsx:propose to generate proposal.md, design.md, and tasks.md. - Retro-Readiness Capture: Runs a short interview to record the expected outcome, watch signals, and open questions into a flow.md file linked back to the parent candidate. - Candidate File Maintenance: Automatically bumps last-reviewed and flips the promoted checklist entry to an in-flight status. - Use Case: Your team validated a "rotate secrets pipeline" candidate during strategy review. Run this Skill to promote one discrete change from it, capture what success looks like, and hand off a fully scaffolded OpenSpec change ready for implementation. ## Quick Start Ask the assistant to run /flow-plan with a candidate id, for example: promote the rotate-secrets-pipeline candidate to an OpenSpec change.

Frequently Asked Questions about flow-plan

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

FAQPage Schema
How do I promote an OpenSpec candidate to a change?

Run /flow-plan with the candidate id, for example /flow-plan rotate-secrets-pipeline. The skill verifies the candidate is active, lets you pick one un-promoted checklist entry, captures expected outcomes, and delegates scaffolding to /opsx:propose.

What is the difference between flow-plan and opsx:propose?

flow-plan is a thin wrapper around /opsx:propose that adds project conventions: a relational link back to the parent candidate, a flow.md file with expected outcome and watch signals, and candidate file updates. For ad-hoc work not tied to a candidate, use /opsx:propose directly.

Can I promote multiple changes from one candidate at once?

No. The skill enforces one change per invocation so each retrospective stays focused. Epic-style candidates with multiple un-promoted entries are promoted one at a time across separate runs.

What happens if the candidate is completed or rejected?

The skill refuses to promote candidates with status completed, rejected, or superseded and suggests revisiting Strategy. To proceed, revive the candidate to active status via /flow-strategy with explicit reasoning.

What is flow.md in an OpenSpec change directory?

flow.md is a metadata file written into openspec/changes/<change-id>/ containing frontmatter linking to the parent candidate plus sections for expected outcome, watch signals, and open questions. It gives the eventual retro concrete criteria to compare against.