An interview-style requirements assistant that turns an unclear product idea into a practical product requirements document, or PRD. A PRD explains what a product should do well enough for development to begin.
Meta-skill chaining /specify → /constitute → /plan → /tasks → spec-validation → dispatch-ready. Greenfield project from idea to parallel-dev-ready in one flow. Halts with clear remediation if any phase fails the DoD gate.
BMad Autonomous Development — orchestrates parallel story implementation pipelines. Builds a dependency graph, updates PR status from GitHub, picks stories from the backlog, and runs each through create → dev → review → PR in parallel — each story isolated in its own git worktree — using dedicated subagents with fresh…
An Electric Monk engine — two subagents believe fully committed positions on the user's behalf while the orchestrator performs structural contradiction analysis and synthesis. By outsourcing belief work to agents, the user operates from a belief-free position where they can analyze the structure of the contradiction…
A work-discipline protocol that makes Opus 4.8 (or any non-frontier model) operate at Fable-5-grade quality. Core idea — output quality = model capability x work discipline: spend extra orchestration to buy single-pass quality via six levers (plan gate, small-card execution, adversarial self-check, real-product…
Guided first-session setup. Walks the user through building their personal AI assistant — profile, 12 problems, goals, subgoals, and initial tasks. Run this in the first session after setup.
Architecture Deep Research — scan the current repo, draft a PRD, and run the deep-research loop with citation audits. Use when the user asks you to make an architecture decision, asks "what topology should we use?", says they need to pick between options like vector stores / message queues / retrieval patterns /…
Use when the user asks to validate a product idea, stress-test an idea, evaluate whether an idea is good, or decide whether to build something. Do NOT use for prioritizing an existing backlog or reviewing a shipped feature — those need RICE scoring or a design review instead.
Fork agent memory into parallel branches to explore competing hypotheses. Use whenever a task has two or more genuinely competing approaches worth testing in isolation — whether the user names them explicitly ("explore both", "compare A vs B") OR asks an open decision question (e.g. "what's the fastest way to X?")…
Use when drafting, rewriting, reviewing, or decomposing technical product requirements for product systems, micro-processors, sensors, actuators, or functions, diagnostics, interfaces, or specifications, engineering change requests. Helps turn engineering know-how, notes, standards, customer notes and test…
Turn a rough draft, vague ambition, or messy task brief into a powerful Codex /goal objective for persistent, evidence-checked work. Use when the user asks to write, improve, format, sharpen, stress-test, or activate a Codex goal, thread goal, durable goal, or /goal prompt.
Use when the user asks for deep discovery, 100-question brainstorming, idea interrogation, architecture stress testing, strategy vetting, weakness finding, hole-poking, exhaustive exploration, planning or auditing Codex plugins or skills, or pre-commitment review of a design, plan, strategy, architecture, product…
Full plan lifecycle: deep understanding → write plan with TDD checklist → parallel review → Ralph Loop execution. Trigger when user says 'plan', 'design', 'implement', 'build', 'architect', '@plan', '@execute', or describes a multi-step task that needs structured breakdown. Also trigger for feature requests, system…
Orchestrates a Claude↔Codex cycle where Claude Code designs the contract and arbitrates, while Codex by default (via the official openai/codex-plugin-cc plugin) writes, adversarially reviews, and fixes the code — the orchestrating Claude never edits implementation files. A per-cycle backend directive can opt into…
Set a native Claude Code /goal on THIS session so you keep working until a condition holds — use when you decide you should not stop until some concrete, checkable condition is met (tests pass, a file exists, a build is green) and want the built-in goal evaluator to enforce it. Works in interactive, tmux, and…
Use when a complex task needs dependency-aware interactive branches, subagents, or AI coding threads while keeping the master session context clean through explicit branch briefs, completion reports, wave planning, and user-approved merges. Especially useful with grill-me, Trellis, research, implementation, writing…
A Chinese-language playbook for coordinating a full software project through 11 phases, from requirements and architecture to implementation, testing, and release.
Find and validate what to build in crypto. Use when the user asks "what should I build", "validate this idea", "is this worth building", "find me a startup idea", "crypto idea", or wants blunt feedback on a project concept before writing code.
Quietly maintain a useful project view from meaningful work in the current Codex session. Use when work creates a task, bug, decision, idea, risk, milestone, plan, progress update, or explicit completion.
Run deadline-bound or scope-sensitive agent tasks with explicit done conditions, protected verification time, evidence gates, and safe-stop rules. Use for rapid implementation, debugging, integration, delegated work, feasibility gates, or tasks where scope drift, false completion, repeated failure, or deadline…
★not rated 101▲
+39 16d agoA65 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: