Results for “spec-check”

Conducts structured requirements workshops to produce feature specifications, user stories, EARS-format functional requirements, acceptance criteria, and implementation checklists.

Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".

Enforces a machine-readable behavioral contract for multi-agent development, mandating specification-first workflows, git checkpoints, context lineage, and quality gates.

Creates a GitHub issue from a specification file using a feature request template, checking for existing issues first.

Creates GitHub Issues for unimplemented requirements from specification files, checking the codebase and existing issues to avoid duplicates.

Create systematic QA checklists to verify that design implementations match specifications across visual accuracy, layout, interaction, content, accessibility, and cross-platform categories.

Comprehensive hospitality guest services specialist for hotels, resorts, restaurants, and event venues — covering reservations, check-in/check-out, concierge services, guest complaint resolution, loyalty program management, and post-stay follow-up to deliver exceptional guest experiences that drive loyalty and revenue

Weed the Allium garden. Find where Allium specifications and implementation code have diverged, and help resolve the divergences. Use when the user wants to check spec-code alignment, compare specs against implementation, audit for spec drift or violations, sync specs with code or code with specs, or verify whether the implementation matches what the spec says.

Generate tests from Allium specifications. Use when the user wants to propagate tests, generate test files from a spec, write tests for a specification, create property-based tests, produce state machine tests, check test coverage against spec obligations, or understand what tests a specification requires.

Run a full project health diagnostic — checks structure, agents, features, scripts, extensions, and git status.

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md. Identifying inconsistencies, duplications, ambiguities, and underspecified items.

Verifica que una implementación cumpla los specs del ciclo SDD ejecutando tests reales, revisando cobertura y emitiendo un veredicto de aprobación o rechazo.

Audit specs against codebase — find unimplemented features, diverged implementations, and undocumented code

Identify underspecified areas in the current feature spec by asking targeted clarification questions and encoding answers back into the spec.

Run GitHub's Spec-Driven Development (SDD) workflow via the `specify` CLI — install spec-kit, initialize a project for one of 30+ AI coding agents (Claude Code, Copilot, Gemini, Cursor, Codex, Qwen, opencode, Kiro, etc.), and drive the constitution → specify → plan → tasks → implement command pipeline. Use when the user wants to bootstrap a Spec-Driven Development project, install `specify-cli`, generate executable specs before code, or invoke the `/speckit.*` slash commands (`/speckit.constitution`, `/speckit.specify`, `/speckit.plan`, `/speckit.tasks`, `/speckit.implement`, `/speckit.clarify`, `/speckit.analyze`, `/speckit.checklist`). Triggers on: spec-kit, speckit, specify, specify init, spec-driven, spec driven development, SDD, /speckit, executable spec.

Create Git branches following the Conventional Branch specification (feature/, bugfix/, hotfix/, release/, chore/). Validates branch names and automates checkout from the correct base branch.

Verifies that blockchain code implements exactly what documentation specifies, identifying gaps between specs and implementation for audit engagements.

Validate Claude Code skills against the agentskills specification. Catches structural, semantic, and naming issues before users do.

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

spec-ship

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).

Perform a post-implementation retrospective analysis measuring spec adherence, implementation deviations, and lessons learned.

Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

Speckit Implement Agent

Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).

Speckit Implement

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".