A document-review agent that evaluates project documents such as product requirements, feature designs, and architecture plans. It checks whether they are complete, clear, consistent, practical to implement, and measurable.
A Japanese-language sub-agent that checks whether implemented code matches its specifications and reviews code quality, tests, security, and performance.
A command workflow for adding a named feature to an existing project. It creates planning files, studies current code patterns, and works through an implementation task list.
A command for reviewing a specified document with a separate review agent. The review checks completeness, clarity, consistency with other documents, and measurable success criteria when relevant.
A command for creating the six main project documents from existing ideas or an interactive discussion. These documents describe the product requirements, design, architecture, repository structure, development rules, and terms.
A set of guides and templates for defining coding rules and a shared development process. It covers TypeScript and JavaScript practices, testing, Git, code review, and quality checks.
A guide and template for writing a functional design document, which explains how a feature will be built technically. It expects a product-requirements document first and saves the result to docs/functional-design.md.
A guide and template for creating a project glossary. It collects and defines project-specific and technical terms used across the project's documents.
A Japanese-language workflow for planning and carrying out software work with steering documents. It uses requirement, design, and task-list files to guide implementation and record a review afterward.
A project instruction file for mcp-gauge, a Python project that builds MCP servers. It describes the technology choices and a document-first development process.