Menü
Display the current FLOW configuration from .flow.json — version and per-skill autonomy settings.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Release a new version of the FLOW plugin. Bumps version in plugin.json and marketplace.json, commits, tags, pushes, and creates a GitHub Release.
Abort the current FLOW feature. Closes the PR, deletes the remote branch, removes the worktree, and deletes the state file. Available from any phase. The confirmation prompt is governed by the skills.flow-abort config in the state file.
Phase 2: Code — execute plan tasks one at a time with TDD. Review diff before each commit. bin/flow ci must pass before moving to the next task. Project architecture standards enforced.
Review the full diff, then git add + commit + push. Use at every commit checkpoint in the FLOW workflow.
Phase 4: Complete — merge the PR, remove the worktree, and delete the state file. Final phase.
Clear the autonomous-flow halt set when the user spoke mid-flow. Invokes `bin/flow clear-halt` so the next assistant turn resumes execution. User-only: the model cannot invoke this skill.
| name | flow-config |
| description | Display the current FLOW configuration from .flow.json — version and per-skill autonomy settings. |
/flow:flow-config
Display-only skill. Reads .flow.json from the project root and shows the current configuration.
Use the Glob tool to check for .flow.json at the project root.
If .flow.json does not exist, tell the user:
"No
.flow.jsonfound. Run/flow:flow-primeto configure this project."
Stop here.
If .flow.json exists, read it with the Read tool.
Output the following banner in your response (not via Bash) inside a fenced code block:
```text
──────────────────────────────────────────────────
FLOW v<version> — Config
──────────────────────────────────────────────────
```
Then display the skills configuration as a markdown table:
| Skill | Commit | Continue |
|-----------|--------|----------|
| start | — | manual |
| code | manual | manual |
| review | auto | auto |
| learn | auto | auto |
| complete | — | auto |
| abort | — | auto |
Use the actual values from .flow.json. The table above is just an example.
Column rules:
commit and continue values from the nested object— for Commit, show the continue value from the nested objectLegacy format handling: If .flow.json has the old single-value format (e.g., "code": "manual" instead of {"commit": "manual", "continue": "manual"}), display the single value in both columns for phase skills that should have two axes.
If .flow.json has no skills key, show "No skills configured — using built-in defaults" instead of the table.
Tell the user that autonomy is configured in .flow.json — there are no --auto/--manual invocation flags — and that re-running /flow:flow-prime changes it.
.flow.jsoncd <path> && git — use git -C <path> for git commands in other directoriesbin/flow — it detects the project root internally