© 2026 YOLOX SYSTEM. ALL RIGHTS RESERVED.
Gives your agent the ability to document critical architecture choices using a structured ADR format optimized for both machine parsing and human reference.
When your team makes a significant technical choice that needs a clear trail
When you want to document why a specific alternative was rejected
When you need to track the positive and negative consequences of a decision
Provide the context, technical constraints, and business requirements for the decision
Describe the chosen solution and the clear rationale behind its selection
List any alternatives considered and the specific reasons they were rejected
Review and save the formatted ADR file to your project's /docs/adr/ directory
You
We've decided to move from REST to GraphQL for our mobile API. Document this.
Agent
I'll generate ADR-0004 for your GraphQL migration. I'll include the performance and flexibility benefits as POS codes, and document the added complexity as a NEG code. I'll also record why we rejected staying with REST, and save it to /docs/adr/adr-0004-graphql-migration.md.
Gives your agent the ability to define clear, unambiguous, and AI-ready specifications for schemas, tools, architecture, and more, ensuring a machine-readable project foundation.
Gives your agent the ability to create an llms.txt file that serves as a high-level navigation guide for LLMs to understand your repository's purpose and structure.
Gives your agent the ability to implement and troubleshoot create technical spike tasks.
Gives your agent the ability to act as a senior expert, creating appealing, informative, and professional README.md files that effectively showcase your project.
Gives your agent the ability to generate a comprehensive AGENTS.md file that provides technical context and instructions for AI coding tools to work effectively on your project.
© 2026 YOLOX SYSTEM. ALL RIGHTS RESERVED.