Loading...
Loading...
Found 15 Skills
Write and review feature specifications to staff-engineer standards. Skeleton-first drafting with a hard Open Questions gate, research against market leaders, an implementation breakdown into phases and steps that feeds om-auto-create-pr, and a severity-ranked architectural review format. Use when starting a new spec or reviewing one.
Configure safe agent behavior around PlanetScale MCP, Insights, schema recommendations, and repository work without autonomous production mutation.
Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Use for /show-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping away.
Mission control Kanban interface for managing autonomous Hermes Agent tasks, routines, and workflows
workflow | discuss plan execute verify phase progress
Tell the agents the user is away and can't answer, so they keep working on their own and leave the user's part for the end.
Run one autonomous GitHub issue-triage tick and route issues through the canonical states.
Autonomous execution workflow for complex long-running tasks. This applies to scenarios where users have a complex or vague task (e.g., "Help me figure out X / Help me evaluate Y / Help me organize this pile of stuff / Help me compare N solutions / Help me run a research"), and expect the AI to decompose, execute, and verify the task on its own, only reaching out to the user at critical moments. It enables unattended autonomous execution for 1-2 hours through the process of "Task Confirmation → Task Queue → Batch Execution → Periodic Queue Verification → Triggered Reporting". It is triggered when users say phrases like "Help me figure out / Evaluate / Organize / Compare / Run a research / Run it on your own don't bother me / Long-running task / Run autonomously". **Not applicable to**: UI design (use design-exploration), to-do priority judgment (use priority-judge), article writing (use writing-assistant), backlog management (use backlog-manager), vision exploration (use vision-exploration), naming (use product-naming), implementation coding tasks with clear specs (code directly).
Acts as the persistent supervisor, launching and monitoring the automated review campaign. Use when running a long-running, continuous security review campaign that needs autonomous coordination. Don't use for executing individual review stages directly.
Take a prepared task and run it to 'ready for human review' on your own: code, self-review loop, self-fixes, verification, commits by the team convention, and an honest handover report. Use when the developer hands over a task whose analysis and grilling are already done — trigger on «реализуй задачу», «запускай в работу», «пили», «делай задачу», «бери таску», implement the task, run this task, even when the skill is never named and even right after a grill session ends. NOT for a small change the developer is watching — that is quick-edit. Does not analyse or grill the task, does not estimate it, and does not create the merge request.
Goal Prep for GoalBuddy. Use for broad, long-running, stalled, vague, detailed, planned, or unhealthy Codex or Claude Code work that needs a structured /goal intake, autonomous task discovery, role-tagged Scout/Judge/Worker delegation, one active task, durable receipts, and a PM-owned rolling board that maximizes the chance of a successful goal run.
Keep a one-row-per-decision log during long or unattended runs, and re-read it before each step so the run does not drift from its goal. Use for multi-phase or autonomous work, work a human will review later, or /ds-ledger.