Create a blog post about your work with minimal friction. Gathers context automatically and provides structured templates to reduce blank-page anxiety.

Reconcile what the codebase actually does against what the PRD says it should do, then map every story to its tests and rank the gaps. Produces one durable artifact: `docs/blueprint/audits/<date>-story-audit.md`.

Analyze test suite for quality issues and reliability.

Read-only status report on the coordination queue. Strictly uses `export | jq` — never `list` — so parallel Bash batches from downstream skills stay safe.

WCAG 2.1/2.2 compliance implementation, ARIA patterns, keyboard navigation, focus management, and accessibility testing. Use when implementing accessible components, fixing accessibility issues, or when the user mentions WCAG, ARIA, screen readers, or keyboard navigation.

Domain analysis, conflict detection, and relationship validation for Architecture Decision Records. Use when creating or validating ADRs to ensure consistency.

Analyze all plugins for sub-agent opportunities. Identifies skills with verbose output, gaps in agent coverage, and model selection improvements.

Check and configure API contract testing with Pact, OpenAPI validation, and schema testing

Route to specialized agents based on codebase health attributes. Use after /attributes:collect to automatically address findings by severity.

Advanced Bevy ECS patterns including complex queries, system scheduling, change detection, entity relationships, and performance optimization. Use when working on advanced Bevy game architecture, optimizing ECS performance, or implementing complex game systems.

Bevy game engine development including ECS architecture, rendering, input handling, asset management, and game loop design. Use when building games with Bevy, working with entities/components/systems, or when the user mentions Bevy, game development in Rust, or 2D/3D games.

Consistent style guide for writing blog posts about projects and technical work. Supports quick updates, detailed write-ups, retrospectives, and tutorials. Designed for low-friction entry and easy scanning.

List all ADRs with title, status, date, and domain in a markdown table

Validate ADR relationships, detect orphaned references, and check domain consistency

Derive Architecture Decision Records from existing project structure, dependencies, and documentation

Derive PRDs, ADRs, and PRPs from git history, codebase structure, and existing documentation

Derive test regression plans from git history by identifying fix and feature commits lacking corresponding tests. Use when you need to find untested bug fixes, coverage gaps, or generate a test backlog from commit analysis.

Generate project-specific rules and commands from PRDs for Blueprint Development methodology. Use when generating behavioral rules for architecture patterns, testing strategies, implementation guides, or quality standards from requirements documents.

List blueprint documents (ADRs, PRDs, PRPs) with metadata extracted from frontmatter and headers

Display feature tracker statistics and completion summary