Loading...
Loading...
Found 179 Skills
Drill open decisions one at a time — present the most important decision not yet clarified, give the top four choices, state a preference, ask the user. Use when the user says "next decision", "one decision at a time", or a plan has several unresolved choices. Differentiator: forward-looking; the decisions skill is retrospective (choices already made). Can be invoked with /next-decision.
Reflective sleep-and-dream heuristic for learning from recent experience. Use when the user asks to sleep on something, dream about it, reflect overnight, learn from yesterday, or extract lessons after a meaningful task, conversation, or debugging session. Avoid for first-pass analysis, simple factual lookups, direct execution, or tasks that do not benefit from reflection.
Closure & Learning (The Learner): Formalize project closure, capture lessons learned, and generate final reports.
Agile methodologies, issue tracking, and team collaboration tools
Wrap up completed work. Council validates the implementation, then extract learnings. Triggers: "post-mortem", "wrap up", "close epic", "what did we learn".
/em -postmortem — Honest Analysis of What Went Wrong
Cross-meeting archaeology skill. Consumes multiple meeting recaps (or raw notes) over a period and surfaces patterns invisible in any single meeting. Shows how decisions evolved, who has been saying what, where threads are stalling, and where contradictions have emerged. Produces a plain-text timeline, themes with confidence markers, stakeholder position tracking, consolidated decision list, contradiction flags, open items, narrative summary, and prioritized follow-ups.
Surfaces and assesses hidden assumptions behind decisions, designs, or recurring patterns — use when reviewing a design before committing, reflecting on recurring problems, or questioning why the same kinds of issues keep appearing
Film light leak + grain noise + 16:9 letterbox + large serif font, cinematic opening / chapter card
Turn a finished, failed, or disappointing work cycle into portable lessons, anti-patterns, quality gates, and next-cycle vocabulary. Use after a build, QA pass, demo, user complaint, or abandoned attempt when the useful output is what the next pass must learn rather than the code itself.
Captura de aprendizaje al cierre de cualquier corrida de producto o build: convierte lo aprendido (qué validó, qué falló, por qué se decidió lo que se decidió) en conocimiento retornable con criterio de aplicación explícito — enrutado por la frontera de datos (porqué durable → Wachi Brain git-first · gotcha de código → Engram con ticket · hecho de fábrica → ya quedó en RumIAndo) — y poda el conocimiento viejo (mantener/actualizar/consolidar/reemplazar/borrar). Usar al cerrar una ficha (SHIPPED o rechazada), después de una sesión de validación reveladora, al resolver un ADR, o periódicamente para podar. La primera resolución cuesta 30 minutos; documentada, la próxima cuesta 2.