القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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 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>.
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.
| name | sf-flow-auto |
| description | 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. |
Run a defined flow end-to-end, no human gates. Input forms: inline prompt, markdown file, PRD, or Jira story (resolved via @pi-stef/atlassian).
Read .pi/workflows/<workflow>.yaml. Validate it (validateFlowYaml). Generate the pi-dw script (idempotent). If the flow isn't registered, error with the create hint.
prompt → use verbatim as the flow's args.inputmd-file → read the file, pass contents as args.inputprd → parse the PRD file, pass as args.inputjira → resolve the story via @pi-stef/atlassian (Jira), pass description+acceptance as args.inputExecute the generated pi-dw script with args.input. Phases run sequentially; intra-phase fan-out via parallel(). Loops (until_dry / until:approved) run to completion. tmux visualization (if enabled) shows per-agent panes.
Each phase exits success / no-op / blocked / exhausted. On blocked/exhausted, stop and report. No human gates; on completion return the flow's result.
Send a completion summary via notify-telegram.sh.