Universal

Plugin universal from marketplace making-good-software in kylehughes/agent-plugins-for-making-good-software. Commands read from the repo's manifest — 3 days ago.

Skills (11)

• graders
• brainstorming-design-specs

  Develop an implementation-ready design through research and dialogue. Use proactively when product scope, requirements, or engineering tradeoffs remain unresolved; skip specified changes ready to implement.

• compiling-agent-goals

  Compile specs, plans, or issues into bounded agent goal contracts with acceptance evidence and stopping conditions. Use proactively when preparing a persistent-agent handoff; this authors the contract, not the implementation.

• delivering-changes

  Carry a requested change through implementation, simplification, hardening, and required checks to a PR-ready handoff. Use proactively when the user delegates end-to-end delivery; preserve narrower requests and project checkpoints.

• designing-documents

  Organize substantive documents for understanding, decisions, action, and lookup. Use when creating, revising, or reviewing document structure, explanations, onboarding, or findability; preserve constrained edits and useful existing structures.

• hardening-changes

  Harden owned changes through scoped review and fixes. Use proactively when preparing a change set for a PR or when hardening is requested; read-only review belongs to reviewing-code.

• reviewing-code

  Review code for concrete correctness, security, concurrency, and compatibility defects. Load for every requested review, including a short function, diff, PR, branch, or repository audit. Keep review-only requests read-only.

• simplifying-code

  Simplify existing code while preserving behavior. Use proactively for requested cleanup, deduplication, local refactoring, or simplification review; preserve read-only review scope. Ordinary defect review belongs to reviewing-code.

• verifying-invariants

  Assess whether invalid domain values or states can be constructed, decoded, mutated into, or reached. Use proactively for invariant assessments or enforcement-boundary changes; choose bounded evidence. Skip ordinary output tests and async-test timing.

• writing-escalation-briefs

  Prepare a standalone expert brief with evidence a reader without repository access needs. Use proactively when debugging stalls or an escalation or expert handoff is requested; skip ordinary first-pass debugging and direct reviews.

• writing-technical-prose

  Write, edit, review, and normalize developer documentation, API comments, READMEs, design docs, runbooks, and PR descriptions. Use proactively for technical prose that needs accurate claims, clear structure, or consistent voice.

Subagents (4)

• code-reviewer

  Review structural design and architecture fit. Use PROACTIVELY when reviewing changes for pattern drift or misplaced responsibilities. Defer correctness defects, codified rules, and prose.

• code-simplifier

  Find behavior-preserving simplifications and reuse in any language. Use PROACTIVELY after changes that add complexity, duplication, or redundant state. Defer correctness and architecture review; report without editing.

• correctness-reviewer

  Review correctness, security, concurrency, compatibility, and performance defects. Use PROACTIVELY when assessing a diff, PR, or branch for merge readiness. Defer structural design, codified style, and prose.

• technical-writing-auditor

  Audit developer documentation for accuracy, reader usefulness, structure, and voice. Use PROACTIVELY after docs or API-comment changes. Defer architecture and code defects; report without editing.

Similar plugins