Plan, create, restructure, or execute Linear projects for audits, remediation, production hardening, and parallel agent work. Use when the user asks to create a Linear project, run the Linear skill, execute a Linear plan, organize multi-agent work, preserve a companion ledger, add milestones/dependencies, or close…
Take one feature request from prompt to reviewed, audited delivery in a SINGLE autonomous pass — one runnable Workflow that plans, reviews the plan, builds task by task, cross-reviews the build, and optionally runs a launch audit, then RETURNS the verified findings rather than looping (the user decides any fix round…
Use when a user explicitly asks to workshop, deepen, challenge, or compare a feature's technical design before implementation. Do not use for ordinary coding requests or implementation plans.
Anti-slop agentic engineering co-pilot. Teaches the Research-Plan-Implement (RPI) workflow, context management, quality gates, per-agent isolation, and anti-slop patterns for building software with AI coding agents. Produces agent-workflow.md or project configuration files. Part of the mlops-tabular skill family but…
Executes a written implementation plan by fanning out one Opus 5 low subagent per vertical slice, each spawning Luna Max as a native Codex subagent through the Codex plugin, with regular check-ins, one review phase before the end-to-end phase, and a human-gated merge. Use when the user asks to execute or ship a plan…
Break a complex multi-step plan into the smallest atomic steps, render as a visual HTML artifact, then execute one step at a time with explicit user approval before AND after each step. Each atomic step is self-contained (its description, files, and verify check do not reference other steps) and has a single owner, a…
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Evaluate a developer's engineering problem and recommend the best approach with a score. Use this skill whenever a developer describes an issue they need to solve and optionally proposes an initial idea — the typical case is something like "we have a problem with X, should we do Y?" or "I need to solve X, my idea is…
Decompose initiative Features into detailed User Stories, one folder per HU (body + assets), keep a table of contents in the Feature spec, flag HUs that need enrichment (architect and/or designer), and emit a lean impact-map.yaml.
Decompose complex work into a Beads-backed execution graph with generated WORKGRAPH.md views, then run an NTM-style swarm by ready frontier with no write overlap. Use before parallel execution for large-ish, UI-facing, multi-file, multi-domain, naturally parallel, naturally orchestrated, subgoal-oriented, or…
Use when the user wants to implement all features from a PRD.md with autonomous execution after initial setup and consultant selection — "run autopilot on my PRD", "implement everything from PRD", "autopilot mode", "PRD to production", or wants Claude to work through a feature list unattended. Orchestrates…
Use when the user wants to define verifiable completion criteria for a fuzzy task — writing, strategy, prioritization, design briefs, anything where they can recognize "done" but can't articulate why. Produces a project spec — a list of binary checks that each pass the "stranger test" — that gates whether an output…
Act as a technical partner for planning, dispatching, following, verifying, and explaining local Codex engineering work through the hermes-codex CLI. Use for implementation tasks where Codex should do the coding; do not use as a general orchestrator or for unrelated shell work.
Implement a set of tk tickets in parallel using a DAG-driven agent team with continuous dispatching. Spawns a pool of up to 4 implementers and up to 2 quality reviewers at startup (sized to the input ticket count, so a single-ticket run gets 1 + 1); dispatches tickets as they unblock without wave boundaries. Quality…
Use BEFORE coding any new feature, MVP, pricing/billing change, launch, or pivot. Acts as a product validation gate for solo founders — validates target user, JTBD, pain intensity, current alternative, success metric, distribution channel, structural advantage vs competitors, unit economics with SaaS-graveyard gate…
Generate structured PRD (Product Requirements Document) planning documents optimized for AI-assisted development. Creates discrete, single-conversation tasks with reasoning level estimates to optimize token usage and model selection. Use when users want to plan implementation work, break down features into tasks…
Convert an implementation plan into an interactive HTML review artifact with engagement gates, then hand back an execution-ready brief. Use when the user says "visual planner", "plan room", "review this plan", "make this plan reviewable", or after writing a plan the user should approve before implementation.
★not rated 5 1mo agoA63 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: