Browse reusable Agent Skills, each with a clear purpose and practical guidance.
The world feels messy. Stale tasks, orphan folders, v2 remnants, unsaved sessions — entropy is accumulating and needs to be addressed before it compounds. Scans across all walnuts, then surfaces issues one at a time.
Dashboard of all walnuts -- grouped by ALIVE domain, health signals, what needs attention
The human doesn't know what to work on, or wants to see everything at once. They need the big picture — what's active, what's stale, what needs attention. Renders a live world view grouped by ALIVE domain, then routes to open, tidy, find, history, or map.
Use this skill for vague, high-rework planning work that needs iterative human decisions, such as product design, research planning, technical strategy, PRDs, workflow design, agent design, or skill design. Run concise P2A decision rounds, challenge assumptions early, record decisions in PLAN.md, DECISIONS.md, and OPEN_QUESTIONS.md, then produce FINAL_PLAN.md when converged. Do not use for simple factual Q&A, routine coding fixes, direct execution, translation, writing polish, or one-shot requests.
Use when a Ready feature needs its acceptance criteria discovered before specs are written. Triggers — "/engineer.discover-acs", "/engineer.acceptance-criteria", "discover ACs", "what must this feature do", "figure out acceptance criteria".
Post-meeting debrief — analyzes what happened, compares outcomes to your prep intentions, tracks decision evolution. Use when the user says "debrief", "what just happened in that meeting", "what did we decide", "debrief that call", "post-meeting", "what changed", or right after stopping a recording.
Interactive meeting preparation — builds a relationship brief and talking points before a call. Use when the user says "prep me for my call with", "I'm meeting with X", "prepare me for", "what should I bring up with", "meeting prep", "get ready for my call", or wants to review history with someone before a meeting.
Use before starting pipeline work on a Ready feature the agent hasn't worked yet. Triggers — "/engineer.prime-context", "prime context", "load context before we start", "get up to speed on feature X".
Use to propagate DAE state — turning handoff summaries into visible progress. Triggers — "/engineer.progress-log", "sync progress", "update the tracker", "reconcile the tracker", "refresh feature status".
Use when you need to create a presentation deck to communicate project status.