A Requirements-First Spec-Driven Development (SDD) toolkit for Codex and Claude Code with multi-language support
This repository also configures its own agents. See what codexspec tells them →
Skill Claude CodeCodex
A tool for checking whether software requirements, designs, plans, and tasks agree with one another. SDD means specification-driven development: using linked documents to describe and plan a system before building it.
Skill Claude CodeCodex
A generator for checklists that test whether software requirements are complete, clear, and consistent.
Skill Claude CodeCodex
A requirements-clarifying tool that resolves ambiguous details and keeps requirements and specifications aligned.
Skill Claude CodeCodex
An interactive manager for project configuration, including the languages used for conversation and generated documents.
Skill Claude CodeCodex
A project-principles tool that interactively creates or updates a project constitution and keeps related templates in sync. It supports separate languages for conversation and generated project documents.
Skill Claude CodeCodex
A systematic debugging workflow that traces a reported failure back to its root cause before fixing it.
Skill Claude CodeCodex
Read .codexspec/config.yml. Two independent language controls apply (each falls back to language.output, then English).
Skill Claude CodeCodex
A workflow that turns reviewed project knowledge into a reusable command or skill and proposes it to the CodexSpec project through a pull request, which is a reviewed code change.
Skill Claude CodeCodex
Read .codexspec/config.yml. Two independent language controls apply (each falls back to language.output, then English).
Skill Claude CodeCodex
A workflow that carries out a prepared list of software implementation tasks. It can use TDD, or test-driven development, where tests are written before the code, when the task calls for it.
Skill Claude CodeCodex
Read .codexspec/config.yml. Two independent language controls apply (each falls back to language.output, then English).
Skill Claude CodeCodex
A task that expands an approved software plan into specific, traceable implementation tasks. A plan describes the intended approach; task tracking breaks it into work that can be completed and checked.
Skill Claude CodeCodex
A command that creates a structured description for a GitHub pull request or GitLab merge request from a code change and, optionally, a specification file. A pull request or merge request is a proposal to review and merge changes into a shared codebase.
Skill Claude CodeCodex
A shortened requirements-first workflow for small, clearly defined software changes. Requirements-first means deciding and recording what the change must do before implementing it.
Skill Claude CodeCodex
A guide for creating release notes from Git history, including a CHANGELOG.md file and a message for users. It does not choose version numbers or change Git state.
Skill Claude CodeCodex
A design-review add-on that checks whether a software design matches the stated requirements, is feasible, and is ready for implementation planning.
Skill Claude CodeCodex
A review checklist for software implementation plans.
Skill Claude CodeCodex
A review checklist for software specifications and the documents that support them.
Skill Claude CodeCodex
A review checklist for software task plans and their supporting project documents.
Skill Claude CodeCodex
A skill for turning an approved specification into a design document. A specification describes the agreed needs, while a design explains the system's structure and interfaces.
Skill Claude CodeCodex
A skill for turning a discussion into a confirmed requirements document. Requirements describe what a project or feature must do.
Skill Claude CodeCodex
A skill for turning an existing task list into GitHub Issues, which are trackable work items in GitHub.
Skill Claude CodeCodex
A skill that autonomously develops confirmed requirements from a shared product blueprint in document order using a requirements-first process.
Skill Claude CodeCodex
A skill for discussing and maintaining confirmed product requirements in one shared product blueprint.
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: