| 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.
Shared Workflow
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:
- Run
mfl agent update-self.
- Read
mfl status.
- Read
mfl thread status <id> --no-color.
- Read recent handoffs with
mfl handoff get -n 5.
Code Duties
-
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.
