// Use when the user starts an interactive-mode request with `/meow-code`; implement the current MeowFlow plan and append a code handoff.
Heavy-ceremony orchestration for big work — research, planning, adversarial review, phased implementation, audit, delivery. Use when the user says "epic", "long task", "build this end to end", or wants a feature that runs all night.
Use when the user starts an interactive-mode request with `/meow-plan`; use mfl to update/discover the thread, launch a plan stage agent when needed, and create the matching proposal without editing production code.
Use when the user starts an interactive-mode request with `/meow-archive`; archive or delete the current MeowFlow thread and proposal.
Use when the user starts an interactive-mode request with `/meow-execute`; execute script, data, automation, or artifact work and append an execution handoff.
Use when the user starts an interactive-mode request with `/meow-flow` or `/mfl`; coordinate staged MeowFlow agents through mfl thread state, thread updates, mfl-run stage launches, and handoffs.
Use when the user starts an interactive-mode request with `/meow-review`; review current MeowFlow changes and append a review handoff.
| name | meow-code |
| description | Use when the user starts an interactive-mode request with `/meow-code`; implement the current MeowFlow plan and append a code handoff. |
Run the code stage for a MeowFlow thread.
Follow the core meow-flow workflow for thread discovery, worktree rules,
status checks, and handoffs before applying coder-specific behavior.
When running inside a stage agent:
mfl agent update-self.mfl status.mfl thread status <id> --no-color.mfl handoff get -n 5.Strip the /meow-code prefix. Treat remaining text as implementation
guidance.
Use the approved OpenSpec change, thread request body, and handoffs as the implementation source of truth.
Make concrete, focused repository changes in the current worktree.
Keep implementation minimal, maintainable, and aligned with repository style.
Run focused validation when practical. Use pnpm for package scripts in
TypeScript workspaces.
Before finishing, append a compact handoff:
mfl handoff append --stage code "changed X; validation Y passed; follow-up Z"
Finish with changed areas, validation results, remaining risks, and the next
suggested command, usually /mfl review.