marcus-skills

Plugin marcus-skills from marketplace marcuskrogh in marcuskrogh/skills. Commands read from the repo's manifest — 11 days ago.

Skills (29)

• adopt

  Adopt the structure catalog across an existing codebase that was not built to it. Produces ADOPT.md: inventory plus a frontier behaviour map (tests, including startable frontend and backend). The adopt workflow then walks the unit chain until Done. Prefer /refine for a bounded area; prefer /restruct

• architect

  Architecture for one Task: record where the work sits (modules, layers, seams, dependency direction) in ARCHITECTURE.md. Depth follows the change. Use standalone, or when a delivery workflow reaches this step.

• bug

  Bug alignment and lightweight definition for a clear defect. Produces BUG.md and one tracker Task with a fix-fast binding. Prefer /define for new work (agent classifies as bug).

• define

  Definition front door for concrete work. Interviews the user (CONCEPT_ALIGNMENT) before classification and workflow binding. A short description starts the interview; it does not approve the plan. Produces PLAN.md (with Classification + Workflow), Sub-tasks, and the Task's delivery branch/PR. Prefer

• explain

  Explanation of the current workflow step, coding choices, interfaces, numerical considerations, or recent agent output, in simple terms. Long explanations are paced: one beat per turn, wait for advance. Prefer /help for which skill to run; prefer /guide for a step-by-step task walkthrough.

• explore

  Exploration through foggy or oversized work. Charts ROADMAP.md plus a Story of sequenced route Tasks (one delivery unit by default). Research, model, and sandbox artifacts stay on the delivery branch — no separate PRs. Use when the destination is felt but the route is not yet visible.

• guide

  Guidance through a manual task one step at a time: installation, setup, hardware, or coding the user wants walked. Present one step; wait for advance (yes, okay, move on) or a block that reevaluates the sequence. Prefer /define when the agent should deliver the work; prefer /explain when they want t

• harden

  Alias for restructure. Refactoring pass after testing. Prefer /restructure; /harden remains valid. Binding key stays harden.mode.

• help

  Help choosing skills and workflows. Summarises front doors (explore, define), how classification binds a workflow, and how Next walks delivery — without starting work. Use when asking which skill to run, how workflows relate, or for a navigation overview. Prefer /explain to teach a current step; pre

• implement

  Implementation through managed, value-routed work packages. Reuses the Task's delivery branch/PR when one exists, honors a Workflow binding when present, and enforces tests and structure as-you-go. Use standalone, for an approved definition spec, or for review fix-forward.

• iterate

  Iteration on already merged work. Produces ITERATE.md and a new Task and branch. Use when shipped work needs another fix cycle. When each turn needs visual, plot, or report inspection, the outcome is inspect-loop.

• jira

  Jira REST details for the tracker jira backend. Prefer the tracker skill and WORKSPACE.md provider selection. Not for user invocation.

• manage-skills

  Maintains the agent skills repository and install workflow. Use when creating a new skill, syncing skills locally, updating an existing project install to latest main (or a pinned ref), installing via agent-from-git or skills.sh / the optional Claude plugin, or asking how skills are distributed acro

• model

  Mathematical alignment through LaTeX-only questions. Produces MODEL.md finding docs on the delivery branch (no separate PR). Use for dynamical models, OCP, estimators, or applied math.

• refine

  Refine alignment and lightweight definition for a limited area that needs refactoring or descriptive improvement without changing behaviour. Produces REFINE.md and one tracker Task. Prefer /adopt for a whole tree; prefer /define for new work (agent classifies as refine).

• research

  Research across preprint, formal, web, and practitioner axes. Produces RESEARCH.md finding docs on the delivery branch (no separate PR). Use for surveys, state of the art, or a wide evidence pass.

• restructure

  Restructure: refactoring pass against the structure catalog (campground, names, size, cohesion, seams, named smells, CRAP). No behaviour change. Use standalone on a named area, or when a workflow's restructure step is current. Alias: /harden.

• review-fix

  Alias for review. Lasers, fix-forward, and code review on the delivery PR. Prefer /review; /review-fix remains valid.

• review

  Review of a change as sequential or bundled lasers across Spec, Correctness, Integration, Architecture, and Standards: find, fix, then publish a code review. Outcome CLEAN or FAILED. Use standalone, or when a workflow's review step is current. Alias: /review-fix.

• rework

  Rework alignment and lightweight definition for an intentional implementation change that must not degrade measured outcomes. Produces REWORK.md and one tracker Task with a parity-iterative binding. Prefer /define for new work (agent classifies as rework).

• sandbox

  Sandbox for isolated, representative inspect-loop development of a contained UI, method, or bench. Produces SANDBOX.md and a runnable isolation tree outside production paths so each iteration can be inspected (screenshot, plot, report) without shipping the product. Use standalone; as a bound workflo

• setup

  Workspace alignment at repository or global (user-level) scope: choose issue tracker (markdown, Jira, GitHub, or Linear), artifact location, and delivery conventions. Writes docs/agents/WORKSPACE.md, or ~/.agents/WORKSPACE.md for machine-wide defaults that apply to every repo without adding files to

• ship

  Shipping of all remaining work for a ready-to-build Task. Detects the stage, composes implementation, test, harden, and review-fix when needed, then merges the delivery PR and completes Done closeout. Use for ship, finish, or close-it-out cues.

• summarise

  Status summary for a pipeline Task or Story: purpose, track, stage, artifacts, and the next valid invoke. Use for status, where-am-I, or what-next questions.

• tracker

  Shared issue-tracker contract for pipeline skills. Resolves the provider from the effective workspace (repo docs/agents/WORKSPACE.md over global ~/.agents/WORKSPACE.md): markdown, jira, github, or linear. Not for user invocation — composed by explore, define, implement, review, ship, and setup.

• tweak

  Tweak alignment and lightweight definition for a small intentional change to existing behaviour. Produces TWEAK.md and one tracker Task with a delta-fast binding. Prefer /define for new work (agent classifies).

• workflow

  Workflow contract for pipeline continuity: one delivery branch/PR per Task, closed-loop ship, continuation keywords (next vs ship), and pointers to disclosed delivery/handoff/tracker/ship refs. Not for user invocation — composed by pipeline skills.

• workflows

  Workflow routing. Foggy → explore; concrete → define (alignment interview, then classify and bind). A short description starts that interview; it does not approve the plan. Finished skill replies end with the exact ## Next block. Honor Next/ship. Walkthroughs → guide; current-step teaching → explain

• writing-for-agents

  Writing skills and concepts for agents. Use when creating or editing a SKILL.md, CONCEPT_*.md, skill reference file, AGENTS.md, or CLAUDE.md in this repo — especially to prune duplication, sharpen terminology, apply the lean concept/skill shapes, or apply the human-cadence overlay.

Similar plugins