supermind

Route user requests to quick or project workflows based on scope.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/steven-3/supermind --skill supermind
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supermind
Source: https://github.com/steven-3/supermind/tree/main/skills/supermind
Command: npx skills add https://github.com/steven-3/supermind --skill supermind

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces decision friction by automatically selecting the right execution mode so you don’t over-ceremonialize small fixes or under-structure larger changes.

Core Features & Use Cases

  • Auto-detects task scope: identifies whether a request looks like a small, clear change or a multi-step project.
  • Invokes the right mode: routes to either quick or project workflow immediately, preserving the original prompt and flags.
  • Supports explicit overrides: respects user commands like /quick and /project (including lifecycle tweaks such as skip-discuss or skip-research).
  • Handles common edge cases: avoids routing for non-tasks and resumes an in-progress .planning/ session.

Quick Start

Tell the assistant what you want changed, and it will choose quick mode or project mode automatically and then run the corresponding workflow.

Frequently Asked Questions about supermind

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate task routing for code refactoring and feature work?

Task routing for code refactoring is automated by analyzing prompt clarity and scope to select either a lightweight quick workflow or a structured project lifecycle. This reduces decision friction by preventing over-ceremonializing small fixes or under-structuring larger changes.

What is the best way to manage workflow orchestration for multi-step implementations?

Workflow orchestration for multi-step implementations is managed by evaluating prompt interpretation to automatically invoke the right execution mode. It preserves the original prompt and routing flags to ensure the appropriate downstream skill handles the requested feature work.

Can I force a specific project lifecycle or skip research during codebase maintenance?

Yes, you can force a specific project lifecycle during codebase maintenance by using explicit overrides like /quick or /project. The workflow honors these commands and applies lifecycle tweaks such as skip-discuss or skip-research.

Does workflow orchestration resume in-progress planning sessions automatically?

Workflow orchestration handles edge cases by automatically resuming an in-progress .planning/ session. It also avoids routing entirely for non-tasks, ensuring that only valid codebase maintenance and feature work trigger the lifecycle planning.

When should I use quick workflow versus a full lifecycle for codebase maintenance?

Quick workflow is used for small, clear changes, while a full lifecycle is applied to multi-step implementations during codebase maintenance. The selection depends on the scope detected through prompt interpretation, unless an explicit override is provided.