> For the complete documentation index, see [llms.txt](https://cc-code.rongyeliu.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cc-code.rongyeliu.com/agents.md). # agents - [dev](https://cc-code.rongyeliu.com/agents/dev.md): Use this agent when the user provides PRD documents, API documentation, prd-plan specifications, or QA requirements and expects them to be implemented fully without questions or explanations. This age - [prd-plan](https://cc-code.rongyeliu.com/agents/prd-plan.md): Use this agent when the user describes a feature idea, product requirement, or technical initiative and needs a comprehensive plan developed from it. This agent transforms rough concepts and PRDs into - [qa](https://cc-code.rongyeliu.com/agents/qa.md): Use this agent when you need a strict, independent quality gate review of recently written code against the PRD and API documentation. This agent acts as a ruthless test engineer who reads only the PR --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cc-code.rongyeliu.com/agents.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.