Claude Skills by FrkAk

Use when the user wants to plan, decompose, track, or resume a multi-task project: scoping a new idea, importing or onboarding an existing repo or workspace, asking what to work on / what's next / what's blocked / where they left off, reporting task completion, dispatching work in parallel, or planning a draft task. Also when the user mentions Piyaz by name (e.g. "piyaz, do X") or references a task by its ref (e.g. VLT-9, KRN-153, PXD-31). Works for any project domain (code or data). Do not i...

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, h...

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.

Explicit doorway to the Mymir manage subagent. Use only when the user types /mymir:manage directly. For natural-language manage requests (strategic review, graph health audit, rebalancing, deep planning, housekeeping), the /mymir skill or the assistant dispatches the manage agent via the Task tool — do not invoke this skill for that path.

Use when the user wants to plan, decompose, track, or resume a multi-task project: scoping a new idea, importing or onboarding an existing repo or workspace, asking what to work on / what's next / what's blocked / where they left off, reporting task completion, dispatching work in parallel, or planning a draft task. Also when the user mentions Mymir by name (e.g. "mymir, do X") or references a task by its ref (e.g. MYMR-83, RZE-153, ORAS-42). Works for any project domain (code or data). Do no...

Explicit doorway to the Mymir onboarding subagent. Use only when the user types /mymir:onboarding directly. For natural-language onboarding requests (the user asks to import an existing repo into Mymir), the /mymir skill or the assistant dispatches the onboarding agent via the Task tool — do not invoke this skill for that path.

Dispatched after a task lands at `in_review` to produce a structured CTO-grade verdict on the work and its PR. Two invocation paths: composer Phase 4 (orchestrator dispatches after the implementer's `in_review` write, surfaces the verdict to HOTL, stops), and direct mode from the mymir skill on natural-language requests ("review MYMR-N", "review this PR", "review <PR URL>"). Reads `mymir_context depth='review'` for the implementationPlan rendered alongside executionRecord, plan-vs-files drift...