37,042 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.
A Chinese-language workflow for exploring requirements, writing implementation plans, and carrying out repeated build-test-commit cycles. TDD means developing with tests as a guide; the description mentions this as part of its loop.
Enforce a claim-to-evidence-to-decision workflow for research projects. Use when planning experiments, implementing research code, analyzing results, changing scope, or preparing weekly updates.
Use when starting Phase 1 of the Beam workflow, or when a new repository needs a plan.md before any scaffolding, AGENTS.md, or technical spec work begins.
Plan or revise experience-design readiness for a UI-bearing SDD Change. Use /sdd-design --plan after Change planning to converge unresolved flow, responsive, component/state, accessibility, or visual direction before implementation, and /sdd-design --revise when candidate-bound implementation, review, comparison, or…
Discipline rules for long-running agent tasks — recurring loops and run-until-done goals. Checkpoint to .loopgoal/state.json, isolate each iteration in a fresh subagent, and write an explicit exit condition.
★not rated 10 26d agoA
tokens not measured
originalMIT
Lightweight development workflow with plan/run/fresh pattern, git workflow integration, PR feedback, and autonomous execution. Optimized for efficiency - minimal hooks, on-demand skills, direct execution.
★not rated 10 3mo agoA
tokens not measured
originalMIT
A guided discussion for analysing review feedback after a proposal has been assessed. It helps separate useful, unclear, or unreasonable comments before producing a revised proposal or response.
An agent named pfc from the HanLi-Chainsea/han-agents project. Its description identifies it as a task coordinator and mentions databases, responsibilities, execution modes, and workflows.
Use this skill when the user wants to create, update, or decompose a product specification. A spec is a triplet of documents — epic.md (what and why), tasks.md (work breakdown), plan.md (execution order). Project-agnostic; drop this skill folder into any repo. Invoke when the user says things like "let's write a…
Use when a plan, spec, design doc, brainstorm, or walkthrough needs review before anyone implements it — especially when it may be over-engineered, over-abstracted, or scoped past a lean MVP. Triggers include "review this plan", "is this over-engineered", "is this too much for an MVP", "sanity check this design"…
use this skill when coordinating complex multi-step or multi-agent work through an autonomous durable kanban dispatch protocol. use it when a user gives only an idea and expects the model to infer product requirements, ux flows, architecture, task decomposition, implementation, review, trace logs, and final results…
Establish disk-backed repository context by reading ASI documentation entrypoints and recording a scoped context digest. Produces onboarding artifacts only (no kickoff, no plan, no execution).
Opinionated workflow skills. Hard gates, not suggestions. Spec through blueprint, implementation, verification, and shipping -- the skills refuse to let you skip steps.
★not rated 10 2mo agoA
tokens not measured
originalMIT
A skill that turns a request, product requirements document, Feishu or Lark document, competitor analysis, notes, or vague product idea into a concise Markdown product requirements document. A PRD explains what should be built and can guide a coding agent.
Advisor Strategy for Claude Code — use Opus-level thinking from Sonnet/Haiku sessions at critical decision points, without switching models.
★not rated 10 6mo 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: