Use when planning active-learning experiments from ee observation ledgers, learning uncertainty reports, evaluation records, causal/economy/context evidence, or ee.skillevidencebundle.v1 artifacts without moving experiment-planning judgment into the Rust ee CLI.
Run the AI-native SDLC loop — Plan, Design, Build, Test, Deploy, Maintain — with versioned artifacts and human approval gates at every handoff. Use when the user states a goal, idea, feature, or change request and expects the agent to scaffold and drive the project through the full lifecycle instead of jumping…
MANUAL TRIGGER ONLY: invoke only when user types /autoplan. Auto-review pipeline — reads the full CEO, design, and eng review skills from disk and runs them sequentially with auto-decisions using 6 decision principles. Surfaces taste decisions (close approaches, borderline scope, codex disagreements) at a final…
Guides developers through a human-supervised PDCA framework for AI code generation. Applies analysis, TDD, validation, and retrospection. Activates for sessions requiring systematic quality control.
BABOK 7.1 skill — Specify and Model Requirements. Use this skill when the BA translates elicitation results into formal specifications: user stories, use cases, business rules, data definitions, process models (BPMN). Triggers: "requirements specification", "user story", "use case", "business rules", "specify…
End-to-end project improvement — plan, branch, delegate execution, verify. Calls /plan for analysis, then delegates fixes to agents. Use when "improve project", "swarm improve", "send agents to fix", "refactor project X", "upgrade project". Do NOT use for planning only (use /plan), single tasks (use /delegate), or own…
Shape and execute multi-step work with the Ergo CLI, a repository-local backlog management tool. Use to plan software development, documentation, or general knowledge work as a series or graph of well-defined tasks. Use to define dependencies within that task backlog. Use to group tasks into epics when needed. Skip…
★not rated 42 3d agoASkillSpector: warn73 tokens
originalMIT
Daily journaling, reflection, and planning. Use when the user says 'morning', 'let's plan the day', 'journal', or similar. Loads calendar + email scan, reviews yesterday, checks emotional state, runs inbox hygiene, creates today's journal, offers an honest reality check, sets 1-3 priorities that ladder up to annual…
Goal-driven conductor for the whole idea-to-published-paper lifecycle. Takes a research idea plus experiments and a target ("submit to NeurIPS 2026", or "help me pick a venue") and runs a goal->plan->execute->verify->reflect loop. It plans the stages, invokes the right lifecycle skills in order (literature-review…
Use when Codex work should route bounded implementation to lower-cost workers and reserve Sol for risky plan review or final evidence gates, or when installing or validating this workflow.
A comprehensive workflow for researching a startup idea and generating a full startup kit including market analysis, competitor mapping, product specs, and a high-fidelity landing page.
Autonomous research loop — read plan, decompose, dispatch research agents, integrate, deliver wiki. For research tasks instead of coding. Runs as visible TUI agents in git worktree. Use when user says "yesresearch", "research ", "recherchiere ". Spawns cluster agents that use opencode built-in subagents (general…
Drive a whole tdmcp feature BACKLOG to completion as resumable, wave-by-wave releases — the campaign layer ABOVE tdmcp-pipeline/tdmcp-feature-lead. Use whenever the user wants to implement an ENTIRE backlog or discovery file (e.g. workspace/discovery/FEATUREBACKLOG.md), 'all the features', many features across…
User-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the…
Designs Claude Code prompts and CC environments. Produces CLAUDE.md drafts, agent topologies, scope-authorization frameworks, halt triggers, Skills/hooks/MCP plans, chat-to-CC handoff specs, and EXECUTIONPLAN.md remediation plans. Five modes: DESIGN (new CC deployments), EVOLVE (updates from friction), RESEARCH…
Challenge the current Limina research direction and next-step plan. Use for step-back reviews, pre-commitment checkpoints, plateau reviews, contradictory findings, or pivot/continue/stop recommendations when evidence or framing may be weak.
Structured six-hats thinking sessions for debating decisions. Use when user says "six hats", "six hats debate", or wants to explore a decision through six colored-perspective lenses in sequential rounds with a final recommendation.
Transform a rough feature idea into a complete milestone document through interactive requirements elicitation. Ensures strict, observable scope boundaries.
Section-by-section authoring of a Product Requirements Doc for a single mobile-app system. Reads concept, systems index, dependencies, and registry; walks the user through each PRD section collaboratively; writes incrementally to file. Use when starting a new PRD or filling gaps in an existing one.
★not rated 40 4mo agoA62 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: