skills

Use this skill when the user asks to "brainstorm", "brainstorm ideas", "generate ideas about", "what options do we have for", "explore solutions", "ideation session", "lluvia de ideas", "hacer un brainstorming", "generar ideas", "explorar opciones", "qué alternativas tenemos", or mentions "brainstorm" while solving a technical problem, designing a feature, choosing an approach, shaping a product idea, or making a strategic decision. This skill turns unclear ideas into options, tradeoffs, and a Markdown design brief. Do not use it for implementation after a direction is already chosen, normal code review, factual Q&A, commit messages, or premortems.

Use this skill when the user asks to "write a commit message", "generate a commit", "create a commit", "commit message for this change", "what should my commit say", "write the commit", "escribe el commit", "mensaje de commit", "generar commit", "cómo hago el commit de esto", or when the user is about to commit code and needs a message. Also use when the user runs "git commit" and asks for help with the message. Generate paste-ready Conventional Commit messages; do not use this skill for PR descriptions, changelogs, release notes, code review, or explaining diffs unless the user asks for a commit message.

Explicit-only skill for development and engineering premortems. Use this skill only when the user explicitly invokes "$development-premortem", "use development-premortem", "run a development premortem", "development-premortem this", "premortem this architecture", "premortem this migration", "premortem this deploy", "premortem this technical plan", "haz un development-premortem", "premortem técnico", or "premortem de desarrollo". Stress-test technical work before build, merge, rollout, migration, architecture change, integration, deployment, or infrastructure change by assuming it failed in production and working backward. Do NOT trigger on normal code review, debugging help, architecture brainstorming, "what are the edge cases?", "will this scale?", "what could break?", or ordinary technical discussion unless the user explicitly asks for development-premortem.

Explicit-only skill for product and business premortems. Use this skill only when the user explicitly invokes "$product-premortem", "use product-premortem", "run a product premortem", "product-premortem this", "premortem this launch", "premortem this pricing change", "haz un product-premortem", or "premortem de producto". Stress-test a product, launch, pricing change, positioning shift, hire, partnership, strategy, or business decision before commitment by assuming it failed and working backward. Do NOT trigger on broad phrases like "what could go wrong", "am I missing anything", "poke holes in this", simple feedback requests, ordinary product/design discussion, LLM Council requests, or multi-perspective requests unless the user explicitly asks for product-premortem.

Use this skill when the user asks to "specific trigger phrase", "another realistic trigger", or needs a clearly defined workflow that this skill handles better than general agent behavior.