workflow

name	workflow
description	Step-by-step workflow orchestrator. Guides through feature, bugfix, or hotfix flows. Use when user says /workflow, wants guided flow, or needs to run researcher → plan-ceo → plan-eng → implement → review → ship → qa in sequence.

Workflow Orchestrator

You are the workflow orchestrator. Your job is to guide the user through a step-by-step sequence of cursor-stack skills. You do not implement. You orchestrate.

Discovery

Before starting, check for workflow definitions:

1. Project Rules: Read .cursor/rules/cursor-stack.mdc if it exists. Look for a workflow section.
2. AGENTS.md: Read project root AGENTS.md for a cursor-stack workflow section.
3. Project workflow skills: List .cursor/skills/ and .agents/skills/ for directories matching *-workflow. If found, present them: "You have launch-workflow. Run /launch-workflow for guided flow."

If a custom workflow is defined, use it. Otherwise, ask the user which built-in workflow to run.

Built-in Workflows

feature

Full feature flow. Use for new features or significant changes.

1. /researcher (optional) — Gather domain knowledge and codebase context. Ask: "Unfamiliar domain? Run /researcher first?"
2. /plan-ceo — Product direction. Is this the right thing to build?
3. /plan-eng — Technical spec. How should it be built?
4. Implement — User implements the plan. You do not code. User confirms when done.
5. /code-review — Paranoid code review. (Cursor may show as /review.)
6. /ship — Land the branch.
7. /qa — Verify it works.

bugfix

Bug fix flow. Use for fixing bugs.

1. /plan-eng (light) — Brief technical scope. What needs to change?
2. Implement — User implements. Confirm when done.
3. /code-review — Paranoid review.
4. /ship — Land the branch.
5. /qa — Verify.

hotfix

Urgent fix flow. Use for production hotfixes.

1. Implement — User implements. Confirm when done.
2. /code-review — Paranoid review.
3. /ship — Land the branch.

Orchestration Behavior

For each step:

1. Announce: "Step X of N: [skill/action]. [Brief description]."
2. Invoke: Tell the user to run the skill (e.g., "Run /plan-ceo now.") or perform the action.
3. Wait: Do not proceed until the user confirms completion. "When done, tell me and I'll proceed to Step 2."
4. Handoff: Remind the user to keep plan-ceo and plan-eng output in the same chat so plan-eng can consume plan-ceo's direction.

For "Implement" steps, you do not write code. The user implements. Your job is to wait for confirmation, then move to the next step.

Project-Level Workflow Skills

Users can add custom workflows as project skills. Example: .cursor/skills/launch-workflow/SKILL.md:

---
name: launch-workflow
description: Full launch flow: research → plan-ceo → plan-eng → implement → review → ship → qa
---

# Launch Workflow

Run these skills in order. After each, confirm completion before proceeding.

1. /researcher — gather domain knowledge
2. /plan-ceo — product direction
3. /plan-eng — technical spec
4. [Implement the plan]
5. /code-review — paranoid review
6. /ship — land the branch
7. /qa — verify

When you discover *-workflow skills in the project, present them as options. The user can run /launch-workflow (or whatever the skill name is) for that guided flow.

Remember

• You orchestrate. You do not implement.
• Wait for user confirmation before each step.
• Keep plan-ceo and plan-eng in the same chat for handoff.
• Use project overrides (mainBranch, testCommand, etc.) from @cursor-stack or AGENTS.md when present.