Plugin Claude Code
Plugin marketplace listing 3 plugins: personal-plugin, bpmn-plugin, slide-gen.
Plugin Claude Code
Plugin marketplace listing 3 plugins: personal-plugin, bpmn-plugin, slide-gen.
Agent Claude Code
Executes deterministic, low-ambiguity implementation tasks. Best for renames, format conversions, regex edits, boilerplate from a clear spec, classification, simple lookups, and summarizing small chunks. Return ESCALATE:[reason] if the task requires architectural judgment or spans multiple files with non-obvious…
Agent Claude Code
Executes judgment-heavy implementation tasks. Best for architectural choices, multi-file refactors with system-wide coupling not anticipated in the plan, ambiguous requirements, cross-cutting debugging, and design synthesis. This is the highest tier — there is no escalation above Opus. Accept the task and produce your…
Agent Claude Code
Executes standard software engineering tasks. Best for writing tests against a spec, single-file refactors, documentation updates, straightforward bug fixes, and most code review. Return ESCALATE:[reason] if the task requires architectural judgment, multi-file refactoring with system-wide coupling, or deeply ambiguous…
Instructions file
Instructions for davistroy/claude-marketplace, covering learning capture — every session, verified operational rules, claude.md, project overview and marketplace installation.
Command
Reads a meeting transcript and produces a structured report with key discussion points, action items, decisions, and risks. Good output captures all explicit action items and decisions from the transcript without fabricating details.
Command
Runs one domain agent from the architecture review team against a target codebase, without running the full 9-agent /arch-review suite. Good output: a single findings/ .md (plus its .meta.json) written for the requested domain, using an existing intake.md when present, without touching any other domain's findings.
Command
Re-synthesizes the executive summary from existing domain findings, without re-running any domain agent. Used after manually editing findings, re-running a single agent via /arch-review-single, or resolving cross-domain conflicts offline. Good output: a fresh reports/executive-summary.md built only from findings files…
Command
Reads a questions JSON file (produced by /define-questions) and conducts a single-question-at-a-time interactive Q&A session. Each question is presented individually; the user's answer is recorded and the session proceeds to the next question. Good behavior: one question at a time, patient waiting, no skipping ahead.
Command
Reads a document and produces a scored quality assessment report across six dimensions (completeness, clarity, consistency, specificity, structure, feasibility). Good output is a saved markdown or JSON file with dimensional scores, categorized issues (CRITICAL/WARNING/SUGGESTION), and actionable recommendations.
Command
Increments the version number in a plugin's plugin.json and marketplace.json files and adds a CHANGELOG placeholder entry. Good behavior: updates both files atomically with the correct semantic version bump and does not touch other files.
Command
Performs repository cleanup: removes stale files, organizes structure, refreshes documentation. This is a potentially destructive command. Evals should be run in a throwaway clone.
Command
Reads multiple document variants covering the same topic and synthesizes a single, superior consolidated document that captures the best elements from each. Good output: a single document that is more complete than either input alone, clearly resolves contradictions, and attributes key points when appropriate.
Command
Converts a markdown file to a nicely formatted Microsoft Word document (.docx). Good output: a .docx file that preserves all headings, tables, bullet lists, and code blocks from the source markdown.
Command
Generates a detailed IMPLEMENTATIONPLAN.md from requirements documents (BRD, PRD, TDD, design specs). Good output: a machine-readable plan with phases, work items, sizing estimates, acceptance criteria, and status markers — following the standard schema used by /implement-plan.
Command
Analyzes a document and extracts all open questions, TBDs, ambiguities, and gaps into a structured JSON file. Good output: a valid JSON file compatible with the questions schema, containing every actionable open item from the document.
Command
Generates a detailed image generation prompt from a document or content description. Good output: a prompt that is specific, visual, non-abstract, includes style/composition/lighting guidance, and is calibrated to the specified dimensions and style options.
Command
Full pipeline: extracts questions from a document (like /define-questions), walks through answering them interactively (like /ask-questions), then updates the document with the answers. Good behavior: the source document is updated in place with answers incorporated, and TBD/open question markers are resolved.
Command
Executes an IMPLEMENTATIONPLAN.md using orchestrated subagents. Each work item is implemented, tested, and committed by a dedicated subagent. Good behavior: items are implemented in order, status markers are updated, tests pass, and a PR is created at the end.
Command
Generates a new skill file with proper nested directory structure and required frontmatter. Good output: a skills/ /SKILL.md file with name and description in frontmatter, proactive trigger conditions, and the correct nested structure.
Command
Analyzes a codebase and generates a prioritized IMPLEMENTATIONPLAN.md with improvement recommendations. Unlike /create-plan (requirements-driven), this is codebase-driven. Good output: a plan that reflects actual issues in the code, not generic advice.
Command
Analyzes the current repository state (git status, recent commits, open issues, existing plans) and recommends the next logical action. Good output: a specific, actionable recommendation grounded in the actual repo state — not a generic "add tests" suggestion.
Command
Sanitizes a document by removing or replacing company identifiers, employee names, internal URLs, and proprietary tool names while preserving the document's meaning and utility. Good output: a sanitized version where specific identifiers are replaced with generic equivalents and no original identifiers remain.
Command
Read-only architectural audit of the current project. Produces an in-conversation scorecard across 6 dimensions with findings and a remediation roadmap. Good output: specific findings with file references, calibrated scores, and concrete remediation suggestions — not generic advice.