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.
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.
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.
An interactive project configuration manager for CodexSpec. It controls the languages used for conversations, generated documents, command output, commit messages, and templates.
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.
A command that turns reviewed, reusable project knowledge into a shareable command or skill and proposes it for contribution through a human-reviewed pull request, a code change submitted for review.
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.
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.
A release-notes generator that reads Git history and prepares a Keep a Changelog entry, a standard format for recording software changes, plus text for users.
A review process for checking whether a proposed website design is faithful, practical, and ready to plan. It compares the design with the requirements and project files.
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.
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.
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.
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.
A tool that turns a confirmed specification, a written description of what a system must do, into a traceable design document. It follows the project’s language settings when writing the document.
A requirements-discovery command for discussing a proposed software change and recording the confirmed result in a requirements file.
★not rated 5
changed 5d agoA11 tokens
originalMIT
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: