Specification-driven development with EARS, Gherkin, and multi-provider support. Covers requirements authoring, BDD workflows, SpecKit integration, Kiro compatibility, ADRs, and user story management.
npx claudepluginhub melodic-software/claude-code-plugins --plugin spec-driven-developmentPROACTIVELY use when documenting architectural decisions. Creates Architecture Decision Records (ADRs) from specification context using MADR format. Extracts technical decisions, alternatives considered, rationale, and consequences from specifications.
PROACTIVELY use. Interactive authoring assistant for specifications. Pass mode as argument (ears, gherkin, userstory). Use when creating new requirements using EARS syntax, Gherkin scenarios, or user stories with step-by-step guidance.
PROACTIVELY use. Converts specifications between formats. Pass mode as argument (ears, gherkin, kiro). Use for format transformations, feature file generation, or Kiro synchronization.
PROACTIVELY use. Generates or refines specifications. Pass mode as argument (generate, refine). Use for creating new specs from requirements or improving existing spec quality.
PROACTIVELY use. Audits or validates specifications (read-only). Pass mode as argument (audit, validate). Use for quality audits with scoring or quick format validation.
PROACTIVELY use. Executes the complete GitHub Spec Kit 5-phase workflow. Use for end-to-end specification-driven development from constitution to implementation. Orchestrates all phases with validation gates.
Create Architecture Decision Record from specification context.
Author and validate AsyncAPI 3.0 specifications for event-driven API design, message brokers, and async communication patterns
Audit specification quality and generate compliance report.
Canonical specification format reference. Use when understanding the canonical spec schema, field requirements, provider-agnostic specification structure, or validating specifications against the schema.
Create or update the project constitution file (.constitution.md) for Spec Kit workflow.
Design and manage API contracts before implementation using OpenAPI and AsyncAPI specifications for contract-first development
Convert specification between formats (EARS, Gherkin, Kiro, canonical).
Interactive EARS pattern authoring assistant. Guides through pattern selection and requirement construction.
EARS requirement pattern authoring. Use when writing requirements using EARS patterns (Ubiquitous, State-Driven, Event-Driven, Unwanted, Optional, Complex). Provides pattern templates, validation, and examples.
Convert specifications to/from EARS format.
Interactive Gherkin scenario authoring. Guides through Given/When/Then construction with BDD best practices.
Gherkin acceptance criteria authoring. Use when writing Given/When/Then scenarios, feature files, or BDD-style specifications. Provides syntax reference, best practices, and Reqnroll integration guidance.
Convert specifications to/from Gherkin/BDD format.
Guide implementation of specification tasks. Phase 4 of Spec Kit workflow.
AWS Kiro specification patterns and synchronization. Use when working with Kiro IDE, syncing requirements.md/design.md/tasks.md files, or configuring steering files for AI agent context.
Synchronize specifications with AWS Kiro format (requirements.md, design.md, tasks.md).
Author and validate OpenAPI 3.1 specifications for REST API design, following API-first and contract-first development practices
Generate an implementation plan from a specification. Phase 2 of Spec Kit workflow.
Refine specification with AI-assisted improvements.
Requirements quality assessment and improvement. Use when evaluating requirements against INVEST criteria, improving clarity, detecting ambiguity, or ensuring completeness. Provides quality checklists, refinement patterns, and MoSCoW prioritization guidance.
Central authority for specification-driven development. Use when working with requirements, specifications, acceptance criteria, or any spec-driven workflow. Provides navigation to specialized skills and delegates to docs-management for official documentation.
Generate a canonical specification from a feature request or user story. Phase 1 of Spec Kit workflow.
Execute the complete GitHub Spec Kit 5-phase workflow from constitution to implementation.
GitHub Spec Kit 5-phase workflow. Use when following the Constitution → Specify → Plan → Tasks → Implement cycle. Provides phase guidance, file templates, and workflow orchestration.
Display specification status dashboard showing workflow progress, quality scores, and pending items.
Author Agile-style user stories with linked acceptance criteria.
Validate specification against schema and quality rules.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Complete collection of battle-tested Claude Code configs from an Anthropic hackathon winner - agents, skills, hooks, and rules evolved over 10+ months of intensive daily use
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Claude Code skills for Godot 4.x game development - GDScript patterns, interactive MCP workflows, scene design, and shaders
Use this agent when you need expert assistance with React Native development tasks including code analysis, component creation, debugging, performance optimization, or architectural decisions. Examples: <example>Context: User is working on a React Native app and needs help with a navigation issue. user: 'My stack navigator isn't working properly when I try to navigate between screens' assistant: 'Let me use the react-native-dev agent to analyze your navigation setup and provide a solution' <commentary>Since this is a React Native specific issue, use the react-native-dev agent to provide expert guidance on navigation problems.</commentary></example> <example>Context: User wants to create a new component that follows the existing app structure. user: 'I need to create a custom button component that matches our app's design system' assistant: 'I'll use the react-native-dev agent to create a button component that aligns with your existing codebase structure and design patterns' <commentary>The user needs React Native component development that should follow existing patterns, so use the react-native-dev agent.</commentary></example>