implement-spec

To generate an implementation plan, the system reads requirements and design documents directly from your repository, extracting the necessary specifications to drive end-to-end feature coding, testing, and reviews.

Yes, you can automate end-to-end feature implementation by instructing the system to read your requirements and design documents, which then produces implementation plans, writes code, runs tests, and conducts reviews.

You need to provide requirements and design documents, such as docs/requirements, docs/design, docs/api/openapi.yaml, and CLAUDE.md, so the system can extract specifications and generate actionable implementation plans.

Yes, the implementation workflow supports delegating coding and testing execution to an integrated agent like Sonnet, while the main system performs the final code reviews and validation.

You can manage multiple feature specs, such as REQ-AUTH-001, and their revisions by using the integrated revise-spec functionality to maintain and update your end-to-end implementation workflow.

The best way to turn OpenAPI specifications into working code is to let the system read your docs/api/openapi.yaml alongside design documents to automatically generate implementation plans, write the code, and run tests.