菜单
Use when creating a new agentic workflow skill. Triggers - need new multi-step orchestrated process, want to add workflow to agentic framework, building spec-driven pipeline.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | agentic:workflow:create-workflow |
| description | Use when creating a new agentic workflow skill. Triggers - need new multi-step orchestrated process, want to add workflow to agentic framework, building spec-driven pipeline. |
| argument-hint | <workflow description or idea> |
Usage: /agentic:workflow:create-workflow <description>
Create new agentic workflow skills through structured qualification, confirmation, configuration, and generation. Produces complete workflow directories following agentic patterns.
1. Input Qualification -> 2. Assumption Confirmation -> 3. Context Confirmation [loop if rejected] -> 4. Output Folder Config -> 5. Storage Config -> 6. Workflow Generation (/writing-skills)
digraph workflow {
rankdir=TB;
input [label="Input Qualification\n(analyze, assumptions)" shape=box];
assumptions [label="Assumption\nConfirmation" shape=box];
context [label="Context\nConfirmed?" shape=diamond];
output [label="Output Folder\nConfig" shape=box];
storage [label="Storage\nConfig" shape=box];
generate [label="Generate Workflow\n(/writing-skills)" shape=box];
done [label="DONE" shape=doublecircle];
input -> assumptions;
assumptions -> context;
context -> output [label="confirmed"];
context -> assumptions [label="needs changes"];
output -> storage;
storage -> generate;
generate -> done;
}
Execute steps in order. Each step file contains detailed instructions.
| Step | File | Description |
|---|---|---|
| 1 | steps/step-01-input-qualification.md | Analyze input, log assumptions & open questions |
| 2 | steps/step-02-assumption-confirmation.md | Confirm each assumption, resolve open questions |
| 3 | steps/step-03-context-confirmation.md | Present full context, get user confirmation |
| 4 | steps/step-04-output-config.md | Detect IDE, ask output folder for workflow files |
| 5 | steps/step-05-storage-config.md | Ask where created workflow stores progress & artifacts |
| 6 | steps/step-06-workflow-generation.md | Generate all files using /writing-skills + agentic patterns |
Start by reading steps/step-01-input-qualification.md and follow NEXT STEP at end of each file.
| Template | Description |
|---|---|
templates/workflow-state.yaml | State tracking template |
This workflow does NOT delegate to subagents — all work is orchestrator-driven through structured questioning and file generation.
You:
dependencies.ts (if in agentic source tree)You NEVER:
If the workflow description lacks enough detail to extract assumptions:
If user rejects context confirmation 3+ times:
If file generation fails:
All outputs: .claude/_agentic_output/task/create-workflow/{topic}/{instance_id}/
workflow-state.yaml — progress trackingqualified-input.md — analyzed input with assumptions & open questionsworkflow-design.md — full qualified context documentStart workflow by reading step 1:
Read steps/step-01-input-qualification.md
Follow each step file's instructions sequentially. Each step ends with a reference to the next step.
Use when producing product artifacts - epics, user stories, acceptance criteria, or analytics specs.
Use when defining product direction, vision document sections, or roadmap. Triggers on strategic product planning, vision creation, or vision document quality review.
Use when designing UI, choosing colors, typography, spacing, creating visual hierarchy, or making design decisions. Based on Refactoring UI by Wathan & Schoger.
Use when someone needs a plain-language explanation of how an existing feature or edge case behaves in the codebase. Triggers - non-technical stakeholder asks how something works, need code-informed functional explanation, need to understand rules or edge cases without implementation planning.
Use when a developer wants to go from rough idea to working code autonomously. Triggers - imperfect prompt, solo dev wants full pipeline, "just build it", idea to implementation without manual steps.
Use when building frontend features from idea to implementation. Triggers on new UI components, pages, or features needing design and code.