workflow

name	workflow
description	Invoke a named recipe from WORKFLOWS.md by name. Each workflow is a defined skill chain with a verification step and rollback path. Use when the user types /workflow <name> or asks "run the X workflow" -- the skill reads WORKFLOWS.md, finds the matching recipe, and executes the steps in order with proper preconditions checked at each step. Pauses for explicit go-ahead before any gated-write step.

workflow

Recipe-runner. Reads <repo>/WORKFLOWS.md, finds the named workflow, walks the steps. Each step's preconditions are checked before invocation. Gated-write workflows pause for explicit go-ahead before the write phase.

When to invoke

Auto-invoke when:

• The user types /workflow <name> (e.g., /workflow verify-toolkit).
• The user says "run the X workflow" / "let's do the X recipe."

Do not invoke for:

• Single-skill requests — just run the skill directly.
• Workflows not yet in WORKFLOWS.md — propose adding it instead, or run the steps manually with /next-step after each.

What it does

1. Resolve the workflow. Read <repo>/WORKFLOWS.md; find the section matching the requested name (case-insensitive). If no match, list available workflows and ask which.

2. Pre-flight.

   • Check the workflow's "Safety mode" — if gated-write, ensure mendix-safety.md preconditions are achievable (clean tree, version >= 11.6, etc.).
   • Refuse and explain if any precondition fails.

3. Walk the skill chain. For each step:

   • Announce: "Step N of M: ".
   • Run the step (skill / command / read).
   • Check the step's verification before proceeding.
   • On failure: stop and report. Don't continue.

4. Pause before write phase. For gated-write workflows, after preconditions pass and BEFORE the actual write step, output:

   ## /workflow <name>: ready to write
   
   **Preconditions met:**
   - <list>
   
   **About to apply:** <what>
   **Risk:** <classification>
   **Rollback path:** <git tag name>
   
   **Proceed? (yes / show me the diff / abort)**
   

   Wait for explicit go-ahead.

5. Run the verification step at the end. Run the rollback path if verification fails.

6. Output:

## /workflow <name>: <PASS | FAIL | ABORTED>

**Steps run:** <list with status per step>
**Verification:** <result>
**Time elapsed:** <ms or s>

**Next:**
- (PASS) <suggested follow-up>
- (FAIL) <suggested fix path>

Hard rules

• Refuse on a workflow not in WORKFLOWS.md. Don't invent recipes; ask Neo to add it first.
• Pause for go-ahead before any gated-write step. No --auto-confirm mode. Neo's explicit yes is required for writes.
• Stop on first failure. Don't try to power through. /next-step after the report can suggest the fix.
• Cite the workflow definition. The output should reference WORKFLOWS.md so Neo can verify the recipe matches what's documented.

Built-in workflows (see WORKFLOWS.md for definitions)

• verify-toolkit — health check the entire stack (read-only).
• audit-page — read-only page audit against doctrine.
• clone-page — gated-write page clone via shadow-write (Skill 1 from PHASE-D-PLAN, build first).
• scaffold-microflow — gated-write microflow creation.
• add-entity — gated-write entity creation, highest risk.
• investigate-broken — read-only diagnostic flow.
• prep-for-handover — session-end state capture.

Cross-reference

• Recipes: <repo>/WORKFLOWS.md
• Orchestrator: <repo>/.claude/agents/mendix-orchestrator.md
• Safety: ~/.claude/rules/mendix-safety.md
• Companion: /start-here (orient), /next-step (what's next).