
Ddunnock Claude Plugins
- 10 repo stars
- Updated March 16, 2026
- ddunnock/claude-plugins
ddunnock-claude-plugins is a Claude Code plugin that bundles twenty systems-engineering and quality-methodology skills for requirements, architecture, FMEA, and documentation inside your agent session
About
ddunnock-claude-plugins is a Claude Code plugin marketplace that bundles twenty capability extensions aimed at developers who want systems-engineering discipline inside the agent, not ad hoc prompts. The collection spans ideation and clarification through structured requirements, architecture narration, failure-mode analysis, corrective-action thinking, and exportable documentation artifacts. Keywords and skill themes point to INCOSE-style rigor, measurable acceptance criteria, bidirectional traceability concepts, and visual diagrams without assuming a full enterprise toolchain. Developers shipping complex SaaS, embedded-adjacent, or compliance-sensitive products can register the marketplace once and invoke specialized commands for brainstorming, gate reviews, nonconformance handling, and black-box investigation patterns. It complements generic coding agents by grounding answers in explicit methodologies (7-step, 9-step, 9-phase frameworks) rather than one-off chat advice. Expect intermediate-to-advanced familiarity with requirements language; the payoff is repeatable audits, decision logs, and engineering memos you can attach to repos or reviews.
- 20-plugin marketplace covering brainstorming, 9-phase lifecycle, and checkpoint-style methodology
- FMEA, DFMEA, FMEA-MSR, and Ishikawa (fishbone) failure and root-cause workflows
- INCOSE-aligned need/requirement, ADR-style, and Ditaxis documentation generation
- Kepner-Tregoe-style decision and appraisal flows plus architecture and audit checklists
- Includes MCP, hooks, and domain-specific investigation patterns for agent-driven engineering
Ddunnock Claude Plugins by the numbers
- Data as of Jul 22, 2026 (Skillselion catalog sync)
/plugin install ddunnock-claude-plugins@ddunnock/claude-pluginsAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 10 |
|---|---|
| Last updated | March 16, 2026 |
| Repository | ddunnock/claude-plugins ↗ |
What it does
Add a 20-skill engineering toolkit to Claude Code for requirements, architecture decisions, FMEA, and structured documentation while you ship hardware- or systems-style products.
Who is it for?
Best when you're shipping complex or regulated-leaning products and want INCOSE-style rigor, FMEA, and decision documentation without hiring a systems engineer.
Skip if: Skip if you only need lightweight todo tracking or a single MCP connector with no requirements or quality methodology.
What you get
After you add the marketplace, Claude Code can run structured brainstorming, FMEA, fishbone, and INCOSE-style doc flows that produce traceable decisions and review-ready artifacts.
- Structured requirements, CONOPS, and Ditaxis-style documentation drafts
- FMEA, fishbone, and decision-analysis writeups tied to your feature or system
- Architecture and audit checkpoint outputs usable in code review or ship gates
By the numbers
- Plugin count: 20
- Repository: ddunnock/claude-plugins
- Marketplace type: multi-plugin engineering and methodology collection
Recommended Plugins
How it compares
A 20-skill engineering methodology marketplace, not one integration skill or a raw skills.sh popularity listing.
FAQ
Who is Ddunnock Claude Plugins for?
and small-team developers using Claude Code who need structured requirements, failure analysis, architecture records, and audit-style checklists during product development.
When should I use Ddunnock Claude Plugins?
Use it during build and pre-ship reviews when you are defining requirements, analyzing failures, documenting ADRs, or running gate-style checkpoints before you commit to implementation.
How do I add Ddunnock Claude Plugins to my agent?
Install or register the ddunnock/claude-plugins marketplace in Claude Code, enable the plugins you need from the bundle, then invoke their commands or skills from your project workspace.