Jose Andrés González Guevara

Generate Architecture Decision Records (ADR) in Markdown format. Use this skill whenever the user wants to create, write, draft, or document an architectural decision, a technical decision record, or an ADR. Triggers include "ADR", "architecture decision record", "decision record", "architectural decision", "document a decision", "technical decision", "record a decision", "create an ADR", "write an ADR", or any request to formally capture why a technical or architectural choice was made. Also trigger when the user says things like "we decided to use X instead of Y and I want to document it", "I need to justify this architecture choice", or "let's record this decision for the team". También se activa en castellano: "ADR", "registro de decisión arquitectónica", "decisión arquitectónica", "decisión técnica", "documentar una decisión", "registrar una decisión", "crear un ADR", "escribir un ADR", "registro de decisión", "decisión de arquitectura", "justificar una decisión técnica", "documentar por qué elegimos esta solución", "crear registro de decisión".

Generate lightweight Product Requirements Documents through a fast, 5-phase guided conversation. Use this skill for MVPs, internal tools, small-to-medium features, or early-stage ideas that need structure but not ceremony. Trigger when the user mentions "PRD light", "light PRD", "quick PRD", "lightweight PRD", "simple PRD", "mini PRD", "short PRD", "brief PRD", "MVP requirements", "MVP spec", "quick requirements", "rough PRD", or asks to "document what we need to build quickly". También se activa en castellano: "PRD ligero", "PRD rápido", "PRD simple", "PRD corto", "mini PRD", "requerimientos ligeros", "requerimientos rápidos", "especificación rápida", "especificación simple", "PRD MVP", "requerimientos del MVP", "documento de requerimientos simple", "PRD breve".

Generate technical Product Requirements Documents (PRD) through an interactive, phase-by-phase guided process. Use this skill whenever the user wants to create a PRD, write product requirements, define a technical product spec, document a new feature or product from a requirements perspective, or needs help structuring what they want to build before starting development. Also trigger when the user mentions "product requirements", "PRD", "technical spec for a product", "feature spec", or asks to "document what we need to build". This skill validates each section as the user writes it and produces a complete PRD document at the end. También se activa en castellano: "PRD", "requerimientos de producto", "documento de requerimientos", "especificación de producto", "requisitos técnicos", "crear un PRD", "escribir un PRD", "definir requerimientos", "documentar producto", "requerimientos del producto", "especificación técnica del producto", "qué necesitamos construir", "requisitos del producto", "escribir requerimientos".

Comprehensive catalog of 60+ refactoring techniques for Java code based on Martin Fowler's "Refactoring" and Alexander Shvets' "Refactoring Guru". Use this skill whenever the user asks to refactor Java code, improve code quality, eliminate code smells, simplify conditionals, restructure classes, improve API design, or apply any named refactoring technique. Also trigger when the user mentions code smells, legacy code improvement, clean code practices, SOLID principles in Java, or asks "how can I improve this code". Covers Java 8 and Java 11+ examples for every technique. Even if the user just pastes Java code and asks for improvement suggestions, use this skill to identify applicable techniques. También se activa en castellano: "refactorizar", "refactorizar código Java", "mejorar este código", "malos olores del código", "olores de código", "código sucio", "limpiar código", "simplificar condicionales", "principios SOLID", "cómo mejorar este código", "código limpio", "reestructurar clase", "mejorar calidad del código", "técnica de refactorización", "extraer método", "renombrar variable", "mover método", "eliminar código duplicado", "reducir complejidad", "mejorar legibilidad", "reorganizar código".

Cross-language catalog of 62+ refactoring techniques based on Martin Fowler's "Refactoring" and Alexander Shvets' "Refactoring Guru". Detects the project's language automatically and provides idiomatic examples. Works with Java, Python, TypeScript, JavaScript, C#, Go, Kotlin, Ruby, PHP, Rust, Swift. Use this skill whenever the user asks to refactor code, improve code quality, eliminate code smells, simplify conditionals, restructure classes, improve API design, or apply any named refactoring technique. Also trigger when the user mentions code smells, legacy code improvement, clean code practices, SOLID principles, or asks "how can I improve this code". Even if the user just pastes code and asks for improvement suggestions, use this skill to identify applicable techniques. También se activa en castellano: "refactorizar", "refactorizar código", "mejorar este código", "malos olores del código", "olores de código", "código sucio", "limpiar código", "simplificar condicionales", "principios SOLID", "cómo mejorar este código", "código limpio", "reestructurar clase", "mejorar calidad del código", "técnica de refactorización", "extraer método", "renombrar variable", "mover método", "eliminar código duplicado", "reducir complejidad", "mejorar legibilidad", "reorganizar código". For Java-specific examples with Java 8 and Java 11+ patterns, use refactor-java.

Interactive skill for creating RFC (Request for Comments) documents as Markdown files. Use this skill whenever the user wants to create an RFC, write a technical proposal, draft a design document, create a technical spec, or write a feature proposal. Triggers include: 'RFC', 'rfc', 'request for comments', 'design doc', 'technical proposal', 'feature proposal', 'tech spec', 'architecture proposal', 'engineering proposal', or any request to document a technical decision with sections like motivation, design, alternatives, and drawbacks. This skill guides the user through an interactive interview process, asking questions step by step, and then generates a polished RFC Markdown file. Use this even if the user just says 'I want to propose a new feature' or 'I need to document a technical decision' — these are RFCs in disguise. También se activa en castellano: "RFC", "propuesta técnica", "documento de diseño", "especificación técnica", "propuesta de arquitectura", "propuesta de ingeniería", "crear un RFC", "escribir un RFC", "proponer una feature", "documentar una decisión técnica", "propuesta de feature", "diseño técnico", "quiero proponer un cambio técnico", "necesito documentar una decisión".

Creates agent-ready GitHub issues structured for Spec-Driven Development (SDD). The issue contains all the information the SDD orchestrator needs to run a full automated cycle: intent, scope, constraints, acceptance scenarios, and technical context. Trigger: When creating a GitHub issue for SDD, writing a buildable issue, preparing work for the orchestrator, or when the user says "create an issue", "write a ticket", "I need to build X". Also trigger when the user references an existing issue number and wants to enrich it for SDD consumption.

Generate well-structured Jira Spike tickets in Jira Markdown syntax. Use when the user wants to create a spike, investigation task, technical research task, or feasibility study for Jira. Triggers include requests like "create a spike", "write a Jira spike", "I need a spike for [topic]", or any request to document a technical investigation or research task as a Jira ticket. También se activa en castellano: "crear un spike", "escribir un spike", "spike de investigación", "tarea de investigación", "investigación técnica", "spike en Jira", "necesito un spike para", "estudio de viabilidad", "ticket de investigación", "spike técnico", "hacer un spike", "documentar investigación", "crear tarea de investigación".

Expert in pedagogical book chapter synthesis. Use this skill WHENEVER the user wants to summarize a book chapter, analyze text or document content, study a chapter, extract key ideas from a reading, or when they mention words like "summary", "chapter", "book", "analyze this text", "summarize this", "cornell", "TL;DR" of long-form content. Also trigger when the user uploads a PDF, EPUB, or document and asks to understand or study it in parts. También se activa en castellano: "resumen", "resumen del capítulo", "resumir esto", "resumir el capítulo", "analizar este texto", "capítulo", "libro", "ideas clave", "resumen del libro", "estudiar el capítulo", "síntesis", "notas cornell", "extraer ideas principales", "dame un resumen", "qué dice este capítulo", "resumir documento", "analizar lectura".

Implements the TCR (Test && Commit || Revert) methodology for ultra-short, safe commits during refactoring and development. Use this skill whenever the user wants to apply TCR, make atomic commits after each green test, commit frequently during refactoring, or follow a test-driven commit workflow. Also trigger when the user mentions "TCR", "test and commit", "commit after each test", "atomic commits", "micro commits", "revert on red", or asks for a disciplined commit cadence during code changes. También se activa en castellano: "test y commit", "commitear tras cada test", "commits atómicos", "micro commits", "revertir en rojo", "commits pequeños", "flujo TCR", "metodología TCR", "test verde y commit".

Java-specific testing techniques for legacy code based on "Working Effectively with Legacy Code" by Michael Feathers. Use this skill when the user needs to write Java tests for existing code without coverage, break dependencies to make Java code testable, apply Characterization Tests with JUnit, use Sprout/Wrap techniques to safely add functionality, deal with Singletons/statics/final classes in Java tests, find Seams in Java code, apply Sensing or Separation to isolate behavior, use TDD in legacy Java contexts, or any situation where legacy Java code hinders testing. Covers JUnit 4, JUnit 5, Mockito, and Java versions from 8 through 21+. This skill is Java-only. For other languages (Python, TypeScript, C#, Go, etc.), use the test-legacy skill instead. Also applies when the user mentions "code without tests", "I can't test this class", "coupled dependencies", "God class", "break dependencies", "characterization test", "Sprout Method", "Wrap Method", "Extract and Override", "Pinch Point", "Seam", "Sensing", "Separation", "Programming by Difference", "Pass Null", "Scratch Refactoring", "Effect Sketch", "Cover and Modify", "Edit and Pray", "Golden Master", "ApprovalTests", or similar techniques. Tambien se activa en castellano: "codigo sin tests", "no puedo testear esta clase", "codigo legado", "romper dependencias", "dependencias acopladas", "clase Dios", "test de caracterizacion", "metodo Sprout", "metodo Wrap", "extraer e implementar", "punto de pellizco", "costura", "cubrir y modificar", "editar y rezar", "codigo heredado", "hacer testeable", "golden master", "prueba de aprobacion", "TDD en codigo legado".

Multi-language legacy code testing techniques from Michael Feathers' "Working Effectively with Legacy Code." Detects the project's language and test framework to generate idiomatic tests. Works with Java, Python, TypeScript, JavaScript, C#, Go, Kotlin, Ruby, PHP, Rust, Swift, and more. Use this skill whenever the user struggles to test existing code — even if they don't mention Feathers by name. Triggers: code without tests, untestable classes, coupled dependencies, God classes, breaking dependencies, characterization tests, Sprout/Wrap methods, Seams, Sensing, Separation, Golden Master, Effect Sketches, Pinch Points, or any situation where legacy code blocks testing. Also triggers on "codigo sin tests", "codigo legado", "no puedo testear", "romper dependencias", "hacer testeable", "test de caracterizacion". For Java-specific JUnit/Mockito version matrices and compiled reference examples, use test-legacy-java.

Generates JUnit 5 and Mockito unit tests following Java project conventions like naming, structure, and assertion styles. Use when the user requests (1) Creating new Java unit tests, (2) Testing Java services/components with Mockito mocks, (3) Adding test coverage to Java code, (4) Writing JUnit parameterized tests, (5) Testing exceptions or edge cases in Java. Triggers include mentions of "JUnit", "Mockito", "AssertJ", "@Test", "@ExtendWith", "MockitoExtension", or testing-related tasks in a Java project. This skill is Java-only (JUnit 5 + Mockito + AssertJ). For other languages, use the unit-tests skill instead. También se activa en castellano: "test unitario", "tests unitarios", "crear tests", "añadir tests", "prueba unitaria", "pruebas unitarias", "escribir un test", "hacer tests", "testear esta clase", "test con Mockito", "mockear dependencias", "cobertura de tests", "no tiene tests", "añadir cobertura", "crear pruebas", "test parametrizado", "test de excepción", "testear el servicio", "cubrir con tests", "generar tests".

Generates idiomatic unit tests in any language. Detects the project's language and test framework automatically. Works with Java, Python, TypeScript, JavaScript, C#, Go, Kotlin, Ruby, PHP, Rust, Swift. Use this skill whenever the user needs unit tests — even if they just say "add tests" or "cover this class" without specifying a framework. Triggers: "unit test", "write tests", "add tests", "test coverage", "mock", "stub", "spy", "test this", "cover this", or any testing-related request. Also triggers on: "test unitario", "crear tests", "añadir tests", "prueba unitaria", "testear", "mockear", "cobertura", "cubrir con tests", "generar tests". For Java-specific JUnit 5 + Mockito + AssertJ patterns with compiled reference examples, use unit-tests-java.

Extract, transcribe, and summarize audio or video files using OpenAI Whisper. Use this skill whenever the user wants to transcribe audio or video, extract what was said in a recording, get a transcript of a meeting/interview/lecture/podcast, or generate a summary of spoken content. Also trigger when the user mentions files like .mp3, .mp4, .wav, .m4a, .ogg, .flac, .webm, .mkv, .mov and wants text out of them. Generates a .md file with an AI summary followed by the full literal transcript. También se activa en castellano: "transcribir", "transcripción", "extraer audio", "qué dice este audio", "transcribir reunión", "transcribir entrevista", "pasar audio a texto", "resumir grabación", "transcribir este video", "extraer texto de audio", "transcript", "whisper", "grabar y resumir".

Generate structured Jira acceptance criteria in Gherkin format (Given/When/Then). Use when the user wants to define, write, or create acceptance criteria for a Jira task, story, or ticket. Triggers include "acceptance criteria", "AC", "write the ACs", "define ACs for", or any request to document expected behavior as testable conditions. También se activa en castellano: "criterios de aceptación", "CA", "escribir los criterios", "definir criterios de aceptación", "crear los CA", "ACs del ticket", "criterios Gherkin", "dado cuando entonces", "condiciones de aceptación", "escribir los ACs", "generar criterios", "criterios para esta historia", "definir los criterios".