process plugins

by Mohit Aggarwal

Engineering craft & process discipline for working with coding agents: TDD Workflow, Bug Diagnosis, Refactoring Plan, Session Handoff, PR Description, and Code Review Guide. How to work, not just what to ship — the disciplines that keep AI-assisted code sane.

by Mohit Aggarwal

Process discipline for professional work — the difference between an agent that produces output and one that produces outcomes. Interview the requester before building, brainstorm divergent-then-convergent, write and execute real plans, verify before declaring done, orchestrate subagents, work incrementally, and simplify what you built.

by Mohit Aggarwal

Operations & procurement skills: Process Documentation, SOP Writer, Vendor Evaluation, RFP Writer, Vendor Contract Checklist, Project Status Report, Workshop Facilitation Guide. Document workflows, write audit-ready SOPs and RFPs, evaluate vendors and review their contracts, produce RAG status reports, and design facilitated workshops.

by Hunter D

Framework-agnostic design principles for design process, accessibility, iteration, and robustness against edge cases. Covers Accessibility, Iteration, Factor of Safety, Prototyping, Weakest Link, Scaling Fallacy, and Ockham's Razor.

by Jamie Nelson

Analyzes, improves, validates, and concisely represents processes and systems using a canonical semantic model and claim-level validation.

by Mingyang Bao

Unattended server & long-running task supervision — health checks, anomaly detection, auto-repair, multi-channel alerting. One YAML config per project, zero code changes to adopt.

by Ivan-WG

Solution-approach deliberation before non-trivial implementation: 2-3 structurally different approaches with trade-offs and a kill-trigger, a strategy catalog mapped to the risk each beats, a four-persona blind opinion round for refactor-shaped tasks — plus the merged pre-code disciplines: build-vs-buy checks, S/M/L/XL estimation, rollout planning, design-pattern selection, and /approaches:consult, a blind stronger-model second opinion when a session is stuck or about to do something irreversible (fresh-take merged in). Includes /approaches:compare, /approaches:opinions, /approaches:build-vs-buy, /approaches:size, /approaches:rollout, /approaches:pattern.

by Ivan-WG

Engineering process: plan-before-code, YAGNI, SOLID principles applied with judgment, task orchestration, work verification — held at Stop by candor's gate (clause 3, refusing a completion claim when files were edited but nothing ran afterward) when candor is installed; without it the rule is prose — low-cognitive-load code, KISS/DRY simplicity principles. Owns structure at both levels: code (units, interfaces, file placement) and system (service boundaries on data ownership, scaling paths, cache placement, sync vs async integration, domain modeling) via the system-design and domain-modeling skills and the system-architect worker.

by Ivan-WG

Systematic debugging: root cause before any fix — reproduce first, read the actual error, isolate with hypothesis tests and bisection, one change at a time, verify against the original symptom; escalation rule after three failed fixes. Ships a delegatable debugger agent for handing off the long reproduce-bisect investigation. Includes /debugging:debug.

by Ivan-WG

Git workflow discipline: isolated worktrees for feature work, a structured finish protocol for development branches (verify, present options, merge/PR/park, clean up), and review-exchange rigor — what to include when requesting review, and technical verification before implementing received feedback. Ships a PreToolUse guard that refuses any commit, merge, tag or PR carrying a Co-Authored-By: Claude trailer or a Generated-with-Claude-Code line. Includes /git-workflow:finish.

by Ivan-WG

Cross-session self-improvement loop: mines session and subagent transcripts for recurring friction and proposes CLAUDE.md rules, skill/plugin ideas, and defects against the plugin artifact that was running — applied only on approval.

by Ivan-WG

Prices every output as a debit and asks how much. Five surfaces, one bar each: code, tests, comments, files, and actions — a tool call, subagent spawn or verify pass whose result cannot change the next step is a paid no-op, and nothing else here prices that. Only four things buy more than the minimum: blast radius, an observed defect, a stated criterion, the user asking; the excess must name which, where it happens. Minimum means risk coverage, not count — never delete a test to hit a ratio.

by Ivan-WG

Subagent orchestration discipline: delegation contracts (self-contained prompts, compressed evidence-backed returns, model/effort tiering, scout-then-fanout, writer isolation), verification panels (refuter voting, judge panels, loop-until-dry, completeness critic), plus the shared contract review commands route their fix lists through. Includes /orchestration:review.

by Ivan-WG

Meta-bundle: the engineering-process category in one install — git workflow, approach deliberation (build-vs-buy, estimation, rollout, pattern selection folded in), hindsight mining, docs discipline (api-design), subagent orchestration, task execution, stack scanning, plugin scouting, a token-cost warn hook (lean), file-aware skill auto-routing (skill-router), a stronger-model second opinion when stuck (fresh-take), a refuting research harness (ultra-deep-research), and a committed codebase map (brain). Uninstall cleanly with /process-suite:uninstall — removes the bundle and prunes its auto-installed plugins. 200k-window installs: see the README's context-window requirement first.

by Ivan-WG

System-level design: service boundaries on data ownership, scaling paths, cache placement, sync vs async integration and its failure modes, single points of failure, plus domain modeling (bounded contexts, aggregates, ubiquitous language) and an event-driven skill (delivery semantics, outbox, sagas, DLQ) — firing system-design, domain-modeling, and event-driven skills, a /system-design:review command, and a system-architect worker + system-design-reviewer pair. Complements code-architecture (code-level structure) without overlapping it.

by Ivan-WG

Disciplined task execution: one task at a time, scope locked to the task, bounded verify-fix inner loop per task, no drift, no unbounded outer loop. Completion means every check passed with evidence — held at Stop by candor's gate (clause 4) when candor is installed; without it a run can end by narration. Ships the shared task-executor agent — the delegatable 'apply the fixes' sink every review routes to — a PostToolUse scope-lock tripwire, parallel-planning (/task-runner:plan), and the subagent discipline (the orchestration plugin was merged in on 2026-09-14): delegation contracts, verification panels, scripts/dispatch-lint.sh, and the ultra-assess boost hook.

by Ivan-WG

Idea-to-execution clarification: brainstorm fuzzy ideas into approved designs, grill requirements until zero ambiguity, deliberate the implementation approach with a blind four-persona round (via the approaches plugin when installed; inline 2-3 approaches otherwise), decide visual choices with mockups, validate whole experiences with an interactive clickable demo, then emit milestone-grouped single-prompt task cards. Outputs live under taskmaster-docs/ (no collision with a project's own docs/).

by Ivan-WG

Meta-bundle: the whole idea-to-shipped pipeline in one install — the core-suite baseline (candor, code-review, git-workflow, hindsight, secret-scanning, skill-router, stack-scan) plus taskmaster clarification and cards, task-runner execution with delegation contracts, approaches deliberation, code-architecture plan-before-code and verification, testing, debugging, and the ui-ux and security lanes the cards dispatch into. Replaces taskmaster-suite, process-suite and quality-principles-suite (2026-09-14). Fifteen members: over the host's 200k skill-listing floor by design — the README names the settings line. Uninstall cleanly with /workflow-suite:uninstall.

by chamaya00

Agent roles, house rules, and repo provisioning commands for turning objectives into shipped code.

by Travis James

KBD process orchestration, portable agent teams, strategic evolution, goal tracking, outer loop, elicit, and PMPO skill creation

by Chetan Verma

An agent-first development process — BRD, identifier registry, dependency-ordered slice queue, CI gate, coverage ledger, and sixteen tuned project skills. /writ:solo for one developer plus agents on a new project, /writ:team for several, /writ:adopt to survey an existing codebase and put the process around it without blocking anyone who has not agreed to it, /writ:update to offer an existing writ project what the kit has gained since, and /writ:contribute to offer writ back what a project built.