azjester

by dunnock

Walk through the NASA Phase A concept development lifecycle: ideation, problem definition, black-box architecture, drill-down with gap analysis, and document generation. Produces concept documents and solution landscape summaries with cited research. Includes 7 specialized agents (ideation, problem analysis, architecture, domain research, gap analysis, skeptic verification, document writing), 6 scripts (session management, source/assumption tracking, web research with crawl4ai), 9 commands, hooks for automatic state updates, and tiered research tool detection. Use when developing a concept, exploring a new idea, brainstorming a system concept, running Phase A, creating a concept document, or conducting feasibility studies.

Transform documentation using the Diátaxis framework

by dunnock

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.

by dunnock

Create comprehensive Fishbone (Ishikawa/Cause-and-Effect) diagrams for structured root cause brainstorming. Guides teams through problem definition, category selection (6Ms, 8Ps, 4Ss, or custom), cause identification, sub-cause drilling, prioritization via multi-voting, and 5 Whys integration. Generates visual SVG diagrams and professional HTML reports. Use when brainstorming potential causes, conducting root cause analysis, facilitating quality improvement sessions, analyzing defects or failures, structuring team problem-solving, or when user mentions "fishbone", "Ishikawa", "cause and effect diagram", "6Ms", "cause analysis", or "brainstorming causes".

by dunnock

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.

by dunnock

Conduct Failure Mode and Effects Analysis (FMEA) for systematic identification and risk assessment of potential failures in designs, processes, or systems. Supports DFMEA (Design), PFMEA (Process), and FMEA-MSR (Monitoring & System Response). Uses AIAG-VDA 7-step methodology with Action Priority (AP) risk assessment replacing traditional RPN. Use when analyzing product designs for potential failures, evaluating manufacturing process risks, conducting proactive risk assessment, preparing for APQP/PPAP submissions, investigating field failures, or when user mentions "FMEA", "failure mode", "DFMEA", "PFMEA", "severity occurrence detection", "RPN", "Action Priority", "design risk analysis", or needs to identify and prioritize potential failure modes with their causes and effects.

by dunnock

Conduct Kepner-Tregoe (KT) Problem Solving and Decision Making (PSDM) analysis using the four rational processes - Situation Appraisal, Problem Analysis, Decision Analysis, and Potential Problem Analysis. Use when performing structured root cause analysis, making complex decisions, evaluating alternatives with weighted criteria, conducting IS/IS NOT specification analysis, anticipating implementation risks, troubleshooting complex issues, or when user mentions "Kepner-Tregoe", "KT method", "IS/IS NOT", "situation appraisal", "decision analysis", "MUSTS and WANTS", "potential problem analysis", or needs systematic problem-solving methodology. Includes specification matrices, decision scoring, quality rubrics, and professional report generation.

by dunnock

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.

by dunnock

Automatically generate Claude plugins from user prompts. Supports plugin creation, documentation, and testing. Use when needing to create a new plugin or when user mentions "plugin", "Claude plugin", "plugin creation", or "plugin development".

by dunnock

Guide RCCA/8D problem definition using 5W2H and IS/IS NOT analysis. Transforms scattered failure data into precise, measurable problem statements that bound investigation scope without embedding cause or solution. Use when defining problems for root cause analysis, writing D2 sections of 8D reports, analyzing nonconformances, investigating failures, or when user mentions problem definition, problem statement, RCCA, 8D, failure analysis, or corrective action.

by dunnock

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.

by dunnock

Transform concept development artifacts into INCOSE-compliant formal requirements. AI-assisted requirements development with hybrid quality checking (16 deterministic + 9 semantic INCOSE GtWR v4 rules), verification planning, bidirectional traceability, gap analysis against concept architecture, assumption lifecycle management, and ReqIF export. Organized around functional blocks from concept development. Includes cross-cutting notes registry, need/requirement split workflow, gap discovery agent, assumption tracker, 5 specialized agents (quality-checker, tpm-researcher, skeptic, gap-analyst, document-writer), 16 scripts, 10 commands, and hooks for automatic state updates. Use when developing requirements, formalizing needs, writing specifications, building traceability, analyzing coverage gaps, managing assumptions, or preparing for systems engineering reviews.

Research and opportunity investigation for protocols

by David Dunnock

Deep test, analyze, and audit Claude skills. Use this skill 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. Trigger on: "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.

by Claude Code Skills

Systematic analysis and refinement of specifications with SEAMS framework, sequential clarification questioning, and multi-phase workflow

by Claude Code Skills

Project-focused specification and task management with PLANS taxonomy, ADR-style architecture decisions, SMART acceptance criteria, SEAMS-enhanced clarification, tech-specific designer agents, anti-pattern detection (50 patterns across 5 tech stacks), 4-level verification (stub detection + wiring checks), execution orchestration (deviation rules, checkpoint taxonomy, auth gates, session continuity), specialized analysis agents, git checkpoints, mandatory approval gates, and session-memory hooks. Outputs to speckit/ directory.

Stream long-form content to markdown files with resume capability and context preservation

Stream structured content to persistent SQLite storage with automatic session break recovery. Supports multi-format export (Markdown, HTML, JSON, YAML, CSV, Text) and document templates. Core principle: The content IS the state.

Systematic trade study using DAU 9-Step Process