Launch multi-agent ideation to explore a concept through structured dialogue between a Free Thinker and a Grounder, arbitrated by the team lead, and documented by a Writer. Three actions: Plan (interview + configure), Ideate (depth-aware exploration + conditional production), Continue (versioned resumption with smart…
Run the full Oh My MiniMax Code loop to independently Accepted evidence (INTAKE → DISCOVER → PLAN → PLANREVIEW → EXECUTE → VERIFY → REPAIR → ACCEPT, optional RELEASE). Triggers: "max mode", "verified mode", "run this to accepted evidence", "oh-my-mcode", "ship with evidence", "prove it passes". Do not trigger for…
Create, tighten, or review runnable /goal contracts for coding agents such as Codex, Claude Code, Cursor, and similar agent tools. Use when the user asks to write, make, generate, improve, productize, or critique a goal prompt, rescue contract, GOAL.md-style task, done-when contract, verification prompt, stop-rule…
Turn an ambiguous question about an unfamiliar or brownfield system into a bounded, read-only, evidence-backed investigation with a confirmed investigation contract, deliberate context manifest, claim ledger, ontology, owned open questions, and reviewable technical brief. Use when asked to investigate a repository…
Commands: newproject, continue, implement, task, research (research a topic on the web), cr (code review), deep cr (multi-phase code review), design crit (multi-phase spec review), pr (address PR feedback), setup, or open guidance Spec-driven development: process for planning, building, and reviewing code projects…
Build a persistent context system (atlas) for any repository — generates directory maps with entrypoints, documents architecture and module boundaries, traces critical flows, catalogs external dependencies, and creates agent-ready onboarding guides. Use when asked to create a repo map, generate codebase documentation…
Orchestrate implementation of a reviewed plan: task breakdown, TDD sub-agents, code review, and verification report. Use when the user asks to implement, build, or execute a plan under specs/plans/ — after /speq-plan, before /speq-record. Arg: .
Product team orchestrator. Coordinates Product Manager, UX Designer, Software Architect, Tech Lead, Frontend/Backend Engineers, DBA, QA and DevOps through the complete feature pipeline. Use when the user types "product team", "ativar time", "montar time", "start feature", "timovi", or wants to coordinate a feature…
Generate a Product Requirements Document (prd.json) for the Ralph autonomous agent loop. Use when planning a feature, starting a new project, or preparing work for Ralph to implement. Triggers on: create a prd, write prd for, plan this feature, generate user stories, set up ralph for, spec out.
Use when starting significant features, epics, or complex tasks. Creates multi-phase implementation plans with parallelizable phases, poker estimates, TDD-first acceptance criteria, and quality gates. Detects tech stack from CLAUDE.md/AGENTS.md (bypassing internet research if complete) or via codebase scan.
Use when the user wants to brainstorm an idea or design a feature/spec. Explores intent and requirements through dialogue, then writes a spec document to docs/spark/ and STOPS. Does not auto-chain to implementation planning or any other skill.
A workflow guide for OpenPrd, a workspace for turning unclear product ideas into clarified requirements and a handoff for implementation. It helps choose and run each stage, from questions through final handoff.
★not rated 50
changed 3d agoASkillSpector: warn68 tokens
originalMIT
Analyzes raw requirements into visual specs and generates artifacts. Invoke when user runs /vspec:new for analysis or /vspec:verify for models and prototypes.
CTO-level architectural advisor for AI-native development. Use this skill whenever you encounter code design decisions, architecture discussions, system resilience questions, or any work touching: "architecture", "design", "scale", "dependencies", "state", "failure", "blast radius", "refactor", "migrate", "optimize"…
Autonomous orchestrated loop that works through a prd.json story-by-story using a fresh Task subagent per story. Use this skill whenever the user asks to "run the loop", "claude loop", "start the loop", "kick off the loop", "work through the prd", "process prd.json", "implement all the stories", "iterate through the…
Structured Chain-of-Thought (CoT) & Deep Reasoning Protocol for complex problem analysis, architectural decisions, security evaluations, and deep troubleshooting. Activate when --deep or --cot flag is present in workflows, or when deep architectural reasoning is required. Supports MCP Graph integration for…
Use when creating or iterating staged planning artifacts for a complex feature: design discussion, structure outline, final executor plan, or supporting research/research questions. Also use when designing before coding, breaking work into vertical slices, or deepening a high-value roadmap item, NNN improve plan…
Use when starting a new project. Genesis finds real production failures from similar GitHub repos, then builds a working MVP immediately - not just documents. Two modes: fast-mvp (5 min research cap, builds right after) and deep-research (full analysis). Success = user can run the project. Triggers on: "genesis init…
★not rated 49 17d agoA133 tokens
AGPL-3.0
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: