dev-workflow

Plugin dev-workflow from marketplace mimas in Grade-AI-Labs/Mimas. Commands read from the repo's manifest — 9 days ago.

Skills (31)

• agentic-review

  Orchestrate repository-aware code review after `setup-agentic-repository` by deriving module specialists from `GLOSSARY-MAP.md` contexts or the `## Modules` list in `AGENTS.md`, applying `CODING_STANDARDS.md`, generating canonical review artifacts, running deterministic policy automation checks, del

• ask-matt

  Ask which skill or flow fits your situation. A router over the skills in this repo.

• code-review

  Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them s

• codebase-design

  Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

• diagnosing-bugs

  Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

• domain-modeling

  Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

• grill-me

  A relentless interview to sharpen a plan or design.

• grill-with-docs

  A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

• grilling

  Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

• handoff

  Compact the current conversation into a handoff document for another agent to pick up.

• implement-spec

  Implement the result of /to-spec and /to-tickets in code.

• implement

  Implement a piece of work based on a spec or set of tickets.

• improve-codebase-architecture

  Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

• orchestrate-spec

  Implement a spec and its tickets (the output of /to-spec and /to-tickets) as an orchestrator: tier each ticket, delegate to tiered worker agents across the ready frontier, adversarially review every result, and land it all on one integration branch.

• pr

  Use when writing a PR body.

• prototype

  Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

• research

  Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.

• retro

  Conduct a retrospective on a coding session.

• review-policy-builder

  Build and maintain project-specific review policy for `agentic-review` after `/setup-agentic-repository` by combining repository docs (`AGENTS.md`, `CODING_STANDARDS.md`, `GLOSSARY.md`/`GLOSSARY-MAP.md`, ADRs), repository-mined conventions, and structured user input, then writing machine-usable poli

• review-policy-rule-builder

  Creates or updates `agentic-review` policy rules, in a repo set up with `/setup-agentic-repository`, in `{docs-dir}/review/policies/global-policy.md` and `module-{slug}.md` using a structured interview and contract-safe merge behavior. Use when the user asks to add, modify, refine, deprecate, or cla

• setup-agentic-repository

  Configure this repo for the dev-workflow skills and scaffold its agent instructions: issue tracker, triage labels and domain doc layout (docs/agents/, GLOSSARY.md, docs/adr/), plus AGENTS.md, CODING_STANDARDS.md and the agent docs, all tailored to the repo's stack, git platform and conventions. Run

• tdd

  Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

• teach

  Teach the user a new skill or concept, within this workspace.

• to-questionnaire

  Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

• to-spec

  Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.

• to-tickets

  Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).

• triage

  Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

• wait-what

  Stop. That last message did not land: re-pitch it.

• wayfinder

  Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

• wizard

  Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can pe

• writing-for-agents

  Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

Subagents (8)

• explorer

  Dev-workflow explorer (Sonnet, medium effort). Reads the codebase and external docs a spec's tickets will need and writes notes outside the repo for implementers. Spawned only by the /orchestrate-spec orchestrator.

• merger

  Dev-workflow merger (Opus, medium effort). Merges one accepted worker branch into the integration branch, resolves conflicts that have one clear resolution, and runs the suite. Spawned only by the /orchestrate-spec orchestrator.

• reviewer

  Dev-workflow reviewer (Opus, high effort). Reviews a diff along one axis, Standards or Spec, as the code-review skill defines them, or one module or cross-cut scope as an agentic-review specialist. Read-only. Spawned by /orchestrate-spec and /agentic-review.

• tier-careful

  Dev-workflow implementer (Opus, high effort). Well-understood but delicate tickets: wide refactors, invariants to preserve, many edge cases. Spawned only by the /orchestrate-spec orchestrator.

• tier-fable

  Dev-workflow implementer (Fable, high effort). Very complex logic (subtle algorithms, concurrency, many interacting states) and bugs that survived a Heavy attempt. Spawned only by the /orchestrate-spec orchestrator.

• tier-heavy

  Dev-workflow implementer (Opus, xhigh effort). Unfamiliar or messy code, unclear root cause, non-obvious architecture; tickets where a wrong first approach is expensive. Spawned only by the /orchestrate-spec orchestrator.

• tier-light

  Dev-workflow implementer (Opus, low effort). Mechanical tickets: expand or contract steps, renames, config, boilerplate. Spawned only by the /orchestrate-spec orchestrator.

• tier-medium

  Dev-workflow implementer (Opus, medium effort). Standard tracer-bullet tickets with clear acceptance criteria in familiar code. Spawned only by the /orchestrate-spec orchestrator.

Similar plugins