evolution-foundation/evo-nexus
Skill Claude Code
Post-AI-generation cleanup — remove single-use helpers, over-abstractions, generic naming, and unnecessary configurability. Use after dev-autopilot or any LLM-generated code burst.
The open source operating system for AI-powered businesses
This repository also configures its own agents. See what evo-nexus tells them →
evolution-foundation/evo-nexus
Skill Claude Code
Post-AI-generation cleanup — remove single-use helpers, over-abstractions, generic naming, and unnecessary configurability. Use after dev-autopilot or any LLM-generated code burst.
evolution-foundation/evo-nexus
Skill Claude Code
Advisory router — query Claude, Codex, or Gemini for a quick second opinion. Experimental — only Claude is guaranteed available; other models require dev-mcp-setup configuration.
evolution-foundation/evo-nexus
Skill Claude Code
Full autonomous execution from idea to working code. Use when user says "autopilot", "autonomous", "build me", "create me", "make me", "full auto" — orchestrates spec → plan → code → QA → validation across the engineering layer agents.
evolution-foundation/evo-nexus
Skill Claude Code
Cleanly stop an active engineering layer flow (dev-autopilot, dev-deep-interview, dev-plan) and report what was completed. Use when the user says "cancel", "stop", "abort", "cancelomc", or wants to exit a multi-phase dev workflow.
evolution-foundation/evo-nexus
Skill Claude Code
Tri-model orchestration — run the same task through Claude + Codex + Gemini in parallel and synthesize the best answer. Use for high-stakes decisions where multi-model consensus reduces single-model bias.
evolution-foundation/evo-nexus
Skill Claude Code
Set up Telegram, Discord, or Slack webhooks for engineering layer alerts — long-running task completion, build failures, security audit alerts.
evolution-foundation/evo-nexus
Skill Claude Code
Two-stage investigation — causal trace (via @trail-tracer) followed by requirements crystallization (via @echo-analyst + dev-deep-interview). Use when a problem is both unclear in cause AND unclear in scope.
evolution-foundation/evo-nexus
Skill Claude Code
Socratic questioning to crystallize vague requirements into a testable spec. Use when input is ambiguous, when the user asks for "deep interview", or before dev-autopilot if the brief is too broad. Pairs with @echo-analyst.
evolution-foundation/evo-nexus
Skill Claude Code
Deep codebase initialization — generate hierarchical AGENTS.md / CLAUDE.md context files for a new project so engineering agents have full context from session start.
evolution-foundation/evo-nexus
Skill Claude Code
Parallel external documentation lookup. Spawn multiple @scroll-docs agents simultaneously to fetch SDK refs, API docs, and framework guides for different topics in one pass.
evolution-foundation/evo-nexus
Skill Claude Code
Meta-skill — extract reusable skills from the current conversation. Identifies patterns that appeared 3+ times and proposes them as new skills. Pairs with skill-creator builtin.
evolution-foundation/evo-nexus
Skill Claude Code
Configure MCP servers for the workspace — web search, filesystem, GitHub, Stripe, etc. Use when adding a new integration that needs MCP-level access.
evolution-foundation/evo-nexus
Skill Claude Code
Strategic planning with optional interview workflow. Use when the user wants to plan before implementing — "plan this", "let's plan", structured requirements gathering for vague ideas. Pairs with @compass-planner agent. Supports consensus mode and review mode.
evolution-foundation/evo-nexus
Skill Claude Code
Worktree-first development environment — create per-issue or per-PR git worktrees, optionally with tmux sessions, so multiple work streams don't collide.
evolution-foundation/evo-nexus
Skill Claude Code
Persistence loop — keep working on a task until it's resolved or until a circuit breaker stops you. Different from /loop (which is time-based) — ralph is iteration-based with state.
evolution-foundation/evo-nexus
Skill Claude Code
Multi-perspective consensus planning with Planner/Architect/Critic loop. Use when high-stakes decisions need RALPLAN-DR structured deliberation (auth, migrations, public APIs, irreversible changes). Pairs with @compass-planner + @apex-architect + @raven-critic.
evolution-foundation/evo-nexus
Skill Claude Code
Release preparation — changelog generation, version bump, tag creation. Generic version (not project-specific). For EvoNexus releases, use custom-release instead.
evolution-foundation/evo-nexus
Skill Claude Code
Persist context across engineering sessions — save important decisions, gotchas, or patterns that should survive beyond the current conversation. For long-term workspace memory, prefer mempalace.
evolution-foundation/evo-nexus
Skill Claude Code
Scientific method scaffolding — hypothesis → experiment → evidence → conclusion. Use when you need rigorous causal reasoning rather than vibes-based debugging.
evolution-foundation/evo-nexus
Skill Claude Code
Create a new custom skill for the workspace. Guides the user through defining the skill's slug, trigger conditions, workflow steps, outputs, and anti-patterns. Use when the user says 'create a skill', 'new skill', 'add a skill', 'I need a custom skill', or wants to formalize a workflow as a reusable skill.
evolution-foundation/evo-nexus
Skill Claude Code
On-demand spawning of multiple engineering agents in parallel for large-context work. Use when a task is too big for a single agent and the work can be split into independent streams.
evolution-foundation/evo-nexus
Skill Claude Code
Evidence-driven causal tracing with competing hypotheses. Use when an observation has multiple plausible explanations and you need to systematically rank them with evidence FOR and AGAINST each. Pairs with @trail-tracer.
evolution-foundation/evo-nexus
Skill Claude Code
QA cycling workflow — repeat build/lint/test/fix cycles up to 5 times until all checks pass. Stops early if the same error repeats 3 times (signals a fundamental issue, not a fixable one).
evolution-foundation/evo-nexus
Skill Claude Code
Verify that a change really works before claiming completion. Use when the user wants confidence that a feature, fix, or refactor actually works — turns vague "it should work" claims into concrete evidence. Pairs with @oath-verifier agent.
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: