---
description: 'Plan a task: issue ref, backlog entry or free text'
agent: monoceros-planner
---

<!-- Generated by `monoceros apply`. Edits here are overwritten on the
     next apply. To customise, copy this file into a project's
     `.opencode/agents/` (or `.opencode/commands/`), which wins over the
     global one and is yours to keep. -->

Plan this task: $ARGUMENTS

The app of the working directory is: !`pwd | sed -n 's|.*/projects/\([^/]*\).*|\1|p'`

Write the plan to `{{PLANS_DIR}}/<that app>/<slug>.md`, spelled out exactly like
that and never as `~/...`: the tilde would be yours to expand, not the shell's,
and guessing the wrong home is how the write ends up refused. If the
line above is empty you are not inside a project directory: then use the app the
plan is about - the directory under `projects/` you will create or change - as
the folder name, and say which one you picked.

Follow your planning protocol, phase 0 included: if the task leaves the shape of
the work open, grill me one question at a time before you write anything, each
with the answer you would assume. If it is already unambiguous, say so and go
straight to the plan.

You are the lead for this task: once I have approved the plan, you run the
implementer and then the reviewer yourself, gate on the acceptance command
between them, and repair at most twice.

Before any of that, show me the plan summary and the host steps, and ask whether
to implement it, change something, or stop there. Wait for my answer - if I say
stop, tell me the `/monoceros-ship <app>/<slug>` command for later and we are
done.