The razor — the one normative statement of the provenance rule, the counted limits, the content rules and the necessity question that every Nexus drafting stage authors under. Load it before drafting an epic, a decision record, or a discovery ticket; the mechanical half of it is enforced by nexus razor-check, whose…
Tiered architecture-decision orchestrator — evaluates trade-offs and produces ADRs or system designs through discover, research, design, and adversarial-review phases. Use for architecture decisions, ADRs, system design, trade-off analysis between approaches, one-way-door decisions, C4-level design, or NFR evaluation…
Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.
Build a writing kit, everything a person needs to write a doc themselves (sourced facts, verbatim quotes, the choices a draft made, reader objections, open questions, blanks only they can fill) without the finished prose. Use whenever the user wants material or "inspo" to write a brief, memo, RFC, PR/FAQ, proposal…
Plan a project by breaking goals into concrete tasks with priorities and deadlines. Use when the user says "let's plan", "break this down", "I need to figure out how to", "help me plan", or when starting a new project.
A requirements-clarification workflow for sorting what is known, what is uncertain, and what risks or choices need attention before a large task begins. It produces a one-page specification for the user to confirm.
A thinking framework that breaks work into five stages: define the problem, explore options, formulate a solution, act, and assess the result. It can be applied fully, partially, or minimally depending on the task.
Use only in coordinator sessions to orchestrate planning or execution of work, including execute, continue, or resume-plan requests. Covers role definition, specialist discovery, dispatch, review, learning, and synthesis. Never use in Session type: DELEGATED executor sessions; those agents perform their handed scope…
Create a new source-grounded decision brief in the source format by default (Feishu/Lark, Word/docx, Markdown, or self-contained HTML) with a reader-fit Pyramid opening, one editable or auditable visual covering at least 80% of value-weighted non-appendix claims, and one key-question table. Use when the user names…
Scenario Prediction Engine — Orchestrates AI-driven scenario simulation and forecasting using Mirofish's graph-building pipeline to predict outcomes, model ripple effects, and generate structured insight reports.
Use when Codex should work on a repository with OACS-backed development memory: build repo context, record command results as evidence, checkpoint iterations, capture D1 repo episodes, coordinate explicitly requested subagents through one shared OACS database, and close subagents when their goals are done.
ALWAYS invoke this skill before starting ANY coding task. This skill evaluates the user's coding prompt for completeness, coaches them to clarify vague requests before any code is written, then guides implementation through a structured workflow. You MUST consult this skill whenever the user mentions code, a…
Set up agent-friendly project structures with AGENTS.md, specs, workflows, and TODO files for long-horizon autonomous execution. Use when starting a new project, onboarding to a brownfield codebase, or when a project lacks clear documentation for agents to follow. Do NOT use when the project already has a…
Design quick validation experiments for product features. Use this skill when the user needs to validate a hypothesis, test a feature idea before building, has low confidence in an initiative, or asks "should I build this" or "how do I validate this". Also trigger when user mentions prototypes, MVPs, testing…
Generate sequential PRD prompt sequences optimized for Replit Agent development. Use when: building applications with Replit Agent, creating PRDs or technical specifications for Replit, experiencing Replit Agent failures and needing better prompting strategy, or decomposing complex projects for Replit Agent. Triggers…
The /goal pattern: cron jobs that run until an objective condition is met, checked by an independent model (maker/checker split). Source: loop engineering framework by 0xCodez / Anthropic evaluator-optimizer pattern.
Emulates Evangelion's MAGI trinity by splitting decisions into three persona cores — MELCHIOR (scientist/logic), BALTHASAR (mother/safety), CASPER (individual/intuition) — each dispatched as parallel subagents that recursively decompose into variable-sized judgment nodes (10–20 total, groups of 3), self-verify…
Analyzes a codebase and breaks down a goal into implementable user stories with clear acceptance criteria. Use when planning a new feature, estimating work, or creating a development roadmap. Outputs structured stories to .context/[goal-slug]-plan.md ordered by dependency. Filename is generated from the goal…
★not rated 9 4mo agoA84 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: