35,491 mods in this category, of every kind an
agent can take. Each one carries what it costs per session, what the
scan found, and whether it is the original.
VibeHarness — AI vibe coding framework for non-developers. AI acts as a senior developer handling planning, design, development, and testing. All rules are also defined in CLAUDE.md. Applies when starting a new project/feature, or continuing work on a project with docs/biz/, Progress.md, or PROJECTRULES.md.
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…
Activates when user needs help with migrations - database migrations, code migrations, or framework upgrades. Triggers on "migrate", "upgrade framework", "move to new version", "database migration", "schema change", "breaking changes", or migration planning.
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.
AI-powered workflows for positioning, copy, and growth that compound over time. Encodes April Dunford's positioning framework and Matt Lerner's growth framework into structured skills.
This skill should be used when the user asks to "build a dev team lineup", "create dev team lines", "dev team game plan", "dev team strategy", "optimize dev team line combinations", "set up dev team special teams", "plan dev team absences", "update dev team playbook", "update dev team roster", "update dev team power…
Interview the user relentlessly about a technical design or architecture until every major decision is examined, justified, and stress-tested. Use when the user wants to pressure-test a system design, validate an architecture, compare options, or mentions "grill me" in a technical context.
Iterative sprint workflow with delegated implementation and independent verify-repair loops. Finalize each sprint only after every required gate passes.
★not rated 5 27d agoA
tokens not measured
originalMIT
Run an adversarial debate with a cross-model reviewer (Codex or Antigravity/agy) to stress-test a draft, plan, research claim, or design decision. Use this whenever you need structured critique before finalizing decisions.
Produce higher-quality code by breaking a feature into small, focused tasks the coding agent can nail one at a time. Works like an engineering team: feature → milestones (product deliverables) → 30-min tasks with specific files, acceptance criteria, and dependencies. Each task runs in a fresh context — narrow scope…
A workflow for developing one requirement across multiple Git repositories, which are separate code projects. It creates a shared workspace containing the requirement, implementation plan, and selected project copies.
Framework for managing project file context after retros/planning. Trigger after weekly retro + planning complete, after monthly retro + planning complete, or when context feels bloated. Also triggers with "context curation", "clean up project files", "archive old summaries", "what can we remove". Uses fractal…
Plan a feature - gathers context, researches, interviews, identifies risks, outputs PRD. Use when: user says autoplan, /autoplan, or wants to plan a feature with the full research-interview-premortem workflow.
A workflow for coordinating coding agents: one main agent defines the scope and acceptance criteria, then delegates isolated tasks to helper agents and checks their work.
★not rated 5 3mo agoA
tokens not measured
originalMIT
Create lean-spec style GitHub issues as specs for human-AI aligned implementation on the current repo. Use when asked to "create a spec", "write a spec issue", "spec this feature", "spec this", or when planning work that needs a specification before implementation. Follows the lean-spec SDD methodology — small focused…
GSD Utilities — autopilot for phases + milestone runner for sequential objective execution.
★not rated 5 4mo agoA
tokens not measured
originalMIT
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: