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.
Generates a structured onboarding backlog that takes a team from zero to publishing verified consumer and provider contract tests on PactFlow — in Jira, GitHub Issues/Projects, or Azure DevOps, or as a manual markdown export. Modelled on the Contract Testing Flywheel: Planning → Requirements → Design → Implementation…
★not rated 6 2d agoA
tokens not measured
originalMIT
Evidence-bound transformation of vague human requirements (Jira ticket, Confluence page, free text, file path) into AI-ready specifications for coding agents. Use WHENEVER user asks to /distill, "analyze requirements", "clarify task", "vague requirements", "ambiguous AC", "task vs bug", "EARS", "Given-When-Then"…
A structured way to guide an AI through difficult problems one step at a time, while keeping the problem bounded and allowing earlier judgments to change.
Locate clarity gaps, business-model breaks, fundraising-story gaps, pitch-deck blockers, and likely investor questions in idea-stage through Series A startups. Use for founder-side review of a startup idea, pitch deck, fundraising material, VC-lens request, investor-meeting preparation, or funding-path fit. Review…
Verified, resumable engineering loops for Claude Code — audit a codebase into an acceptance-gated backlog, route each item to the right model, execute one verified commit at a time.
★not rated 6 2mo agoA
tokens not measured
originalMIT
Route substantive software engineering work through the smallest evidence-driven workflow: close unclear requirements or plans, trace an unknown failure, run a disposable decision probe, deliver and verify a defined code change or refactor, inspect structural redundancy, or draft local work items. Use when software…
Primary Ultra Orchestration entry point for strict Codex-controlled engineering runs. Use this single skill for development, bug fixes, OpenSpec work, multi-file implementation, review/QA-heavy tasks, risk-gated work, or any run that needs automatic mode selection, OpenSpec bootstrap, machine-checkable TaskManifest…
Write the concept for a demo, guide, walkthrough or site-tour video of an app or any public website — the two documents that get approved BEFORE anything is recorded: PLAN.md (the shape: purpose, audience, beat list, spotlight targets, privacy flags, what is out of scope) and SCRIPT.md (every word in playing order…
Deeply grill an idea, decision, design, plan, or implied approach through evidence, failure modes, and user-owned decisions. Use discovery mode for raw ideas, clarification, "grill me", or an unfinished Product Brief; use audit mode for a formed target that needs a verdict or revision. Continue every reply in an…
Mindful-coding OS for any LLM coding agent — faster, quality, scalable output. One invoke configures seven layers (0–6): (0) BRIEF — optional one-page PRD.md (skipped if design.MD/README already covers it, or on request), plus git init, gitignore, and a day-one security baseline; (1) HARNESSING — Handoff.MD…
Specification-Driven Development — a structured workflow for Claude Code that enforces specify → clarify → plan → tasks → implement → validate before writing code.
★not rated 6 6mo agoA
tokens not measured
originalMIT
Create project.md (PRD), brand.md (brand guidelines), and CLAUDE.md (technical config) for any project. Interactive workflow with audit, archetype-based branding, and stack-specific optimization. Supports Laravel, Flutter, Vue2/3, Nuxt2/3, TailwindCSS, Alpine.js, and more.
★not rated 6 7mo agoA
tokens not measured
originalMIT
Pattern taxonomy, agent role combinations, model routing, unit-of-work sizing, review-findings settling, and resilience discipline for Claude Code dynamic workflows. ALWAYS load this skill before authoring or running any Workflow tool script, and ALWAYS load it when the user mentions "workflow" or "ultracode" in any…
Use this skill when the user asks to "write a spec", "create a spec", "spec out", "plan the implementation", "draft an implementation plan", "create a feature spec", "document how to implement", or otherwise needs a detailed implementation specification for a feature, integration, refactor, library, CLI, UI flow, data…
Sima Atlas navigation strategy — standard read order, MCP tool selection, skip-list, write protocol, stop-signals. Activates whenever working in a repo with atlas/graph.json and atlas/blocks/.
Use during Trellis planning when creating or refining a PRD. Applies grill-me style clarification: ask one question at a time, inspect code before asking, provide options and a recommended answer, update prd.md after each decision, verify technical facts against latest knowledge with grok-search-mcp before…
Run a high-stakes decision through a council of five persona-diverse advisors (Contrarian, First-Principles, Expansionist, Outsider, Executor) in parallel, then anonymized peer review, then a chairman synthesis of where they agree, clash, and what to do. Use for real tradeoffs ("council this", "pressure-test this"…
A planning workflow for multi-day or multi-session projects. It creates shared specification, plan, worker-brief, status, and handoff files in the repository before work begins.
This skill should be used when a request is ambiguous, underspecified, conflicting, or high impact. It is intended for vague verbs like optimize, improve, fix, refactor, and add feature; for missing file paths or unknown dependencies; and for risky actions like deploy, delete, overwrite, or migrate. It should not be…
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: