一键导入
creating-workflows
How to write pikit workflow YAML files — steps, loops, branches, interpolation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
How to write pikit workflow YAML files — steps, loops, branches, interpolation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Recognizing context pressure before it degrades output quality.
Writing implementation plans — small testable steps, dependency ordering, upfront risk identification.
Evidence before claims, always — run verification commands and confirm output before making any completion or success claims.
Generate Architecture Decision Records — use when asked to document a decision, create an ADR, record why we chose X, or capture architectural rationale.
Generate a structured changelog from git history — use when asked to create a changelog, release notes, or summarize what changed between versions/tags/branches.
Deep research with Analysis of Competing Hypotheses — use when asked to do deep research, deeply investigate, validate claims, or when correctness is critical and the user wants rigorous analysis with disconfirmation testing.
| name | creating-workflows |
| description | How to write pikit workflow YAML files — steps, loops, branches, interpolation. |
Pikit workflows are YAML files in the workflows/ directory. Each workflow defines a sequence of steps executed in order by the agent.
name: string # Workflow display name
description: string # What this workflow does
budget: # Optional: token budget
limit: number # Max characters (1 token ~ 4 chars)
downgrade: string # "fast" | "skip" | "stop"
steps:
- id: string # Unique step identifier
model: string # Model alias (e.g., "smart", "fast")
prompt: string # The prompt to send (supports {{variable}} interpolation)
command: string # Alternative: shell command to run
args: object # Arguments for command steps
skills: string[] # Skills to load for this step
approval: bool # Require user confirmation before running
loop: # Optional: repeat this step
max: number # Maximum iterations
until: string # Stop when response contains this string
branch: # Optional: conditional execution
- when: string # Match this text in the response
goto: string # Jump to this step id
parallel: string[] # Run listed step ids (sequentially, in order)
{{input}} — the user's input passed to /workflow{{step_id}} — output from a previous step, referenced by its idOnly referenced keys are injected into the prompt. Unreferenced step outputs are excluded to save tokens.
name: summarize-and-review
description: Summarize a document then review the summary
steps:
- id: summarize
model: smart
prompt: |
Summarize the following document in 3 bullet points:
{{input}}
- id: review
model: smart
prompt: |
Review this summary for accuracy and completeness.
Summary: {{summarize}}
Original: {{input}}
steps:
- id: implement
model: smart
prompt: |
Execute the next incomplete todo from the plan.
If all todos are complete, say "ALL_DONE".
loop:
max: 20
until: ALL_DONE
steps:
- id: check
model: fast
prompt: Run the test suite and report results.
branch:
- when: all passing
goto: done
- when: failure
goto: fix
/workflow list # List available workflows
/workflow feature implement auth # Run "feature" workflow with input "implement auth"
/workflow --dry-run feature test # Preview steps without executing
ids — they appear in the chat as step labels.--dry-run first.approval: true on destructive steps for a confirmation gate.