Design or audit an agentic AI workflow with process-first guardrails: deterministic spine, evidence, gates, monitoring, and recovery before autonomy. Use when a user is designing an AI workflow, agent flow, workflow automation, vendor AI deliverable, or autonomy review.
Write specifications precise enough for autonomous AI coding agents to implement without human intervention. Use when: user wants to spec a feature, system, or tool for agent implementation. Do NOT use for: writing code directly (let agents implement), creating skills (use skill-creator).
Diagnose, score, map, visualize, or accept an AI agent or workflow using a public closed-loop readiness report. Use for agent specs, automation workflows, vendor proposals, and agentic builds.
Route prompts by task-demand surface before spending tokens. Use when deciding which model, tool lane, verifier, or human gate a task needs; when a task involves local/private models, small/cheap models, coding, agents, long context, media, compliance, or high-stakes verification.
Universal codebase operations: analyze, organize, and architecturally deepen any repo. Two commands: /organize for read-only analysis and /deepen for multi-agent refactoring. Use when the user wants a codebase scan, deep module scoring, dependency mapping, architectural improvement, or code-to-skill conversion.…
Build three context layers (structural, semantic, philosophical) for a module or service, producing production-ready artifacts: a module manifest, behavioral contracts, and a decision log. Use when: (1) a dark code audit identifies high-risk modules, (2) proactively documenting any critical service, (3) a module's…
Relentlessly interview the user to stress-test a plan, design, docs, or existing codebase before building. Use when the user says "grill me", "grill docs", "grill with docs", wants codebase/domain alignment, wants a CONTEXT.md or ADR-backed interrogation, or needs shared language before implementation.
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
Use when the user asks to "make sense," "make sense of this," "make it make sense," "this doesn't make sense," or otherwise requests structured comprehension of a confusing idea, decision, plan, document, system, unfamiliar domain, or stuck situation. Produces a visible router, a declared artifact shape, trust-marked…
Use when a user asks whether a new external thing, idea, article, tool, repo, framework, competitor move, workflow, or opportunity is worth caring about now. Runs a memory-first triage, maps where the thing applies, and returns exactly one verdict: GO-now, PARK, or KILL.
Comprehension instrument for AI-mediated work. Triggers when the user says "seeit", "show me the shape", "make this visible", or asks to see/understand/visualize a project, codebase, agent workflow, spec, or AI build at a structural level. Use this skill whenever the user wants to understand the SHAPE of something the…
Turn any repository into a structured, skill-like decomposition that stays alive for context at all times. Invoke during spec diagramming, brownfield exploration, or at any point in a repo's lifecycle. Auto-creates a skill-pack directory with PROJECT.md (repo-as-skill manifest), context layers, and ADRs. Consumed by…
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
Turn the current conversation context into a PRD and produce a PRD artifact that can be pasted into the project issue tracker. Use when user wants to create a PRD from the current context.
Use when writing implementation plans with bite-sized tasks, file paths, ordered steps, verification checkpoints, and handoff-ready execution detail.
★not rated 11 23d agoA30 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: