Tasks & Inventory
The top-level flow-next skill handles conversational requests about the state of .flow/. It is the meta-skill behind phrases like:
- “show me my tasks”
- “list specs”
- “what’s ready”
- “add a task for X”
- “show fn-1-add-oauth”
- “task status”
It does not plan or work — those belong to /flow-next:plan and /flow-next:work. This skill is for inspection, quick edits, and bookkeeping.
What it can do
Section titled “What it can do”| Intent | Underlying flowctl |
|---|---|
| List everything | flowctl list --json |
| List specs | flowctl specs --json |
| List tasks | flowctl tasks --json (with --spec or --status filters) |
| Show a spec or task | flowctl show <id> --json, flowctl cat <id> |
| What’s ready | flowctl ready --spec <id> --json |
| Add a task | flowctl task create --spec <id> --title <...> |
| Set task description and acceptance | flowctl task set-spec <id> --description ... --acceptance ... |
| Start a task | flowctl start <id> |
| Mark done | flowctl done <id> --summary-file ... --evidence-json ... |
| Validate structure | flowctl validate --spec <id> / --all |
The skill picks the right flowctl invocation from the request and surfaces the result in conversational form.
Why it exists
Section titled “Why it exists”flowctl is precise but verbose, and .flow/ is just files. The meta-skill bridges the two: ask in plain English, get a structured answer that you can act on or hand back to a slash command.
It is also the entry point for non-planning tasks like adjusting a spec’s evidence after the fact, or adding a small follow-up task that does not warrant a full /flow-next:plan run.
When NOT to use it
Section titled “When NOT to use it”- Designing a new feature →
/flow-next:plan. - Executing a spec →
/flow-next:work. - Refining a vague spec →
/flow-next:interview. - Synthesizing a conversation into a spec →
/flow-next:capture.
If the request involves multi-step thinking, hand it to the dedicated skill. This one is for direct manipulation of .flow/.
Discovery
Section titled “Discovery”flowctl --helpflowctl <command> --helpflowctl is bundled with the plugin, not installed globally. The meta-skill resolves the bundled path automatically.