workflow-builder
GitHub用于生成一次性工作流适配器，仅负责按明确输入执行独立操作并报告结果。禁止重试、状态存储或框架抽象，旨在防止脚本膨胀为未请求的编排器，确保调用者掌控流程。
Trigger Scenarios
Install
npx skills add boshu2/agentops --skill workflow-builder -g -y
SKILL.md
Frontmatter
{
"name": "workflow-builder",
"context": {
"intent": {
"mode": "questions"
},
"window": "fork",
"sections": {
"exclude": [
"HISTORY"
]
}
},
"consumes": [],
"metadata": {
"tier": "meta",
"effects": [
"write_workflow_script"
],
"disposition": "keep_specialist",
"capabilities": [
"workflow_builder"
],
"dependencies": [],
"canonical_status": "canonical"
},
"produces": [
"workflow-script"
],
"practices": [
"pragmatic-programmer",
"hexagonal-architecture",
"agile-manifesto"
],
"context_rel": [
{
"kind": "customer-of",
"with": "automation-shape-routing"
},
{
"kind": "shared-kernel",
"with": "operationalize"
}
],
"description": "Scaffold an explicit one-shot workflow adapter without lifecycle authority. Triggers: \"build a workflow adapter\", \"scaffold a one-shot workflow\".",
"hexagonal_role": "supporting",
"output_contract": "a runnable one-shot workflow with explicit inputs and outputs",
"skill_api_version": 1
}
Workflow Builder — one-shot adapter authoring
Build a thin adapter only when a caller needs to dispatch an explicit set of independent operations. A workflow is convenience code, never a correctness or lifecycle authority.
At-most-once dispatch over explicit inputs is the whole safety argument: a workflow that cannot retry or select work cannot compound a failure, so the worst case is one reported error per operation.
Named failure mode — framework gravity: a one-shot script growing config files, plugin hooks, and a state store until it is an unrequested orchestrator.
Anti-pattern: adding retry-on-failure "just for robustness". Corrective: report the per-operation error and stop; the caller owns whether anything runs again.
Contract
- Inputs, executors, write scopes, and outputs are supplied explicitly.
- Each operation is dispatched at most once.
- Parallel operations must have caller-proven disjoint write scopes.
- The workflow reports per-operation output or error and then stops.
- It contains no work selection, retry, budget, queue, tracker, validation, Git, integration, closure, release, or delivery logic.
- Optional substrate state cannot be translated into RPI or verdict state.
Prefer the smallest script supported by the target runtime. Include a dry-run or fixture demonstrating exact dispatch count and failure reporting. Do not create a new framework or SDK abstraction unless the caller explicitly requests one.
Version History
- d9f9c50 Current 2026-08-27 19:43
- 7b07a7d 2026-08-19 22:01
- 3f402e5 2026-07-24 22:08
