القائمة
Use when asked to create or design a vibe-lab workflow artifact that coordinates skills, agents, hooks, plugins, and verification gates across Claude Code, OpenCode, and OMP/Pi.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | create-workflow |
| description | Use when asked to create or design a vibe-lab workflow artifact that coordinates skills, agents, hooks, plugins, and verification gates across Claude Code, OpenCode, and OMP/Pi. |
Use this skill when the user asks to:
Do not use for one-off task lists. Use a workflow only when multiple artifacts or CLI adapters need a shared contract.
A workflow is a deterministic artifact, not a runtime framework. Do not add workflow runtime until bin/inject and bin/doctor validate the artifact type.
Use canonical/workflow-template.md.
packages/cli/library/workflows/<name>.md for documentation-only workflow surface; runtime workflow dispatch remains retired.n/a explicitly when skipped.n/a depending on whether the workflow changes behavior.lazyai-cli compile and lazyai-cli doctor after workflow support is wired.n/a.n/a.Use when debugging a failing test, broken build, runtime error, or unexpected system behavior. Drives hypothesis-based investigation, root-cause fixes, verification, and reusable learning capture.
Use when a claim, plan, spec, doc, or design must be attacked against source evidence before implementation or approval. Uses write tools, shell execution, and may spawn subagents. Invoke with enable_write_tools=true and enable_subagent_tools=true.
Use when fixing broken behavior and the priority is reproduce, root cause, regression proof, and the smallest safe repair. Uses write tools, shell execution, and may spawn subagents. Invoke with enable_write_tools=true and enable_subagent_tools=true.
Use when reviewing code changes with explicit stage, target, and focus so own-code checks and others’ PR reviews stay distinct but share one contract. Uses write tools, shell execution, and may spawn subagents. Invoke with enable_write_tools=true and enable_subagent_tools=true.
Use when the deliverable is docs or reference material and every claim must stay tied to observed behavior or cited source evidence. Uses write tools, shell execution, and may spawn subagents. Invoke with enable_write_tools=true and enable_subagent_tools=true.
Use when adding or changing product behavior that must ship with explicit purpose, scenarios, and verification. Uses write tools, shell execution, and may spawn subagents. Invoke with enable_write_tools=true and enable_subagent_tools=true.