STDD (Spec and Test Driven Development) methodology, skills, and templates for Claude Code
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.