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.
Daily entry workflow for NoteFlow OS. Create or update the current week's file, carry over unfinished work, summarize priorities, archive completed weeks, refresh the yearly index, and optionally update public tools.
Install or update Codex SDLC enforcement in the current repository. Use when the user wants this wizard set up as Codex hooks/docs, wants adaptive setup, or needs the generated Codex SDLC files repaired.
APS awareness, truth validation, and reconciliation. Loads plan context, validates selected work against current project truth before implementation, and reconciles plan state at task boundaries.
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.
A project-development process that treats each feature as a complete, trackable cycle from requirements and design to implementation, testing, and proof of completion. It also defines release checks for the whole project.
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.
A command for reviewing the current state of a SpecPilot requirement, where SpecPilot tracks feature requests through planning and implementation stages. It checks the request against its stage and reports what is complete or still missing.
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 2mo 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.
This skill teaches you to use APS (Anvil Plan Spec) — a markdown-based planning format — as persistent memory for complex tasks. APS files live in plans/ and survive context resets, session clears, and handoffs.
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…
TRIZ Physical Contradictions (ccTOPP v4.1) — formulates a physical contradiction with both justifications and resolves it with two documented strategy sets: the Litvin variant (separation in space, time, relation, system level, plus Satisfy and Bypass) and the Zlotin/Zusman variant (separation in space, time, on…
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"…
★not rated 10 1mo agoA97 tokens
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: