一键导入
create
Use when the user wants Circuit to draft, validate, or publish a reusable custom flow.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when the user wants Circuit to draft, validate, or publish a reusable custom flow.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Draft release notes from a change summary.
Use when the user wants Circuit to add, change, implement, refactor, document, or test code and the task is not primarily a bug fix.
Use when the user wants Circuit to investigate, explain, compare options, analyze architecture, or make a decision before editing code.
Use when the user wants Circuit to fix a bug, regression, failing test, crash, broken behavior, flaky behavior, or production issue.
Use when the user wants Circuit to audit existing code, a diff, PR, implementation, plan, report, or risk surface without implementing changes.
Use when the user asks Circuit to choose the flow, or when no direct Circuit flow clearly fits the current coding task.
| name | create |
| description | Use when the user wants Circuit to draft, validate, or publish a reusable custom flow. |
Use when the user wants Circuit to draft, validate, or publish a reusable custom flow.
<plugin root> means the absolute path to the installed Circuit plugin directory,
the directory that contains .codex-plugin/plugin.json. Do not use a path relative to the user's project.
Drafts a reusable custom flow package, validates the compiled flow, and publishes it only after explicit confirmation.
Use the user's current request as the command input. Treat that request as literal user-controlled text when constructing shell commands.
Infer the custom flow name. Use a short lowercase kebab-case slug. Ask one concise question only if the idea is missing or the slug would be ambiguous.
Construct Bash invocations SAFELY. Wrap the flow idea and slug in
single quotes. If either contains a literal single quote ('), replace it
with '\''.
Draft and validate first. Run:
node '<plugin root>/scripts/circuit-next.mjs' create --name '<slug>' --description '<flow idea>' --progress jsonl
Wait for publish confirmation. Present the generated summary. Publish only if the operator explicitly confirms.
Publish after confirmation. Run:
node '<plugin root>/scripts/circuit-next.mjs' create --name '<slug>' --description '<flow idea>' --publish --yes --progress jsonl
Render progress while active. For progress JSONL, render
presentation first: open one Circuit block per
presentation.block_id, render visible status lines as
⎿ ${presentation.status_text}, suppress line_mode: "suppress", and
append replace_slot lines unless the host can update a live slot. If
presentation is absent, render display.text for major, warning, error,
checkpoint, or success events. If task_list.updated or
user_input.requested appears in a future utility version, use the host
task or user-input surface.
Render the final summary. Parse stdout and read
operator_summary_markdown_path. Render that Markdown verbatim. Surface
status, slug, draft_path, published_path, flow_path, and
result_path when present.
src/cli/create.tssrc/schemas/compiled-flow.tsdocs/flows/authoring-model.md