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.
Turn a contested question, research brief, technical choice, or high-impact decision into a source-grounded interactive evidence map. Use when an agent must preserve support, contradiction, qualification, and missing evidence; make every evidence edge traceable to a dated source region; pressure-test a conclusion; or…
First-principles assumption auditor. Deconstructs any decision or belief into irreducible premises, classifies each assumption (fact / convention / belief / interest-driven), ranks them by fragility × impact, and rebuilds conclusions from verified ground truth. Bilingual: responds in the user's language (Chinese or…
Meta-skill that audits health of the entire product launch engine, identifies broken links between phases, and generates improvement roadmaps. Use when: system health, skill audit, launch engine health, are our skills working together, process audit, workflow health check.
End-to-end ABM program design and orchestration for B2B SaaS mid-market and enterprise motions. Use when building a target account list, designing account tiering criteria, planning ABM channel orchestration, coordinating BDR outreach with marketing campaigns, defining ABM measurement frameworks, or running an ABM…
Use only within an active harness lifecycle when pre-stories feasibility review, a pipeline batch drift check, or the SHIP as-built review is current. Do not invoke for ordinary implementation, code review, or general architecture questions.
A strategic analysis approach that examines conflicts through interests, resources, incentives, likely reactions, trade-offs, timing, and fallback plans.
A requirements-analysis agent that turns an informal feature request into structured goals, requirements, constraints, risks, and questions. It prepares this information for later planning.
Drive a long-running, progressively-disclosed plan from a single durable state file. The same invocation initialises a new plan or resumes an existing one, writes state through before replying, dispatches one session at a time on the user's word, and ingests each session's handback. On the user's ask, a live…
Use when starting or resuming a SpecForge task — the orchestrator that scaffolds the task directory, detects the current phase, and routes to the explore, spec, or execute stage skill. Triggers on "specforge", "execution spec", "spec-driven implementation".
Author an executable, phased implementation plan under docs/plans — first gather real context from the repo and docs, debate the ambiguities, trade-offs and open decisions with the human, and only after explicit human confirmation write the plan. Produces Master Plans (a directory with a bootstrap entry point, master…
Interview the user about a plan, design, topic, or decision while checkpointing every answer to a durable markdown capture file. Use when the user says "grill-me-checkpoint", "grill me with checkpoints", asks to be grilled without losing context, wants a discovery session saved to disk, or needs messy thinking…
Produces an unusually strict implementation plan focused on structural simplicity, minimal moving parts, and maintainable execution. Use for a thermo-nuclear plan, plan quality audit, strict planning review, deep implementation plan, or when the user wants an ambitious plan that avoids complexity.
An opinionated product-development-lifecycle harness that lets coding agents deliver work items end-to-end, with minimal human intervention, through a predictable loop of plan, execute, self-review, critic-review and escalate.
★not rated 7
changed todayA
tokens not measured
originalMIT
Use when a problem involves interacting actors, feedback loops, delays, incentives, constraints, unintended consequences, or repeated patterns over time. Use when applying systems thinking, causal loop analysis, system mapping, leverage point identification, or dynamic complexity diagnosis.
Complete methodology for software and business requirements gathering. Use when you need to document a new project, validate a business idea, create technical specifications, or generate complete documentation covering business vision, stakeholders, processes, functional and non-functional requirements, data model…
This skill should be used when the user asks to evaluate, sharpen, red-team, or pressure-test a business idea, offer, market choice, product, or strategic move using Roger Martin and A.G. Lafley's Playing to Win choice cascade. Triggers on phrases including "Playing to Win", "P2W", "where to play", "how to win"…
★not rated 7 4mo agoA159 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: