tool-module-builder

What problem does it solve?

This Skill prevents backend tool-module development from drifting into legacy assumptions by forcing a single-module implementation to be derived from the architect task, design document, and test document.

Core Features & Use Cases

• Doc-driven module contract: Converts the task list, design document, and test document into an explicit API contract (paths, permissions, request/response schemas, validation, error cases).
• Architecture-aligned implementation: Implements exactly one backend tool module within the repository’s module architecture and separation of layers (interface/application/persistence).
• Verification through module tests: Produces or repairs module tests so behavior is verifiable against the test document, including happy paths and documented failures.

Quick Start

Ask: “Using the architect task, the design doc, the test doc, and the task list, implement or repair exactly one backend tool module named by the task, strictly following the repository module architecture and making the tests match the test document.”