flow-next

Solid

Manage .flow/ tasks and specs. Triggers: 'show me my tasks', 'list specs', 'what tasks are there', 'add a task', 'create task', 'what's ready', 'task status', 'show fn-1-add-oauth'. NOT for /flow-next:plan or /flow-next:work.

AI & Automation 621 stars 47 forks Updated 4 days ago MIT

Install

View on GitHub

Quality Score: 92/100

Stars 20%
93
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Flow-Next Task Management Quick task operations in `.flow/`. For planning features use `/flow-next:plan`, for executing use `/flow-next:work`. ## Preamble **CRITICAL: flowctl is BUNDLED — NOT installed globally.** `which flowctl` will fail (expected). Define once; subsequent blocks use `$FLOWCTL`: ```bash FLOWCTL="${DROID_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}/scripts/flowctl" ``` **Discover all commands/options:** ```bash $FLOWCTL --help $FLOWCTL <command> --help # e.g., $FLOWCTL task --help ``` ## Quick Reference ```bash # Check if .flow exists $FLOWCTL detect --json # Initialize (if needed) $FLOWCTL init --json # List everything (specs + tasks grouped) $FLOWCTL list --json # List all specs $FLOWCTL specs --json # List all tasks (or filter by spec/status) $FLOWCTL tasks --json $FLOWCTL tasks --spec fn-1-add-oauth --json $FLOWCTL tasks --status todo --json # View spec with all tasks $FLOWCTL show fn-1-add-oauth --json $FLOWCTL cat fn-1-add-oauth # Spec markdown # View single task $FLOWCTL show fn-1-add-oauth.2 --json $FLOWCTL cat fn-1-add-oauth.2 # Task spec # What's ready to work on? $FLOWCTL ready --spec fn-1-add-oauth --json # Create task under existing spec $FLOWCTL task create --spec fn-1-add-oauth --title "Fix bug X" --json # Set task description and acceptance (combined, fewer writes) $FLOWCTL task set-spec fn-1-add-oauth.2 --description /tmp/desc.md --acceptance /tmp/accept.md --json # Or use stdin with heredoc (no temp file)...

Details

Author
gmickel
Repository
gmickel/flow-next
Created
5 months ago
Last Updated
4 days ago
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

flow-next-work

Execute a Flow spec or task systematically with git setup, task tracking, quality checks, and commit workflow. Use when implementing a plan or working through a spec. Triggers on /flow-next:work with Flow IDs (fn-1-add-oauth, fn-1-add-oauth.2, or legacy fn-1, fn-1.2, fn-1-xxx, fn-1-xxx.2).

621 Updated 4 days ago
gmickel
AI & Automation Solid

flow-next-plan

Create structured build plans from feature requests or Flow IDs. Use when planning features or designing implementation. Triggers on /flow-next:plan with text descriptions or Flow IDs (fn-1-add-oauth, fn-1-add-oauth.2, or legacy fn-1, fn-1.2, fn-1-xxx, fn-1-xxx.2).

621 Updated 4 days ago
gmickel
AI & Automation Solid

flow-next-sync

Manually trigger plan-sync to update downstream task specs after implementation drift. Use when code changes outpace specs.

621 Updated 4 days ago
gmickel
AI & Automation Solid

flow-next-interview

Interview user in-depth about a spec, task, or spec file to extract complete implementation details. Use when user wants to flesh out a spec, refine requirements, or clarify a feature before building. Triggers on /flow-next:interview with Flow IDs (fn-1-add-oauth, fn-1-add-oauth.2, or legacy fn-1, fn-1.2, fn-1-xxx, fn-1-xxx.2) or file paths.

621 Updated 4 days ago
gmickel
AI & Automation Solid

flow-next-deps

Show spec dependency graph and execution order. Use when asking 'what's blocking what', 'execution order', 'dependency graph', 'what order should specs run', 'critical path', 'which specs can run in parallel'.

621 Updated 4 days ago
gmickel