Use when a team needs to plan, author, or standardize product/software documentation (PRD, FSD, HLD, TRD, ERD, OpenAPI, Wireframe, Roadmap, PRODUCT.md, DESIGN.md, AGENT.md). Provides terminology verification, ready-to-use templates, and a scale-based 'need-or-not' decision matrix so the right documents are produced…
Turn an unstructured stakeholder conversation, Slack thread, or meeting transcript into a structured spec (problem, goals, non-goals, success metrics, open questions). Use whenever a PM has raw conversational input and needs a first-draft spec, or when someone says "can you turn this into a doc" after a discussion.…
Skill pour analyser, evaluer, prioriser et planifier la reduction de la dette technique dans un codebase ou un projet logiciel. Utiliser ce skill des que l'utilisateur mentionne "dette technique", "tech debt", "code legacy", "refactoring", "qualite du code", "code smell", "complexite cyclomatique", "couverture de…
Durable repo-local workflow control for explicit loop/queue workflows, long-running implementation or review passes, durable source-backed investigations, and goal/control handoffs that need a persistent cursor, evidence surface, verifier, and stop state. Use when the user asks to create, run, resume, reset, audit, or…
Execute an agentmaster plan. Use when the user asks to execute, implement, or run a plan produced by agentmaster-plan, or invokes /agentmaster-execute. Honors the plan's execution mode (sequential default, justified parallel with optional pilot), gates every task on verification, re-verifies independently, runs the…
Generates technical implementation spec, plan, AND an operational contract for one or more features based on PRD, codebase analysis, and iterative clarification. Produces contract.md (environment contract, quality gates, coverage manifest, observable criteria) consumed by implement-feature and evaluator. Supports…
A Japanese-speaking thinking and context assistant for the Mac command line. It helps with notes, light conversation, idea development, summaries, and routing deeper discussions to Discord.
Fully autonomous expert forum builder and project maturity engine. User delivers an idea, auto-distills domain experts from web sources, builds knowledge base with breadth/depth/thickness/effectiveness, scores maturity (0-100), builds project code, debugs, re-scores in adversarial loop until 100/100, then submits to…
Plans, documents, and reviews code architecture for software projects. Produces structured architecture documents with Mermaid diagrams through a collaborative interview workflow. Triggers on architecture planning, project structuring, folder organization, system design, component design, data flow planning, codebase…
Research-backed comprehensive project planning. Use when planning a new project or initiative. Triggered by "make a plan", "I want to start a project", "break down tasks", or "create a roadmap".
Design autonomous AI agent systems. Multi-agent orchestration, tool use, memory, planning, and evaluation. Use when building AI-powered automation or agent workflows.
A guided workflow for turning ideas for AI products into product requirements documents (PRDs), which describe what to build and why. It asks structured questions, adds AI-specific sections, checks the result four ways, and rates its quality.
Evidence-driven dissection of an existing service, written plan, or codebase area. Interrogates every entity (table, field, component, endpoint, module, boundary) against ground truth from multiple sources at once, red-teams each verdict devil's-advocate style, and arrives at the minimal-build optimization plan. Runs…
Coordinates a subagent workflow where a worker implements a development task, a code reviewer audits the result for critical errors, flaws, and optimization opportunities, and then the worker iterates to apply the reviewer’s optimization suggestions. Use when the user requests implementation or other development work…
A lightweight engineering workflow for turning an idea into a real, shippable product with an AI coding agent. Core = Karpathy's four coding disciplines (think before coding / simplicity first / surgical changes / goal-driven; battle-tested), plus an Explore→Plan→Build→Polish→Ship process, task tiers (skip the process…
Build, review, update, and audit production-grade project documentation packs from a brief, partial docs, or implementation changes. Use when the user asks to create a full docs folder, PRD/FRS/NFR, architecture docs, ERD/data dictionary, API/OpenAPI docs, UX flows, project plans, engineering workflow docs, AI agent…
Use when the clodex router hands off a run at stage open or plan, when a run the router resumed shows no recorded plan or a plan with no standing approval, or when plan-review findings on such a run still need dispositions before work can start.
name: ship description: Plan and ship a feature. Explores codebase, writes specs/.md, then runs ship CLI for autonomous execution. Use when asked to build something substantial. user-invocable: true.
A workflow layer for running long, mostly unattended Codex development sessions with saved state, task queues, isolated workspaces, retries, and verification records.
Ensemble de commandes pour structurer et piloter le cycle d'analyse, de revue, d'implementation et de validation d'une demande ou tache. Commandes disponibles : help, init, best-practices, asking, analysis, review, process, validate, re-process.
★not rated 1 4mo agoA61 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: