A review agent for checking the quality of documents such as product requirements, design specifications, and architecture plans. It evaluates completeness, clarity, consistency, feasibility, and measurable success criteria.
An automated command for adding a new software feature according to an existing project's patterns. It creates planning files, studies the project, generates requirements and design details, and works through the implementation task list.
A command for reviewing a document through a separate review agent. It checks whether the document is complete, specific, consistent, and—when relevant—has measurable success criteria.
A project-setup command that interactively creates six lasting project documents, such as requirements, design, architecture, structure, development guidance, and a glossary.
A Japanese-language guide and template set for defining team coding rules and development processes, including implementation practices, Git use, testing, and code review.
A Japanese-language guide and template for writing a functional design document: a detailed explanation of how a product requirement will be built. It requires an existing product-requirements.md file.
A guide and template for creating a glossary, which is a shared list of project-specific and technical terms with their definitions. It is written in Japanese and expects project documentation such as requirements and architecture files.
A Japanese-language guide for defining a repository structure: the folders and files used to organise a software project. It uses product, functional, and architecture documents to create or update docs/repository-structure.md.
A Japanese-language planning skill that records work instructions, requirements, design decisions, tasks, progress, and final reflections in .steering files.
Project instructions for a TypeScript and Node.js MCP server. They describe documentation, planning, implementation, testing, and project-memory rules, including a specification-driven workflow.