Agent skills
Skills you can use with AI coding agents, indexed from public GitHub repositories.
-
concept-dev
This skill should be used when the user asks to "develop a concept", "explore a new idea", "brainstorm a system concept", "do concept development", "create a concept document", "run Phase A", "define the problem and architecture", or mentions concept exploration, feasibility studies, concept of operations, system concept, architecture exploration, solution landscape, or NASA Phase A.
ddunnock/claude-plugins 6
-
speckit-generator
Project-focused specification and task management system. Run /speckit.init to install 8 project-local commands: /plan, /tasks, /design, /analyze, /clarify, /implement, /revert, /lint. Each command MUST be invoked separately and requires user approval before proceeding. NEVER chain commands automatically - each produces output that requires user review. Use /plan when user wants to create plans from specs. Use /tasks only AFTER user has approved plans. Git checkpoints enable safe revert.
ddunnock/claude-plugins 6
-
adr-authoring
This skill should be used when writing Architecture Decision Records (ADRs),
documenting technical decisions, or reviewing architecture choices. Triggers on
phrases like "document this decision", "create ADR", "architecture decision",
"why did we choose", "record the decision", "MADR template", or when the user
is working on plan files that contain ADR sections.
ddunnock/claude-plugins 6
-
requirement-patterns
This skill should be used when writing requirements, specifications, or user stories.
Triggers on phrases like "write requirements", "create spec", "define user stories",
"document feature", "specify behavior", "what should the system do", or when reviewing
specification quality. Provides patterns for clear, testable, unambiguous requirements.
ddunnock/claude-plugins 6
-
documentation-architect
Transform documentation from any starting point into professional, comprehensive documentation packages using the Diátaxis framework. 7 commands: init (create structure), inventory (catalog sources), plan (create WBS), generate (create docs), sync (update from code reality), analyze (quality audit), readme (manage README/CHANGELOG). Integrates with speckit-generator for implementation-to-docs workflow. Supports specs, ADRs, RFCs as input with code walkthrough for syncing docs to reality.
ddunnock/claude-plugins 6
-
rcca-master
Orchestrate complete Root Cause and Corrective Action (RCCA) investigations using the 8D methodology. Guides team formation (D1) with domain-specific recommendations, problem definition (D2), containment (D3), root cause analysis (D4) with integrated tool selection (5 Whys, Fishbone, Pareto, Kepner-Tregoe, FTA), corrective action (D5-D6), prevention (D7), and closure (D8). Use when conducting RCCA, 8D, root cause analysis, corrective action, failure investigation, nonconformance analysis, quality problems, or customer complaints.
ddunnock/claude-plugins 6
-
five-whys-analysis
Conduct rigorous 5 Whys root cause analysis with guided questioning, quality scoring, and professional report generation. Use when performing root cause analysis, investigating problems, conducting 5 Whys sessions, troubleshooting recurring issues, or when user mentions "5 whys", "root cause", "why did this happen", "find the cause", or needs to identify underlying causes of defects, failures, or process problems. Includes validation tests, scoring rubric, and countermeasure development.
ddunnock/claude-plugins 6
-
research-opportunity-investigator
Conduct systematic research and opportunity investigation for ACP protocol integration, collaboration, and enhancement opportunities. Use when the user wants to research external projects, protocols, or tools for potential collaboration; investigate gap-filling opportunities for IDE integrations; assess compatibility between ACP and external protocols; or identify opportunities for ACP adoption. Guides through discovery, analysis, validation, and RFC generation with mandatory gates and source grounding. Outputs include comprehensive summary documents, gap analyses, and formal RFC proposals.
ddunnock/claude-plugins 6
-
specification-refiner
Systematic analysis and refinement of specifications, requirements, architecture designs, and project plans. Use when the user wants to identify gaps, weaknesses, inefficiencies, or complications in a proposed plan, specification, or design document. Triggers on gap analysis, specification review, requirements analysis, architecture critique, design validation, plan assessment, weakness identification, assumption auditing, or when users share specs/plans asking for feedback. Produces actionable findings with remediations and maintains analysis state across iterations. Features sequential clarification with one question at a time, recommended answers, and immediate integration.
ddunnock/claude-plugins 6
-
fault-tree-analysis
Conduct Fault Tree Analysis (FTA) to systematically identify and analyze causes of system failures using Boolean logic gates. Top-down deductive method for safety and reliability engineering. Use when analyzing system failures, evaluating safety-critical designs, calculating failure probabilities, identifying minimal cut sets, assessing redundancy effectiveness, or when user mentions "fault tree", "FTA", "system failure analysis", "minimal cut sets", "safety analysis", "failure probability", "AND/OR gates", or needs to trace failure pathways from top event to basic events. Supports qualitative structure analysis and quantitative probability calculations.
ddunnock/claude-plugins 6
-
plugin-creator
Creates plugins (skills and MCPs) by guiding through the authoring process. Use when users want to create or update (1) skills that extend Claude's capabilities with specialized knowledge and workflows, or (2) MCPs (Model Context Protocol servers) that provide tools for Claude Desktop.
ddunnock/claude-plugins 6
-
trade-study-analysis
Conduct systematic trade study analyses using the DAU 9-Step Trade Study Process. Guides engineers through problem definition, root cause analysis (5 Whys, Fishbone), data collection from alternatives and datasheets, normalization calculations, weighted scoring, sensitivity analysis, and professional report generation with visualizations and decision matrices. Use when evaluating alternatives, comparing solutions, conducting trade-offs, or making engineering decisions.
ddunnock/claude-plugins 6
-
pareto-analysis
Conduct Pareto Analysis (80/20 Rule) to identify the vital few causes driving the majority of problems. Guides data collection, category definition, chart creation, cumulative percentage calculation, and prioritization. Generates professional Pareto charts (SVG) and HTML reports with quality scoring. Use when prioritizing defects, complaints, failures, or improvement opportunities; when user mentions "Pareto", "80/20 rule", "vital few", "trivial many", "prioritization", or needs to identify which factors contribute most to a problem.
ddunnock/claude-plugins 6
-
skill-tester
This skill should be used whenever the user wants to test a skill's behavior, analyze how it uses the Claude API, inspect inputs/outputs from scripts, or run security and code review audits against skill scripts. Even for casual phrases like "test my skill", "analyze this skill", "audit skill scripts", "review skill for security issues", "what does this skill actually do when it runs", "inspect API calls from skill", "run a skill through its paces", "check my skill for bugs or vulnerabilities". Also trigger when the user shows you a SKILL.md and asks you to evaluate, critique, or stress-test it.
ddunnock/claude-plugins 6
-
system-dev
Guides AI-assisted systems design using INCOSE principles. Creates and manages a Design Registry with typed slots for components, interfaces, contracts, and requirement references. Use when the user mentions system design, design registry, component decomposition, interface resolution, behavioral contracts, traceability, impact analysis, or /system-dev commands.
ddunnock/claude-plugins 6
-
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
junghan0611/denotecli 8
-
brainstorming
Use when creating or developing anything, before writing code - refines rough ideas into bd epics with immutable requirements
withzombies/hyperpowers 72
-
test-driven-development
Use when implementing features or fixing bugs - enforces RED-GREEN-REFACTOR cycle requiring tests to fail before writing code
withzombies/hyperpowers 72
-
sre-task-refinement
Use when you have to refine subtasks into actionable plans ensuring that all corner cases are handled and we understand all the requirements.
withzombies/hyperpowers 72
-
review-implementation
Use after hyperpowers:executing-plans completes all tasks - verifies implementation against bd spec, all success criteria met, anti-patterns avoided
withzombies/hyperpowers 72
-
debugging-with-tools
Use when encountering bugs or test failures - systematic debugging using debuggers, internet research, and agents to find root cause before fixing
withzombies/hyperpowers 72
-
writing-plans
Use to expand bd tasks with detailed implementation steps - adds exact file paths, complete code, verification commands assuming zero context
withzombies/hyperpowers 72
-
fixing-bugs
Use when encountering a bug - complete workflow from discovery through debugging, bd issue, test-driven fix, verification, and closure
withzombies/hyperpowers 72
-
using-hyper
Use when starting any conversation - establishes mandatory workflows for finding and using skills
withzombies/hyperpowers 72