A Requirements-First Spec-Driven Development (SDD) toolkit for Codex and Claude Code with multi-language support
Command Claude Code
A cross-document consistency checker for software requirements, specifications, designs, plans, and task lists. It treats requirements.md as the main source of truth and can update downstream documents when they disagree.
Command Claude Code
A command for reviewing whether translated documents keep the same meaning and quality as their English source.
Command Claude Code
A command that creates a tailored checklist for checking whether software requirements are complete, clear, and consistent. It can use the project's constitution file, which records project principles and quality rules, when one exists.
Command Claude Code
A requirements clarification command that resolves unclear feature requests and keeps requirements.md and spec.md in sync. It can use the project's language settings for conversations and document files.
Command Claude Code
A command that turns confirmed requirements into a technical specification document without changing the intended product behavior. It also follows project rules and records assumptions separately from confirmed decisions.
Command Claude Code
Manage CodexSpec project configuration interactively.
Command Claude Code
A command for creating or updating a project's constitution: a written set of principles that guides project work. It can take principles directly or explore them interactively.
Command Claude Code
Debug a failure to its root cause before proposing any fix.
Command Claude Code
Distill reusable, cross-feature knowledge from an interaction into the project profile.
Command Claude Code
Compile vetted project-profile knowledge into a reusable command/skill and contribute it upstream via a reviewed PR.
Command Claude Code
Read .codexspec/config.yml. Two independent language controls apply (each falls back to language.output, then English).
Command Claude Code
A task implementation command that carries out the tasks in a project plan. For code, it can use TDD, a process of writing a failing test before the code that makes it pass; documents and configuration are implemented directly.
Command Claude Code
Cold-start the project profile by scanning an existing codebase for conventions and constraints.
Command Claude Code
A task-planning command that expands an approved implementation plan into specific, traceable coding tasks.
Command Claude Code
A pull-request or merge-request description generator based on the changes in Git and, when available, a software specification.
Command Claude Code
A command for small, clearly defined code changes that follows a short requirements-first process. Requirements-first means confirming what should be built before planning the edits.
Command Claude Code
Generate release notes from git history — maintain a Keep a Changelog CHANGELOG.md entry and emit a user-facing release body, without deciding versions or mutating git state.
Command Claude Code
A command that reviews selected code changes as a strict defect gate before merging. It also supports a separate audit mode.
Command Claude Code
Review design fidelity, feasibility, and planning readiness.
Command Claude Code
A plan-review command for checking whether a software implementation plan matches the requirements, can realistically be built, and is ready to use.
Command Claude Code
A command for reviewing Python code for style, type annotations, reliability, performance, and project rules. PEP 8 is the commonly used guide for formatting and writing readable Python.
Command Claude Code
A command that reviews React and TypeScript code, including how components are organised, how Hooks are used, how state is handled, and how the code performs.
Command Claude Code
A command that reviews a software specification for accuracy, internal quality, and readiness for implementation. A specification describes what a feature should do and provides the reference for building it.
Command Claude Code
A command that reviews a task list for fidelity to its source plans, practical executability, dependencies, and ways to verify completion. It can use project requirements, specifications, designs, plans, and repository files.