메뉴
Use when a user asks to create or validate a reusable flow from a declarative agents/phases/loops definition. Interviews the user, writes .pi/workflows/<name>.yaml, and registers /<name>.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | sf-flow-create-workflow |
| description | Use when a user asks to create or validate a reusable flow from a declarative agents/phases/loops definition. Interviews the user, writes .pi/workflows/<name>.yaml, and registers /<name>. |
Turn a user's intent into a declarative flow YAML at .pi/workflows/<name>.yaml, validate it, and register it as a /<name> command runnable via sf_flow_auto.
Ask the user ONE question at a time for any missing field:
name (kebab-case)descriptioninput type (prompt / md-file / prd / jira)agents — for each agent: name, tools, model, thinking, isolated, and whether it needs a schema (e.g. verdict)phases — for each phase: id, run type (agent/skill/raw), prompt, and any fanout/verify/in/outloops — for any phase: until_dry or until:approved (+ fail_on + max_rounds)Write the collected definition to .pi/workflows/<name>.yaml using the writeFlowYaml serializer (or write the file directly in the documented format).
For each agent in agents: without an existing .md (check ~/.pi/agent/agents/<name>.md then <cwd>/.pi/agents/<name>.md), write a write-once stub:
Run validateFlowYaml on the assembled flow (the tool returns errors). If errors, surface them and re-interview only the broken parts. Repeat until valid.
Register /<name> (via registerGeneratedFlow) so the flow is runnable via sf_flow_auto <name> <input>.
Tell the user: Flow "<name>" created at .pi/workflows/<name>.yaml. Run it with: sf_flow_auto <name> "<prompt>" (or a file/PRD/Jira id).
The 3 knobs: agents, phases, loops. See the canonical template at packages/flow/templates/workflow.yaml and the spec §3. Each phase runs exactly one of agent / skill / raw. Cross-field rules (enforced by validateFlowYaml):
fanout is only supported on agent phases, and requires the phase to declare out;until_dry requires the phase to set fanout;until: approved requires the phase agent to declare a verdict schema;out values must be unique across phases.Use when a plan folder created by sf-pair-plan must be executed milestone-by-milestone in a worktree, with a per-milestone TDD→review→commit→tracker loop, then finalized so the branch is preserved for a PR.
Use when a user asks to create a structured implementation plan with milestones, stories, and reviewer approval using pi-subagents.
Execute a single task end-to-end with plan review, implementation review, verification, and one persistent task-plan artifact.
Use when a diff or codebase must receive a CodeRabbit-style audit — 7 finder angles, a dual-blind AND-gate, and fix-apply — returning P0–P3 findings and an APPROVED/REVISE verdict.
Use when a defined flow (.pi/workflows/<name>.yaml) must be run end-to-end with no human gates. Input may be a prompt, a markdown file, a PRD, or a Jira story.
Use when a plan folder created by sf-flow-plan must be executed in a single worktree (flow/<slug>) with TDD per story and a non-optional audit gate before commit, then finalized so the branch is preserved for a PR.