35,518 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.
This command is designed to create a comprehensive Product Requirement Prompt (PRP) for building Model Context Protocol (MCP) servers referencing this codebase patterns mirroring tool setups for the users specific requirements.
Scaffold a new research project repository, then run the intake briefing to populate its direction. Use when Hugo starts a new research direction or asks to set up a project repo. Picks the host (Spartan or local), assembles and fills the orchestrator CLAUDE.md, seeds the docs files, sets up local git and pre-commit…
Use Zoe's local orchestration tools to plan engineering work, dispatch subtasks, inspect task or plan status, and list archived plans in the local ai-devops installation. Use this when the user asks Zoe to create or queue development work, check execution state, or inspect recent plans.
You are the lead architect for this task. Your job is to understand, assess, plan, and coordinate. You do not write implementation code during this phase.
Pick the next pending task from a project's task list and drive it through the full implementation cycle: plan, implement, test, review, fix, simplify, and mark complete.
Creates specifications before code. Phase 1 (Specify) is always delegated to the requison subagent — it elicits requirements and drafts content aligned to this skill’s template. Use when starting a project, feature, or large change without a spec. With Figma, run the MCP flow (below) before locking the spec. Suggested…
Only three files. A minimal spec-driven workflow for Claude Code: /tripod:spec interviews you and writes SPEC.md + CLAUDE.md, /tripod:tasks turns them into TASKS.md, /tripod:next executes tasks one by one.
★not rated 2 29d agoA
tokens not measured
originalMIT
Foundational traceability layer for the entire Plan→Build→Verify→Review→Accept responsibility chain. Every role must leave a traceable record: upstream requirements → execution → output mapping → evidence → persisted record. Without traceability at every link, the chain cannot be audited, handoffs break, and sign-off…
Aktiviert Fable-artiges, systematisches Vorgehen für komplexe, mehrstufige Aufgaben: explizites Planen (Stage-Map), paralleles Delegieren an Sub-Agenten und verpflichtende Selbst-Verifikation an jeder Stufe. Auslösen, wenn der Nutzer sagt "be systematic", "act like Fable", "deep work mode", "mach das…
Use when the user wants to plan a non-trivial change before writing code — refactor, migration, new feature, debugging strategy. Produces a written plan file, not implementation.
Contract-driven, design-first quality guardrails for AI-assisted full-stack development. Prevents project chaos at scale by enforcing a five-layer protection system: Design → Contract → Implementation → Verification → PM. Use when: starting a new full-stack project, planning a non-trivial feature, dispatching…
A research-topic adviser that turns a vague idea into a clearer study question through guided questions, different viewpoints, and checks against academic standards.
AI-powered PRD generator with official-source research validation, self-evolving project skills, CI/CD pipeline generation, and local documentation cache for AI-assisted development.
★not rated 2 6mo agoA
tokens not measured
originalMIT
MANUAL TRIGGER ONLY: invoke only when user types /plan-ceo-review. CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick expansions), HOLD…
Plans large refactors, framework upgrades, and legacy modernization for .NET solutions. Produces phased plans with risk and effort estimates. Use for audits of legacy code or "should we modernize or rewrite" questions. Read-only.
A guide for turning project ideas and product discussions into a product requirements document, or PRD. A PRD describes what a product should do, what it should not do, and how it should be designed.
A command for carrying out a planned feature in several stages, with review and validation points along the way. It uses a feature plan stored under the project’s rpi folder and places implementation work in a matching output folder.
★not rated 2 4mo agoA10 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: