create-workflow

You are creating or revising the /workflow command for a ClaudeWorks profile. /workflow is a dormant slash command stored in the profile's workflow field in ~/.claudeworks/profiles.json — when the user types /workflow inside a session running under that profile, Claude Code walks through a specific orchestration of the profile's tools (plan → scaffold → implement → verify → ship, or whatever sequence you co-design with the user).

You always run interactively. You never draft the body unilaterally — you propose one stage at a time and let the user confirm, tweak, or add. This is true whether the user invoked the skill themselves (e.g. "add a /workflow to my frontend-dev profile") or create-profile chained it during new-profile assembly.

The default path is direct invocation: the skill reads the user's current profile (from CLAUDE_CONFIG_DIR), walks them through shape + sequencing, and patches profiles.json in place. There is one special case — parent mode — when create-profile hands over a context block so new-profile assembly can include the workflow in a single write. The rest of this SKILL.md spells out how to handle that handoff; everything else is the default.

• Parent mode — create-profile hands over a context block with the profile description, the picked plugins, the chosen workflow shape, and the stage list. You skip profile selection and shape picking and go straight to sequencing. When done, you emit the final body between marker lines so the parent skill can capture it as P_WORKFLOW and fold it into its own write-profile.js call.

Step 0 — Detect invocation mode

Look for a block in the incoming prompt of the following shape (this is what create-profile emits when it hands off):

CREATE_WORKFLOW_CONTEXT
{
  "profileDescription": "...",
  "profileName": "...",
  "pickedPlugins": [{"id":"...","displayName":"...","enabledItems":{"skills":[...],"commands":[...],"agents":[...]}}, ...],
  "shapeId": "feature-development",
  "stages": [{"id":"plan","name":"Plan","intent":"...","keywords":[...]}, ...]
}
END_CREATE_WORKFLOW_CONTEXT

• If the block is present, parse it and jump straight to Step 3 (sequencing). Use profileDescription, pickedPlugins, and stages from the block — do not ask the user to restate any of these.
• If the block is absent, proceed to Step 1.

Do not mix modes — either the parent hands over context, or the user drives the whole flow. Never fall through "half-handed-over" because the block was malformed; if parsing fails, tell the user the handoff broke and ask them to re-run create-profile, rather than silently restarting the direct flow inside a half-completed profile creation.