scan-gaps

Estrellas24

Forks3

Actualizado9 de mayo de 2026 a las 02:45

Analyze gaps in user-facing features and desirable characteristics, developer-facing tooling and desirable characteristics, and other opportunities not currently tracked in the project's backlog. Use when the user asks you to help identify opportunities to improve the system.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

ooloth

ooloth/dotfiles

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Especialistas en gestión de proyectosOperaciones empresariales y financieras·SOC 13-1082

SKILL.md

readonly

name	scan-gaps
description	Analyze gaps in user-facing features and desirable characteristics, developer-facing tooling and desirable characteristics, and other opportunities not currently tracked in the project's backlog. Use when the user asks you to help identify opportunities to improve the system.
effort	high

Your task

Use up to 50 subagents to explore the current codebase (or subsection if the user specified a smaller scope)
Identify opportunities to improve user- or developer-facing characteristics and address fundamental flaws
Study the user's trekker, Jira, Monday, GitHub issues or other backlog (if any) to see what opportunities are already tracked
Report the top untracked user-facing and developer-facing opportunities
Generate a self-contained HTML slide deck of the findings:
- mkdir -p .outputs/<yyyy-mm-dd>
- Write the report to .outputs/<yyyy-mm-dd>/scan-gaps.html — clean minimal styling, one slide per opportunity plus a summary/title slide, keyboard arrow-key and click navigation between slides
- open .outputs/<yyyy-mm-dd>/scan-gaps.html

Más de este repositorio

mismo repositorio

write-pr-description

ooloth/dotfiles

Voice guide for writing PR descriptions. Use this skill for ALL PR creation and updates (via gh CLI or editing existing PRs). Contains your specific voice rules, anti-patterns, examples, and workflow. Never write PR descriptions without invoking this skill first.

2026-06-1124

commit

ooloth/dotfiles

Commit the changes in the working tree. Only invoke when the user explicitly signals to commit ("commit", "/commit", etc.). Never invoke this skill on your own initiative — implementation approval is not a commit signal.

2026-06-1124

review-code

ooloth/dotfiles

Standalone code review for any scope — PR number, branch, file paths, or current changes. Synthesizes intent, runs 10 parallel specialized agents, and presents actionable findings with a verdict. For PR scope, optionally posts the review to GitHub with inline comments.

2026-06-1024

prove-it-works

ooloth/dotfiles

Survey observable paths, run the real system, capture evidence, and surface gaps. TRIGGER when asked to prove a change works or write a QA plan.

2026-06-1024

handoff

ooloth/dotfiles

Tell the next agent everything they need to know to continue your work.

2026-06-0624

write-ticket-description

ooloth/dotfiles

Voice guide for writing issue/ticket/task/epic descriptions. Use this skill for ALL issue creation — GitHub issues, Jira tasks, Monday tasks, Linear tasks, and epics. Contains section structure, voice rules, and anti-patterns. Never write ticket descriptions without invoking this skill first.

2026-06-0224

name	scan-gaps
description	Analyze gaps in user-facing features and desirable characteristics, developer-facing tooling and desirable characteristics, and other opportunities not currently tracked in the project's backlog. Use when the user asks you to help identify opportunities to improve the system.
effort	high

Your task

Use up to 50 subagents to explore the current codebase (or subsection if the user specified a smaller scope)
Identify opportunities to improve user- or developer-facing characteristics and address fundamental flaws
Study the user's trekker, Jira, Monday, GitHub issues or other backlog (if any) to see what opportunities are already tracked
Report the top untracked user-facing and developer-facing opportunities
Generate a self-contained HTML slide deck of the findings:
- mkdir -p .outputs/<yyyy-mm-dd>
- Write the report to .outputs/<yyyy-mm-dd>/scan-gaps.html — clean minimal styling, one slide per opportunity plus a summary/title slide, keyboard arrow-key and click navigation between slides
- open .outputs/<yyyy-mm-dd>/scan-gaps.html