Menú
Use when creating, updating, triaging, or completing repository tasks stored as Obsidian Tasks Markdown lines with
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.
Basado en la clasificación ocupacional SOC
Debug the LangGraph summarize graph (the sole summarize path) -- node walk, validate/repair retry loop, and the LLM attempt trail. Trigger keywords -- LangGraph, summarize graph, graph node, retry, repair loop, attempt_trigger, attempt_index, graph_node, validation failure, self-correction, summarization agent.
Build, ship, and restart the Ratatoskr container on the Raspberry Pi via cross-platform Docker image streaming. Trigger keywords -- pi deploy, raspi, raspberry pi, pi-deploy, ship to pi, deploy production, build-and-deploy-pi.
Coordinate Ratatoskr backend web integration with the external React + TypeScript + Vite frontend. Trigger keywords -- web, frontend, React, Vite, TypeScript, ratatoskr-web, app/static/web, Frost, UI change.
Quick-reference card for all ponytail modes, skills, and commands. One-shot display, not a persistent mode. Trigger: @ponytail-help, "ponytail help", "what ponytail commands", "how do I use ponytail".
Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", and whenever they complain about over-engineering, bloat, boilerplate, or unnecessary dependencies.
Quick-reference card for all ponytail modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /ponytail-help, "ponytail help", "what ponytail commands", "how do I use ponytail".
| name | repo-task-board |
| description | Use when creating, updating, triaging, or completing repository tasks stored as Obsidian Tasks Markdown lines with |
This repository uses Obsidian Tasks-compatible Markdown checkboxes as the canonical task system.
- [ ] #task <imperative task title> #repo/ratatoskr #area/<area> #status/<status> <priority>
#status/backlog#status/todo#status/doing#status/review#status/blocked#status/done#status/dropped🔺 critical · ⏫ high · 🔼 medium · 🔽 lowdocs/tasks/issues/<slug>.md — source of truth — one file per task with YAML frontmatter + canonical line + specdocs/tasks/backlog.md — Obsidian Tasks query view for #status/backlogdocs/tasks/active.md — Obsidian Tasks query view for #status/doing and #status/reviewdocs/tasks/blocked.md — Obsidian Tasks query view for #status/blockeddocs/tasks/dashboard.md — full query hub + Bases view linksdocs/tasks/board.md — Kanban board (visual only; source of truth is issues/)#status/* tag per task; remove the previous one when transitioning.#blocked alongside #status/blocked; add an indented reason below.issues/<slug>.md note; git history is the audit trail.Each task lives in its own file at docs/tasks/issues/<slug>.md (kebab-case imperative title). This is the source of truth.
---
title: Imperative task title
status: doing # backlog | todo | doing | review | blocked | done | dropped
area: auth # auth | api | kmp | sync | ci | frontend | observability | testing | content | scraper | llm | db | docs | ops
priority: high # critical | high | medium | low
owner: Role name
blocks: []
blocked_by: []
created: YYYY-MM-DD
updated: YYYY-MM-DD
---
The per-task note body contains exactly one checkbox line (the canonical task line), followed by spec sections:
- [ ] #task <title> #repo/ratatoskr #area/<area> #status/<status> <priority>
The Tasks plugin picks up this line when querying across the vault — stored inside the per-task note, not in active.md/backlog.md/blocked.md.
new-task.md in docs/tasks/templates/. Fill prompts (title, area, priority, owner). Filename is kebab-case of the title.status: frontmatter field AND update #status/* tag in the canonical line. Always update updated: YYYY-MM-DD.docs/tasks/issues/<slug>.md. Git history is the audit trail.#blocked after #status/blocked in the canonical line; add an indented reason bullet below it; populate blocked_by: frontmatter with filename stems.active.md, backlog.md, blocked.md, and dashboard.md contain only Obsidian Tasks ```tasks query blocks. Do NOT add task lines to these files; add them only inside issues/<slug>.md.
docs/tasks/ for similar tasks.docs/tasks/issues/<kebab-case-slug>.md from docs/tasks/templates/new-task.md.status: in frontmatter and the matching #status/* tag in the canonical line.#repo/ratatoskr, #area/<area>, and a priority marker.