Command
A technical-design command that turns an approved requirements document into a software design document. It can cover data flows, TypeScript interfaces, database schemas, and API endpoints.
Command
A command that runs a selected range of Kairo tasks in order from start to finish. It includes quality checks, returning to earlier steps when needed, and debugging after all tasks are complete.
Command
A requirements-writing command that turns a feature overview into a detailed specification using EARS, a structured way to describe software requirements and their conditions. It can also define user stories, acceptance criteria, non-functional requirements, and edge cases.
Command
A context-gathering command for Kairo development work. It collects project rules, technology choices, existing specifications, design documents, and optionally related code into a note file.
Command
A task-planning command that breaks an approved technical design into individual implementation tasks and groups them into phases. It considers task dependencies and can optionally register tasks for Claude Code.
Command
The implementation stage of test-driven development known as the Green phase. It changes the code until the tests written in the earlier Red phase pass.
Command
A TDD Red-phase command that creates tests expected to fail before the feature is implemented. The Red phase is the first TDD step, where tests define the behavior that the code must later satisfy.
Command
A command for the refactor stage of test-driven development (TDD), a method where tests guide implementation. It improves code after the tests are passing, using project notes and earlier implementation documents.
Command
A requirements-planning command for test-driven development, or TDD, where tests are written before the implementation. It gathers project context and creates a requirements document with reliability ratings.
Command
A TDD preparation command that gathers a feature's technical context and records it in a note. TDD, or test-driven development, is a method of writing tests before the implementation.
Command
A command for identifying test cases during test-driven development (TDD), where tests are planned before or alongside implementation. It uses documented requirements to create and organize test cases.
Command
A command that turns task files and design documents into a structured, implementation-ready TODO list. TDD means test-driven development, where tests guide the implementation.
Command
A TDD completion-check command that verifies whether a feature's planned test cases and implementation are finished. It reviews the earlier development records and checks that the tests pass.
Skill Claude CodeCodex
A skill for implementing split development tasks in order or by selected task ID, using existing test-driven development commands. It reads task metadata and project notes to choose the work and model settings.
Skill Claude CodeCodex
A project-analysis skill that creates a compact context file describing the codebase, such as its languages, tools, tests, structure, conventions, and architecture. The file is saved as `docs/dev/context.md`.
Skill Claude CodeCodex
A debugging skill for diagnosing and fixing failed tests, build and type errors, runtime crashes, environment problems, and code-style issues.
Skill Claude CodeCodex
A test-first implementation skill for carrying out a planned task or a small direct code change. TDD means writing a test before the code that makes it pass.
Skill Claude CodeCodex
An interactive project-initialization tool that helps choose a technology stack and can create a compatible project context file. Scaffolding means generating the initial project files and folder structure.
Skill Claude CodeCodex
A developer-navigation guide that asks what kind of work you want to do and recommends the appropriate development workflow. It covers planning, implementation, verification, debugging, and web testing.
Skill Claude CodeCodex
A development-planning tool that turns a feature request or product-requirements document into a design and a list of testable tasks. It supports a lightweight mode and a full-spec mode using EARS, a format for writing precise software requirements.
Skill Claude CodeCodex
An orchestration skill that runs a planned range of development tasks through implementation, checking, and debugging. It uses separate helper agents and tracks task dependencies.
Skill Claude CodeCodex
A tool that creates and updates screen specification documents from source code or acceptance criteria. These documents describe individual screens and are saved as Markdown files.
Skill Claude CodeCodex
A verification tool that checks whether all tasks in a development plan are complete and then runs the project’s tests, coverage check, build, lint, and file-size checks. A development plan is a set of tasks for delivering a change.
Skill Claude CodeCodex
A tool that creates Playwright web-test plans from development plans and screen specifications. Playwright is a tool for testing web pages in a browser.