Loading...
Loading...
Found 71 Skills
Use when reviewing how skills performed during a session, when the user wants to analyze skill invocations and identify improvements, or when the user says "skill retro", "review skills", "how did skills do", "improve this skill", or "skill retrospective".
Generates structured OKR plans (Objectives and Key Results) for teams and companies following Google/Intel methodology. Takes company goals, team function, quarter, and current metrics to produce a comprehensive okr-plan.md with objectives, key results, scoring criteria, alignment mapping, tracking cadence, and retrospective templates.
Conduct a project or sprint retrospective by gathering data from status reports and velocity metrics, structuring what went well and what needs improvement, and generating actionable improvement items with owners and due dates. Use at the end of a sprint, after a project phase or milestone, following a significant incident or success, at a quarterly review of ongoing processes, or before starting a similar project to capture lessons learned.
Turn recent work into an engineering retro with shipped work, patterns, and momentum in one place. Use when asked to "weekly retro", "what did we ship", "engineering retrospective", "retro this sprint", or "team retro". Proactively suggest at the end of a work week or sprint. Requires One Horizon MCP.
Create a personal GitHub coding retrospective from a date range and turn it into a short Markdown review. Research commit activity across accessible public and private repositories through the authenticated gh CLI, understand what the relevant repositories and subsystems are for, and write a prose retrospective with stats and highlights. Use when the user asks for a commit review, coding recap, engineering retrospective, GitHub activity story, weekly/monthly/yearly highlights, or a written summary of what their commits achieved.
Sakura Chroma — Vintage Japanese cassette-package aesthetic: cream paper, diagonal rainbow ribbons, condensed bold type, JIS-style spec checkboxes. Anything that should feel like a vintage Japanese cassette package or a TDK / Sony / Sakura Color product catalogue: indie hardware brand decks, music-label release schedules, analog studio retrospectives, zine and magazine pitches, kawaii-tech product launches, creative-studio annual reports.
Perform a comprehensive session retrospective. Use when user says "retro", "retrospective", "회고", or at the end of a working session.
Agile methodologies, issue tracking, and team collaboration tools
Analyze agent-user interaction transcripts to identify context network maintenance needs and guidance improvements. Use after significant agent interactions or to improve context networks.
Closure & Learning (The Learner): Formalize project closure, capture lessons learned, and generate final reports.
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.