mymir

Use when the user has a net-new software project idea that needs shaping into a brief before tasks can be created. Triggers: "I want to build...", "I'm thinking about an app for...", "let's plan a project", vague or exploratory phrasing, ambiguous scope. Do not use when an existing repo is present (route to onboarding), a Mymir project already exists with a description, or the user has a complete spec ready (route to decompose).

Phase 3 of the /mymir:composer pipeline. Dispatched per task by the composer orchestrator after the planner has saved the implementationPlan to Mymir. Reads the plan, implements it on a feature branch with production-grade quality (security, performance, reliability, observability), runs the project's tests / typecheck / lint until green, opens a pull request using the project's PR template with the [<taskRef>] bracket form on the title, and marks the task in_review in dispatched mode per the Completion Protocol (executionRecord, decisions, files, evaluated acceptance criteria); the HOTL operator finalizes in_review → done after PR approval. Does not refine or replan. If the plan is broken, fails loudly back to the orchestrator. Invoked automatically by the composer skill; safe to call directly when the user asks "implement <taskRef> per the saved plan" outside the composer loop.

Phase 2 of the /mymir:composer pipeline. Dispatched per task by the composer orchestrator after the researcher returns. Takes the research brief plus the target task's planning context, writes the unabridged implementationPlan to Mymir, and transitions the task draft → planned in the same update. Applies refinements the researcher proposed (acceptance criteria rewrites, description tightening, tag adjustments) via append-only updates. Returns a one-sentence confirmation. Does not edit code, run tests, or open PRs. Invoked automatically by the composer skill; safe to call directly when the user asks "plan <taskRef> from the research brief" outside the composer loop.

Phase 1 of the /mymir:composer pipeline. Dispatched per task by the composer orchestrator to gather grounded context before planning. Reads the target task at multiple Mymir context depths, searches up-to-date library docs via context7, explores the codebase for files and patterns the implementer will touch, surfaces the project's house conventions (commit format, test/lint/typecheck commands, PR template), and reasons about security, performance, and reliability standards the work must meet. Returns one research brief; does not write to Mymir, the repo, or any external system. Invoked automatically by the composer skill; safe to call directly when the user asks "research task <taskRef>" or "investigate <taskRef> before planning" outside the composer loop.

Use when the user wants to add a new feature, capability, or cluster of work to an existing active Mymir project. Triggers: "add a feature for notifications", "decompose this idea into tasks", "I want to plan out the X subsystem", "extend the project with Y", "add Z to the project". Reuses the project's existing categories and tag vocabulary; creates 5 to 20 tasks plus internal edges and edges to existing project tasks. Does NOT change project status. Do NOT use for greenfield project decomposition (route to mymir:decompose), for splitting an existing oversize task (route to mymir:decompose-task), or for refining a single task (route to the mymir skill directly).

Explicit doorway to the Mymir brainstorm subagent. Use only when the user types /mymir:brainstorm directly. For natural-language brainstorm requests (the user describes a net-new project idea), the /mymir skill or the assistant dispatches the brainstorm agent via the Task tool — do not invoke this skill for that path.

Use when the user types /mymir:composer or /mymir:composer <taskRef>, or asks composer to "run the next task", "ship the backlog", "compose through my ready queue", "loop through mymir tasks", or otherwise requests end-to-end Mymir task delivery (research → plan → implement → propagate, then pick the next task and repeat). Composer dispatches one fresh subagent per phase per task so each phase runs with a clean context window and a focused tool set; the orchestrator itself only picks tasks, hands off, and propagates. Do NOT invoke for one-off task lookups, status checks, refinement of one task by hand, or planning a single task interactively. Those flows belong to the mymir skill and using composer for them adds latency without adding quality.

Explicit doorway to the Mymir decompose-feature subagent. Use only when the user types /mymir:decompose-feature directly. For natural-language requests to add a new feature or capability cluster to an active project, the /mymir skill or the assistant dispatches the decompose-feature agent via the Task tool. Do not invoke this skill for that path.

Explicit doorway to the Mymir decompose-task subagent. Use only when the user types /mymir:decompose-task directly. For natural-language requests to split an existing oversize task (the user says "split this task" or composer's oversize handler routes here), the /mymir skill or the assistant dispatches the decompose-task agent via the Task tool. Do not invoke this skill for that path.

Explicit doorway to the Mymir decompose subagent. Use only when the user types /mymir:decompose directly. For natural-language decompose requests (the user asks to break a project description into tasks), the /mymir skill or the assistant dispatches the decompose agent via the Task tool — do not invoke this skill for that path.