Skip to content

skill registry

Mauricio Rodriguez edited this page Oct 22, 2026 · 1 revision

Skill Registry — MISO-PROYECTO-FINAL-SOLVENTA.wiki

Last updated: 2026-10-22

Sources scanned

  • C:\Users\Mauricio.claude\skills

Contract

Delegator use only. This registry is an index, not a summary. Any agent that launches subagents reads it to select relevant skills, then passes exact SKILL.md paths for the subagent to read before work.

SKILL.md remains the source of truth. Do not inject generated summaries or compact rules by default; pass paths so subagents load the full runtime contract and preserve author intent.

Skills

Skill Trigger / description Scope Path
branch-pr Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review. user C:\Users\Mauricio\.claude\skills\branch-pr\SKILL.md
chained-pr Trigger: PRs over 400 lines, stacked PRs, review slices. Split oversized changes into chained PRs that protect review focus. user C:\Users\Mauricio\.claude\skills\chained-pr\SKILL.md
cognitive-doc-design Design docs that reduce cognitive load. Trigger: writing guides, READMEs, RFCs, onboarding, architecture, or review-facing docs. user C:\Users\Mauricio\.claude\skills\cognitive-doc-design\SKILL.md
comment-writer Write warm, direct collaboration comments. Trigger: PR feedback, issue replies, reviews, Slack messages, or GitHub comments. user C:\Users\Mauricio\.claude\skills\comment-writer\SKILL.md
gentle-ai-bench Trigger: bench, journey, journeys, driven mode, gentle-ai-bench, journey corpus, j-numbers, bench axis. Author and verify gentle-ai bench journeys; go test ./bench never proves driven execution. user C:\Users\Mauricio\.claude\skills\gentle-ai-bench\SKILL.md
issue-creation Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence. user C:\Users\Mauricio\.claude\skills\issue-creation\SKILL.md
judgment-day Trigger: judgment day, dual review, adversarial review, juzgar. Run explicit blind dual review with at most two scoped fix/re-judgment rounds. user C:\Users\Mauricio\.claude\skills\judgment-day\SKILL.md
rdd-defect-workflow Trigger: RDD, receipt-driven development, review authority, receipt/lineage, correction/recovery, delivery gate/kill switch, bounded review defects. Guide work. user C:\Users\Mauricio\.claude\skills\rdd-defect-workflow\SKILL.md
skill-creator Trigger: new skills, agent instructions, documenting AI usage patterns. Create LLM-first skills with valid frontmatter. user C:\Users\Mauricio\.claude\skills\skill-creator\SKILL.md
skill-improver Trigger: improve skills, audit skills, refactor skills, skill quality. Audit and upgrade existing LLM-first skills. user C:\Users\Mauricio\.claude\skills\skill-improver\SKILL.md
systemic-issue-triage Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it. user C:\Users\Mauricio\.claude\skills\systemic-issue-triage\SKILL.md
work-unit-commits Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code. user C:\Users\Mauricio\.claude\skills\work-unit-commits\SKILL.md

Loading protocol

  1. Match task context and target files against the Trigger / description column.
  2. Pass only the matching Path values to the subagent under ## Skills to load before work.
  3. Instruct the subagent to read those exact SKILL.md files before reading, writing, reviewing, testing, or creating artifacts.
  4. If no matching skill exists, proceed without project skill injection and report skill_resolution: none.

📚 Solventa Wiki


🏠 Inicio


📅 Semana 1

Épicas y features · Acta de constitución · Board · Showcase

📅 Semana 2

📐 Documento del alcance (EDT)

📋 Hoja de trabajo

🧪 Estrategia de pruebas

🏗️ Visión de arquitectura

📅 Semana 3

Escenarios de calidad · Historias web/móvil y HA · Priorización · Estrategia de pruebas · Frameworks y ambientes · Plan y tablero · Showcase

🎯 Hoja de trabajo · Escenarios de calidad

📖 Historias de usuario y de arquitectura · Priorización

🧪 Documento de estrategia de pruebas

⚙️ Definición de frameworks y ambientes

🗂️ Plan de trabajo y tablero

🎥 Showcase

Video con evidencias

📅 Semana 4

1. Hoja de trabajo con modelos de arquitectura, patrones detallados y experimento

2. Refinamiento estrategia de pruebas

3. Plan de trabajo y tablero

4. Video con evidencias

📅 Semana 5

1. Documento de arquitectura refinado y detallado

2. Diseño final de los experimentos que permitan validar o refutar las hipótesis de diseño

3. Versión 3 de la estrategia de pruebas

4. Plan de trabajo y tablero

5. Video con evidencias

📅 Semana 6

1. Avance de la ejecución de los experimentos de arquitectura sobre validación de ASR

2. Avances del prototipo versión web/móvil

3. Documento de arquitectura ajustado

4. Plan de trabajo y tablero

5. Video con evidencias

📅 Semana 7

1. Versión final del prototipo

2. Resultados finales de experimentación

3. Documento de arquitectura ajustado

4. Versión inicial del plan de trabajo PF2

5. Plan de trabajo y tablero

6. Video con evidencias

📅 Semana 8

1. Documento final de arquitectura Proyecto I

2. Historias de usuario detalladas del Sprint 1 del Proyecto 2

3. Presentación del prototipo web/móvil final

Guías de usuario

4. Documento de lecciones aprendidas

5. Plan de trabajo y tablero cerrados

6. Video con evidencias


🚀 Proyecto Final 2

📅 Semana 1

1. Configuración del ambiente de trabajo DevOps (55 puntos)

2. Evidencias de avance semanal (15 puntos)

3. Tablero del Proyecto (15 puntos)

4. Video con evidencias (15 puntos)

📅 Semana 2

1. Configuración del ambiente de trabajo DevOps

2. Evidencias de avance semanal

3. Retrospectiva sprint 1


📎 Documentos

Clone this wiki locally