Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →mohitagw15856/architecture-decision-record
Create an Architecture Decision Record (ADR) for any technical decision.
Passed 16 of 22 test cases with the skill, and 8 of 22 without it.
and 10 more in the full report
8 fixed8 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
Can you draft an Architecture Decision Record (ADR #015) for our team regarding our choice of Apache Kafka over RabbitMQ for system event streaming? We need it structured in Nygard format, including metadata like status (Accepted), context detailing our throughput constraints, pros and cons for both options, why RabbitMQ was rejected, the final decision explanation, positive/negative consequences, risks, and implementation guidance.
| Checked | Without skill | With skill |
|---|---|---|
| The metadata header includes an explicit author field. | Missed | Passed |
| The context section contains a key constraints subsection. | Passed | Passed |
| The risks section is placed as a subsection under consequences rather than a top-level section. | Missed | Passed |
The instructions your model reads when the skill loads.
Esta habilidad produce un Registro de Decisiones de Arquitectura (ADR) completo siguiendo el formato Nygard — el estándar más ampliamente adoptado. Los ADR documentan el razonamiento detrás de decisiones técnicas significativas para que los miembros del equipo futuro entiendan no solo qué se decidió, sino por qué.
Pide al usuario esto si no está proporcionado:
Fecha: [AAAA-MM-DD] Estado: [Propuesto / Aceptado / Deprecado / Supersedido por ADR-NNN] Autor(es): [Nombre(s)] Decisores: [Quién tuvo la palabra final — individuo o equipo]
[3–6 oraciones. Describe la situación, restricciones y fuerzas en juego que hicieron que esta decisión fuera necesaria. Incluye: el problema que se está resolviendo, estado relevante del sistema, restricciones del equipo, presiones de cronograma, o requisitos innegociables. Escribe como si explicaras a alguien que se une al equipo en 18 meses que no tiene contexto previo.]
Restricciones clave:
test cases passed, vs 8 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.