Audit a speq project's health — spec-library structure, feature/decision-log/plan validation, mission-to-spec sync, unrecorded plans, and gitignore hygiene — then guide fixes. Use when the user asks to audit, health-check, doctor, lint, or sanity-check the specs or repo, or after cloning or inheriting a speq project.
Orchestrate implementation of a reviewed plan: task breakdown, TDD sub-agents, code review, and verification report. Use when the user asks to implement, build, or execute a plan under specs/plans/ — after /speq-plan, before /speq-record. Arg: .
Headless, non-interactive version of /speq-plan for CI or agent-driven runs. Plans a feature without a live interview, commits the result to a feat/plan-name branch, and opens a draft PR. If a decision genuinely needs a human, it persists the partial plan and open questions and asks in a PR comment instead of…
Generate deterministic, executable tests strictly from a canonical verification contract, with requirement traceability, test-oracle independence, artifact integrity validation, and strict separation from production implementation. Prevent interpreter mismatches and pre-flight binary existence loops.
Transform a canonical implementation specification into a deterministic verification protocol with explicit requirement traceability, evidence contracts, testability assessment, and implementation-independent verification methods. Highly stable, failing closed on specification gaps.
Transform a rough feature idea into a complete milestone document through interactive requirements elicitation. Ensures strict, observable scope boundaries.
Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
Skill "mddd-context-map" from JulioCRFilho/mermaid-diagram-driven-development, covering purpose, conceptual model, multi-level architecture diagram spec, 1. type and direction and 2. subgraphs (one per macro domain).
Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes…
A code review procedure that checks whether concurrent code can safely share data and perform operations at the same time. Concurrency means multiple parts of a program run in overlapping periods.
A documentation audit tool that compares project documents with the code and checks several linked records, such as routes, database models, and service methods. It also scans selected rules and configuration areas for omissions or unsafe patterns.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: