Skill Claude CodeCodex
An automated workflow that takes a software task from an issue, document, URL, or plain description through clarification, specifications, planning, coding, testing, review, design updates, and pull-request creation.
Skill Claude CodeCodex
An automated workflow that takes a software task from an issue, document, URL, or plain description through clarification, specifications, planning, coding, testing, review, design updates, and pull-request creation.
Skill Claude CodeCodex
A guide for creating a pull request from the current code branch to the repository's primary branch. A pull request is a proposal to merge reviewed changes into the main line of development.
Skill Claude CodeCodex
A guide for creating and managing PLAN documents: task lists that describe the work planned for one development session. It is part of STDD, or Spec and Test Driven Development.
Skill Claude CodeCodex
A Japanese-language guide and template for writing REQUIREMENTS.md files, which record what a feature must do and why. It follows STDD, meaning Spec and Test Driven Development, and covers business, functional, and non-functional requirements.
Skill Claude CodeCodex
A Japanese-language skill for creating technical design and test-plan documents, plus shared architecture, database-table, API, and design specifications. It follows STDD, or Spec and Test Driven Development, where requirements guide the design and tests.
Skill Claude CodeCodex
A tool that turns written requirements into simple HTML wireframes, or rough screen layouts, showing pages, controls, labels, and common states.
Skill Claude CodeCodex
A guided process for adding STDD, or Spec and Test Driven Development, to an existing working project. It records progress in a plan and moves through documentation, feature analysis, implementation, and review.
Skill Claude CodeCodex
A set of development principles based on Kaizen, the practice of making small continuous improvements. It covers preventing errors, avoiding unnecessary work, reusing proven patterns, and refactoring step by step.
Skill Claude CodeCodex
A process that examines an existing project and creates shared specification documents for its business requirements, architecture, database tables, and APIs, when APIs exist.
Skill Claude CodeCodex
A guide for documenting and testing an existing software feature or page by studying how its code already works. It creates requirement, design, and test documents that describe the current behavior rather than an imagined future version.
Skill Claude CodeCodex
A workflow for reviewing an existing pull request with two specialist agents: one focused on testing and logic, and one focused on code quality and security. A pull request is a proposed code change submitted for review before merging.
Skill Claude CodeCodex
Software design guidelines based on Clean Architecture, which separates code by responsibility, and domain-driven design, which models the business concepts directly. It also recommends a library-first approach and consistent naming.
Skill Claude CodeCodex
A project-specific format for writing software specifications, including requirements, technical design, tests, naming, and document layout. It adapts the STDD (Spec and Test Driven Development) templates to an existing or new project.
Skill Claude CodeCodex
A consistency checker for software specifications, tests, and implementation. It compares stable requirement and feature IDs across those layers to find missing or mismatched parts.
Agent Claude Code
A specialist agent that reviews code for project rules, quality, security, performance, and responsive behavior. Responsive behavior means checking that an interface works across small mobile screens and larger desktop screens.
Agent Claude Code
An implementation agent that follows specification- and test-driven development, where requirements and tests guide the code. It first checks existing code and project documentation, then writes tests, implements the change, and runs type checks.
Agent Claude Code
An implementation-planning agent for STDD, or Spec and Test Driven Development: a method that plans work from written requirements and tests before implementation. It reads requirements, technical design, and test-plan documents to create a task plan.
Agent Claude Code
A quality-assurance specialist that runs software tests, checks that requirements and code agree, and verifies key browser actions with Playwright, a browser-testing tool.
Agent Claude Code
A Japanese-language specialist role for reviewing REQUIREMENTS.md, a document that states what a software feature must do and why. It checks completeness, structure, use cases, acceptance criteria, project conventions, and compliance with a single source of truth.
Agent Claude Code
A specialist agent that turns issues and existing design information into REQUIREMENTS.md files. These documents describe what a feature should do and why, without defining its technical implementation.
Agent Claude Code
A specialist agent that reviews technical design and test documents against requirements and project rules. It checks documents such as TECH_DESIGN.md and TEST_PLAN.md for coverage, consistency, and current-spec accuracy.
Agent Claude Code
A technical-planning specialist for STDD, or Spec and Test Driven Development, an approach that defines requirements and tests before deciding how to build the feature.
Agent Claude Code
A specialist role for reviewing tests during the Red stage of Spec and Test Driven Development, where tests are written before the implementation. It checks whether tests actually verify the stated requirements.
Hook Claude Code
Runs before the agent uses a tool for Bash, Edit, Write and MultiEdit tool calls, executing pre-push-check.sh and spec-first-check.sh (2 commands). From careerchain-ys/stdd.