all publishers

garyld1962

@garyld1962 source repo

246 published skills · page 1 of 3

  1. ▌
    Humanizer 2 · garyld1962 bundle
    Rewrite AI-sounding text so it reads naturally without changing what it says. Use when editing or reviewing prose for inflated claims, sales language, vague sources, repetitive structure, stock AI words, passive voice, filler, or chatbot artifacts. Based on Wikipedia's "Signs of AI writing."
    0 repo stars
  2. ▌
    Review Adversarial 2 · garyld1962 bundle
    Cross-model adversarial code review via Codex/Gemini. Use for high-stakes diffs (auth, payments, migrations) or diffs over 200 lines after domain-review passes.
    0 repo stars
  3. ▌
    Checkpoint 3 · garyld1962 bundle
    Quality gate for changed scope. Discovers package tooling, then runs lint, typecheck/build, tests, and a quick security-oriented diff review before push or PR.
    0 repo stars
  4. ▌
    Code Investigate 2 · garyld1962 bundle
    Search one or more repos for a code pattern or behavior and produce a versioned Markdown investigation report. Supports literal, regex, and semantic (behavioral) search across multi-repo scope.
    0 repo stars
  5. ▌
    Repo Delivery 2 · garyld1962
    Declarative schema every repo must satisfy so execute-plan, checkpoint, and review-adversarial don't have to guess. Not user-invokable.
    0 repo stars
  6. ▌
    Domain Review 2 · garyld1962 bundle
    Domain-based PR review controller (formerly code-review). Preferred over the built-in /code-review when you need the 11-domain controller/worker review with per-domain findings; use the built-in for a fast single-pass diff review or the ultra cloud review. Supports two profiles: 'breakpoint' (light mid-flow review covering security, correctness, and tests only) and 'full' (comprehensive PR-boundary review covering all 11 domains). Conditional domains fire only when triggers match: data-integrity fires when the diff touches persistence (migrations, schemas, SQL, repositories, ORM models); api-contract fires when the diff touches a public surface (API routes, controllers, handlers, .proto files, OpenAPI/Swagger specs, library surface, message schema, CLI, or SDK). Do NOT use for trivial changes (typo fixes, mechanical refactors, dependency bumps with no logic changes). Do NOT use for reviewing a GitHub PR by number where a standard pass suffices — the built-in /review handles that. Do NOT use when you want prof
    0 repo stars
  7. ▌
    Validate Plan 2 · garyld1962 bundle
    Lightweight readiness gate for a plan file: checks structure, task discreteness, acceptance criteria, milestones, and forbidden placeholders.
    0 repo stars
  8. ▌
    Configure 3 · garyld1962
    Resolve missing configuration for Copilot workflows, including execution environment and an Obsidian vault. Use when a workflow preflight reports missing fields; preserve existing user-owned settings.
    0 repo stars
  9. ▌
    Execute Plan 2 · garyld1962 bundle
    Use when the user has a written implementation plan file (typically produced by /execute-prd, in the plan-format contract) and wants it executed — phrases like 'execute the plan', 'run docs/plans/X.md', 'resume the plan'. Not for writing plans (use /execute-prd) or trivial single-file edits.
    0 repo stars
  10. ▌
    Execute Prd 2 · garyld1962
    Use when a written requirements source exists (PRD, RFC, prompt.md, spec file, or ADO/Linear ticket) and the user wants it planned and built — phrases like 'build this PRD', 'execute prompt.md', 'turn this RFC into a plan and run it'. Not for vague ideas (use superpowers:brainstorming) or when a validated plan already exists (use /execute-plan).
    0 repo stars
  11. ▌
    Code Investigate · garyld1962 bundle
    Search one or more repos for a code pattern or behavior and produce a versioned Markdown investigation report. Supports literal, regex, and semantic (behavioral) search across multi-repo scope.
    0 repo stars
  12. ▌
    Prd Create 2 · garyld1962 bundle
    Create a PRD, ONTOLOGY.md and AERS from an idea, goal, thesis or codebase via interview. Modes: greenfield, feature, refresh, rewrite. Not for an existing artifact (use /prd-validate).
    0 repo stars
  13. ▌
    Dep Migrate 2 · garyld1962
    Plan a dependency migration: analyze breaking changes, assess impact on your codebase, produce a step-by-step migration plan. Use when upgrading Node, TypeScript, frameworks, or major dependencies.
    0 repo stars
  14. ▌
    Validate Plan · garyld1962 bundle
    Lightweight readiness gate for a plan file: checks structure, task discreteness, acceptance criteria, milestones, and forbidden placeholders.
    0 repo stars
  15. ▌
    Dep Audit 2 · garyld1962
    Audit project dependencies: check for vulnerabilities, outdated packages, unused deps, and license compliance. Use periodically or before releases.
    0 repo stars
  16. ▌
    Checkpoint 2 · garyld1962
    Quality gate: discovers project tooling, runs linter, typecheck/build, and tests for changed packages. Use before pushing or creating PRs.
    0 repo stars
  17. ▌
    Execute Plan · garyld1962 bundle
    Use when the user has a written implementation plan file (typically produced by /execute-prd, in the plan-format contract) and wants it executed — phrases like 'execute the plan', 'run docs/plans/X.md', 'resume the plan'. Not for writing plans (use /execute-prd) or trivial single-file edits.
    0 repo stars
  18. ▌
    Domain Review · garyld1962 bundle
    Domain-based PR review controller (formerly code-review). Preferred over the built-in /code-review when you need the 11-domain controller/worker review with per-domain findings; use the built-in for a fast single-pass diff review or the ultra cloud review. Supports two profiles: 'breakpoint' (light mid-flow review covering security, correctness, and tests only) and 'full' (comprehensive PR-boundary review covering all 11 domains). Conditional domains fire only when triggers match: data-integrity fires when the diff touches persistence (migrations, schemas, SQL, repositories, ORM models); api-contract fires when the diff touches a public surface (API routes, controllers, handlers, .proto files, OpenAPI/Swagger specs, library surface, message schema, CLI, or SDK). Do NOT use for trivial changes (typo fixes, mechanical refactors, dependency bumps with no logic changes). Do NOT use for reviewing a GitHub PR by number where a standard pass suffices — the built-in /review handles that. Do NOT use when you want prof
    0 repo stars
  19. ▌
    Triage 2 · garyld1962
    Investigate a bug from reproduction through root cause analysis and produce a structured triage report (classification, risk, recommended next step) — the deliverable is the report, not a fix. Preferred over superpowers:systematic-debugging when the goal is a handoff document for /hotfix, /execute-prd, or a human decision rather than an in-session fix.
    0 repo stars
  20. ▌
    Kickoff 2 · garyld1962
    Use for operator-supervised feature work from a PRD/story/AERS: readiness → plan → implement → review, with the operator at the keyboard. Does not produce audit-grade governed artifacts; for an unattended run use /execute-prd.
    0 repo stars
  21. ▌
    Drawio 2 · garyld1962 bundle
    Generate native .drawio diagram files (flowcharts, ER, sequence, class, architecture diagrams) as draw.io XML, with optional export to PNG/SVG/PDF or a browser URL that opens in app.diagrams.net. No MCP setup required. Triggers on '/drawio', 'create a diagram', 'draw.io', 'flowchart', 'sequence/ER/class diagram'. When NOT to use: for Azure resource-group / cloud-architecture diagrams, use create-diagram instead.
    0 repo stars
  22. ▌
    Hotfix 2 · garyld1962
    Apply an expedited fix for a critical production issue: branch from main, apply a scoped fix, run targeted tests, and fast-track merge.
    0 repo stars
  23. ▌
    Ideate 2 · garyld1962
    Use before superpowers:writing-plans or brainstorming to shape a rough ask, doc, or folder into a direction. Three modes: idea (general), ba (business-analysis), tech (technical options).
    0 repo stars
  24. ▌
    Dep Migrate · garyld1962
    Plan a dependency migration: analyze breaking changes, assess impact on your codebase, produce a step-by-step migration plan. Use when upgrading Node, TypeScript, frameworks, or major dependencies.
    0 repo stars
  25. ▌
    Prd Create · garyld1962 bundle
    Create a PRD, ONTOLOGY.md and AERS from an idea, goal, thesis or codebase via interview. Modes: greenfield, feature, refresh, rewrite. Not for an existing artifact (use /prd-validate).
    0 repo stars
  26. ▌
    Kickoff · garyld1962
    Use for operator-supervised feature work from a PRD/story/AERS: readiness → plan → implement → review, with the operator at the keyboard. Does not produce audit-grade governed artifacts; for an unattended run use /execute-prd.
    0 repo stars
  27. ▌
    Dep Audit · garyld1962
    Audit project dependencies: check for vulnerabilities, outdated packages, unused deps, and license compliance. Use periodically or before releases.
    0 repo stars
  28. ▌
    Checkpoint · garyld1962
    Quality gate: discovers project tooling, runs linter, typecheck/build, and tests for changed packages. Use before pushing or creating PRs.
    0 repo stars
  29. ▌
    Drawio · garyld1962 bundle
    Generate native .drawio diagram files (flowcharts, ER, sequence, class, architecture diagrams) as draw.io XML, with optional export to PNG/SVG/PDF or a browser URL that opens in app.diagrams.net. No MCP setup required. Triggers on '/drawio', 'create a diagram', 'draw.io', 'flowchart', 'sequence/ER/class diagram'. When NOT to use: for Azure resource-group / cloud-architecture diagrams, use create-diagram instead.
    0 repo stars
  30. ▌
    Hotfix · garyld1962
    Apply an expedited fix for a critical production issue: branch from main, apply a scoped fix, run targeted tests, and fast-track merge.
    0 repo stars
  31. ▌
    Ideate · garyld1962
    Use before superpowers:writing-plans or brainstorming to shape a rough ask, doc, or folder into a direction. Three modes: idea (general), ba (business-analysis), tech (technical options).
    0 repo stars
  32. ▌
    Triage · garyld1962
    Investigate a bug from reproduction through root cause analysis and produce a structured triage report (classification, risk, recommended next step) — the deliverable is the report, not a fix. Preferred over superpowers:systematic-debugging when the goal is a handoff document for /hotfix, /execute-prd, or a human decision rather than an in-session fix.
    0 repo stars
  33. ▌
    Jev Gate · garyld1962
    Local System-1 Jev-class decision-model control plane (vllm-sr/Decision-1.0-Nox-4B or jaredpalmer/kev-4b on local RTX 5090 /v1/systemone via FastMCP jev-gate). Defines the 4 core contracts: cascading configuration, smart_search, triage_coding_task, and verify_code_invariants + gate_shell_command. Not user-invokable.
    0 repo stars
  34. ▌
    Humanizer · garyld1962 bundle
    Rewrite AI-sounding text so it reads naturally without changing what it says. Use when editing or reviewing prose for inflated claims, sales language, vague sources, repetitive structure, stock AI words, passive voice, filler, or chatbot artifacts. Based on Wikipedia's "Signs of AI writing."
    0 repo stars
  35. ▌
    Drawio 5 · garyld1962
    Draw.io Skill for Claude Code
    0 repo stars
  36. ▌
    Test Writer 3 · garyld1962
    Test file generator — converts TestSpecification objects into valid Vitest .test.ts files with it.todo() stubs.
    0 repo stars
  37. ▌
    State Lifecycle 3 · garyld1962
    State machine analyst — tests every valid transition, rejects every invalid one, verifies side effects of status changes.
    0 repo stars
  38. ▌
    Boundary Validation 3 · garyld1962
    Input validation analyst — tests required field enforcement, Zod constraint boundaries, NOT_FOUND handling, error code specificity, soft-delete behavior.
    0 repo stars
  39. ▌
    Contract Compliance 3 · garyld1962
    Requirements analyst — decomposes task description into testable requirements. Maps Zod schema fields to assertions. Verifies CRUD completeness and return type coverage.
    0 repo stars
  40. ▌
    Integration Surface 3 · garyld1962
    Integration analyst — tests router-to-service wiring, Zod schema binding, query vs mutation assignment, auth requirements, and cross-boundary contracts.
    0 repo stars
  41. ▌
    Prd Acceptance 4 · garyld1962 bundle
    Verify delivered behavior against PRD/AERS criteria with a per-criterion evidence scorecard. Use for acceptance validation, not implementation or a general code-quality review.
    0 repo stars
  42. ▌
    Parallel Optimization 4 · garyld1962 bundle
    Optimize a draft task graph's dependencies and file ownership for safe optional concurrency. Use before execution when scheduling needs work; do not change requirements or create a second lane/wave plan.
    0 repo stars
  43. ▌
    State Lifecycle 4 · garyld1962
    State machine analyst — tests every valid transition, rejects every invalid one, verifies side effects of status changes.
    0 repo stars
  44. ▌
    Boundary Validation 4 · garyld1962
    Input validation analyst — tests required field enforcement, Zod constraint boundaries, NOT_FOUND handling, error code specificity, soft-delete behavior.
    0 repo stars
  45. ▌
    Contract Compliance 4 · garyld1962
    Requirements analyst — decomposes task description into testable requirements. Maps Zod schema fields to assertions. Verifies CRUD completeness and return type coverage.
    0 repo stars
  46. ▌
    Integration Surface 4 · garyld1962
    Integration analyst — tests router-to-service wiring, Zod schema binding, query vs mutation assignment, auth requirements, and cross-boundary contracts.
    0 repo stars
  47. ▌
    Process Tune 3 · garyld1962 bundle
    Read accumulated postmortems or run evidence, group repeated workflow failures, and propose concrete edits to skills, rubrics, templates, or rules.
    0 repo stars
  48. ▌
    Feature Sweep 4 · garyld1962 bundle
    Audit installed skills against verified current platform releases and propose or apply targeted improvements. Use after a Codex or Copilot release, or to find useful new integrations; use a skill quality audit for ordinary wording and trigger problems.
    0 repo stars
  49. ▌
    Validate Plan 6 · garyld1962 bundle
    Validate a task graph plan's YAML, dependencies, write ownership and acceptance before execution, then review semantic readiness. Use for plan checks; do not execute or rewrite the plan unless requested.
    0 repo stars
  50. ▌
    Audit Existing 3 · garyld1962 bundle
    Read-only audit of an existing implementation before planning or extending it. Produces implemented, missing, duplicated, broken, and risky findings without editing files.
    0 repo stars
  51. ▌
    Refactor Brief 4 · garyld1962 bundle
    Investigate a refactoring problem and produce an RFC with preserved behavior, interface decisions, characterization tests and small working commits. Use for refactor planning or an issue brief, not for applying a refactor that is already specified.
    0 repo stars
  52. ▌
    Review Gauntlet 3 · garyld1962 bundle
    Meta-review of an existing code review. Tests whether review findings are accurate, actionable, complete, and severity-calibrated.
    0 repo stars
  53. ▌
    Code Investigate 3 · garyld1962 bundle
    Evidence-backed code investigation across one or more repos. Use for durable reports about where behavior lives, how a pattern is implemented, or whether a behavior exists.
    0 repo stars
  54. ▌
    What Is It About 3 · garyld1962 bundle
    Find the central thesis of a video, article, talk, or content idea, then produce an outline where every segment serves that thesis.
    0 repo stars
  55. ▌
    Review Adversarial 4 · garyld1962 bundle
    High-stakes adversarial code review after normal review. Challenges assumptions with distinct reviewer lenses and optional configured external model/CLI reviewers.
    0 repo stars
  56. ▌
    Ubiquitous Language 3 · garyld1962 bundle
    Build or refresh a domain glossary from interviews, specs, code, and docs. Flags ambiguous terms and writes UBIQUITOUS_LANGUAGE.md when asked.
    0 repo stars
  57. ▌
    Spec Review Adversarial 3 · garyld1962 bundle
    Adversarially review PRDs, stories, requirements, acceptance criteria, or AERS drafts for ambiguity, contradiction, unverifiability, and scope traps.
    0 repo stars
  58. ▌
    Code Review Professional 3 · garyld1962 bundle
    Seniority-calibrated craft review after a normal code review. Grades code quality across maintainability, clarity, design, tests, operability, and professional judgment.
    0 repo stars
  59. ▌
    Pr 3 · garyld1962
    Full PR lifecycle: branch, commit, checkpoint, push, create PR, and optionally squash-merge. Automates the entire pull request workflow with quality gates.
    0 repo stars
  60. ▌
    Ship 4 · garyld1962 bundle
    Ship completed work through the repo's actual delivery flow: checkpoint, commit, push, PR, and release steps. Reads project-specific delivery commands from config.
    0 repo stars
  61. ▌
    Test Plan 4 · garyld1962 bundle
    Use before implementing a feature to generate it.todo() stubs from requirements (TDD-first). Supports plan, validate, and refresh modes. TypeScript monorepos.
    0 repo stars
  62. ▌
    Code Review 2 · garyld1962 bundle
    Domain-based PR review controller. Use when you need a structured, multi-lens review of a pull request or code change. Supports two profiles: 'breakpoint' (light mid-flow review covering security, correctness, and tests only) and 'full' (comprehensive PR-boundary review covering all 11 domains). Conditional domains fire only when triggers match: data-integrity fires when the diff touches persistence (migrations, schemas, SQL, repositories, ORM models); api-contract fires when the diff touches a public surface (API routes, controllers, handlers, .proto files, OpenAPI/Swagger specs, library surface, message schema, CLI, or SDK). Do NOT use for trivial changes (typo fixes, mechanical refactors, dependency bumps with no logic changes). Do NOT use when you want professional craft grading or seniority assessment — use the code-review-professional skill instead.
    0 repo stars
  63. ▌
    Hotfix 3 · garyld1962
    Apply an expedited fix for a critical production issue: branch from main, apply a scoped fix, run targeted tests, and fast-track merge.
    0 repo stars
  64. ▌
    Execute Plan 7 · garyld1962 bundle
    Execute a written implementation plan with staged reviews, per-task build/test cycles, milestone breakpoints, and optional parallel agent lanes.
    0 repo stars
  65. ▌
    Code Investigate 4 · garyld1962 bundle
    Search one or more repos for a code pattern or behavior and produce a versioned Markdown investigation report. Supports literal, regex, and semantic (behavioral) search across multi-repo scope.
    0 repo stars
  66. ▌
    Review Adversarial 5 · garyld1962 bundle
    Cross-model adversarial code review via Codex/Gemini. Use for high-stakes diffs (auth, payments, migrations) or diffs over 200 lines after code-review passes.
    0 repo stars
  67. ▌
    Kickoff 3 · garyld1962
    Use for standard feature work to autonomously ship a PRD/story/AERS: readiness → plan → implement → review. Does not produce audit-grade governed artifacts.
    0 repo stars
  68. ▌
    Test Writer 2 · garyld1962
    Test file generator — converts TestSpecification objects into valid Vitest .test.ts files with it.todo() stubs.
    0 repo stars
  69. ▌
    State Lifecycle 2 · garyld1962
    State machine analyst — tests every valid transition, rejects every invalid one, verifies side effects of status changes.
    0 repo stars
  70. ▌
    Boundary Validation 2 · garyld1962
    Input validation analyst — tests required field enforcement, Zod constraint boundaries, NOT_FOUND handling, error code specificity, soft-delete behavior.
    0 repo stars
  71. ▌
    Contract Compliance 2 · garyld1962
    Requirements analyst — decomposes task description into testable requirements. Maps Zod schema fields to assertions. Verifies CRUD completeness and return type coverage.
    0 repo stars
  72. ▌
    Integration Surface 2 · garyld1962
    Integration analyst — tests router-to-service wiring, Zod schema binding, query vs mutation assignment, auth requirements, and cross-boundary contracts.
    0 repo stars
  73. ▌
    Pr 2 · garyld1962
    Full PR lifecycle: branch, commit, checkpoint, push, create PR, and optionally squash-merge. Automates the entire pull request workflow with quality gates.
    0 repo stars
  74. ▌
    Goal 2 · garyld1962
    Clarify and validate a development goal before writing a PRD. Use when the user has an idea or intent but hasn't shaped it into requirements yet — phrases like 'I want to build X', 'I'm thinking about adding Y', 'we should improve Z', 'what should we work on next', 'help me think through this idea'. Separates outcomes from solutions before any implementation work begins. When NOT to Use: requirements already written (use /prd-validate); specific bug to fix (use /triage); design decision to explore (use /design-twice).
    0 repo stars
  75. ▌
    Ship 2 · garyld1962 bundle
    Ship completed work through the repo's actual delivery flow: checkpoint, commit, push, PR, and release steps. Reads project-specific delivery commands from config.
    0 repo stars
  76. ▌
    Vault 2 · garyld1962
    Search, create, and manage notes in the Obsidian vault at /data/obsidian. Use when user wants to find, create, link, or organize notes — phrases like 'find my note on X', 'create a note about', 'add this to the vault', 'search my notes', 'open the vault'.
    0 repo stars
  77. ▌
    Thesis 2 · garyld1962
    Interrogate to discover the single-sentence product or architectural thesis, then audit all planned features and decisions against it.
    0 repo stars
  78. ▌
    Goal 3 · garyld1962
    Turn a rough idea into a clear outcome, problem statement, success measures and scope before requirements work. Use for goal discovery, not an already written PRD or an implementation request whose outcome is clear.
    0 repo stars
  79. ▌
    Vault 3 · garyld1962
    Search, read, create or organize Markdown notes in a configured Obsidian vault, including wiki links and backlinks. Use when the user names their vault or Obsidian notes; do not assume a personal filesystem path or use it for ordinary repository docs.
    0 repo stars
  80. ▌
    Grill Me 2 · garyld1962
    Use when user says 'grill me', wants to stress-test a plan, or validate assumptions. Walks the decision tree one question at a time, exploring the codebase when it can.
    0 repo stars
  81. ▌
    Simplify 2 · garyld1962 bundle
    Explain dense progress reports, task or wave summaries, blockers and decision requests in plain language. Use /simplify, 'explain that simply', or before user-facing PRD/plan execution updates. Simplifies explanations, not code.
    0 repo stars
  82. ▌
    Drawio 3 · garyld1962 bundle
    Create or edit editable draw.io diagrams, optionally export PNG/SVG/PDF with embedded diagram data, or produce a diagrams.net URL. Use when draw.io format is requested; use native text diagrams for simple explanations that need no draw.io artifact.
    0 repo stars
  83. ▌
    Changelog 2 · garyld1962
    Use to generate a release from Conventional Commits. Groups commits since the last tag, auto-bumps the version, updates CHANGELOG.md, tags, and releases.
    0 repo stars
  84. ▌
    Configure 2 · garyld1962 bundle
    Use when a skill's pre-flight says config is missing, or with no arg to see what needs configuring. Interviews the user and writes the config file.
    0 repo stars
  85. ▌
    Env Check 2 · garyld1962 bundle
    Detect the current shell environment and choose safe command routing. Use when working across different shells, OSes, or remote hosts. Reads user-specific shell config from ~/.claude/env.config.md.
    0 repo stars
  86. ▌
    Modernize 2 · garyld1962
    Audit a codebase against current AI toolchain capability and produce a prescriptive refactor plan. Use when revisiting an older project (months of dormancy or older-AI-era patterns) to identify structural improvements — abstraction, separation of concerns, types, error handling, tests, infra organization — that newer models can now execute safely. Default --handoff invokes /execute-prd --type=refactor on the resulting plan. Trigger phrases: 'modernize this codebase', 'refresh the code', 'what would this look like today', 'AI-time refresh', 'modernization audit'. Strictly within the current platform/stack — does not propose framework changes, language switches, or public-API rewrites.
    0 repo stars
  87. ▌
    Sync Main 2 · garyld1962
    Sync current branch with main: fetch, rebase, resolve conflicts. Use when your branch is behind main or before creating a PR.
    0 repo stars
  88. ▌
    Test Plan 2 · garyld1962 bundle
    Use before implementing a feature to generate it.todo() stubs from requirements (TDD-first). Supports plan, validate, and refresh modes. TypeScript monorepos.
    0 repo stars
  89. ▌
    Work Item 2 · garyld1962
    Retrieve a work item from Azure DevOps or Linear. Extracts title, description, acceptance criteria, status, assignee, and tags. Presents in clean markdown format for use by other skills.
    0 repo stars
  90. ▌
    Simplify 3 · garyld1962 bundle
    Explain dense updates and decisions in plain language.
    0 repo stars
  91. ▌
    K8S Verify 2 · garyld1962
    Post-deploy verification for Kubernetes: checks pod health, service endpoints, recent events, log errors, and rollout status. Use after any K8s deployment to verify it succeeded.
    0 repo stars
  92. ▌
    Postmortem 2 · garyld1962
    Structured retrospective over a completed execute-plan run. Reads the run folder, writes postmortem.md + postmortem.json, and appends to the postmortem index.
    0 repo stars
  93. ▌
    Skill Help 2 · garyld1962
    List available skills or show detailed help for a specific skill. Use when the user asks 'what skills are available', 'help with a skill', 'what can you do', 'list skills', or '/skill-help'.
    0 repo stars
  94. ▌
    Simplify 4 · garyld1962 bundle
    Explain dense progress reports, task or wave summaries, blockers and decision requests in plain language. Use 'simplify this update', 'explain that simply', or before user-facing PRD/plan execution updates. Simplifies explanations, not code.
    0 repo stars
  95. ▌
    Bug Session 2 · garyld1962
    Interactive bug-reporting session: user describes problems conversationally, agent explores the codebase for domain context, and files durable GitHub issues. Use when user wants to report bugs, do QA testing, capture defects — phrases like 'let's do a bug session', 'I found some issues', 'QA session', 'help me file these bugs'. When NOT to Use: single known bug to investigate (use /triage); existing issue to fix (use /hotfix or /execute-prd).
    0 repo stars
  96. ▌
    Repo Status 2 · garyld1962
    Reports live repo state: branch, working tree, unpushed commits, stashes, and open PRs. Read-only snapshot for orienting at the start of a session or after a long break.
    0 repo stars
  97. ▌
    Skill Audit 2 · garyld1962
    Use periodically or when setting up a new project to audit Claude Code skills/plugins/agents, research marketplaces, gap-analyze, and implement recommendations.
    0 repo stars
  98. ▌
    Design Twice 2 · garyld1962
    Explore multiple radically different API/module designs using parallel agents before committing. Use when designing a new interface, module API, or public surface — phrases like 'design it twice', 'explore the design space', 'what are my options for this interface', 'compare API shapes', 'how should this module look'. When NOT to Use: implementation details inside an existing interface (use superpowers:writing-plans); evaluating existing code (use /code-review).
    0 repo stars
  99. ▌
    Gh Readiness 2 · garyld1962
    Verify GitHub CLI (gh) is installed, authenticated, and able to reach github.com before running skills that create PRs, issues, or releases. Use before /pr, /ship, /hotfix, /issue-slices, /bug-session, or /changelog when gh status is unknown.
    0 repo stars
  100. ▌
    Issue Slices 2 · garyld1962
    Break a PRD into independently-grabbable GitHub issues as vertical tracer-bullet slices. Use when user wants to convert a PRD to tickets, create implementation issues from a PRD — phrases like 'break this PRD into issues', 'create tickets from the PRD', 'slice the PRD into work items'. When NOT to Use: want the PRD executed end-to-end automatically (use /execute-prd); rough idea not yet a PRD (use /goal → /prd-create first); want a plan doc not issues (use /execute-prd step 1).
    0 repo stars