quick

Execute isolated verified updates for small software changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quick Mode removes the overhead of the full planning lifecycle when you just need a small, clear change—so you can get verified results quickly.

Core Features & Use Cases

  • Single-executor workflow: Runs one fresh-context executor and verifies before finishing.
  • Task type detection: Automatically routes requests into fix-bug, write-test, refactor, or write-feature flows.
  • Lean context gathering: Pulls only the necessary branch, recent commits, relevant ARCHITECTURE.md excerpts, and CLAUDE.md conventions.
  • Optional worktree isolation: Uses worktree isolation for multi-file or logic-touching tasks to reduce blast radius.
  • Targeted methodology injection: Adds the right supporting skills based on detected task type (e.g., TDD for write-test).

Quick Start

Prefix your request with quick: and describe what you want changed, then let Supermind execute it as a single verified task run.

Frequently Asked Questions about quick

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

FAQPage Schema
How do I apply small software changes like bug fixes and refactors without running the full planning lifecycle?

Small software changes such as bug fixes and refactors bypass the full planning lifecycle by using a single-executor workflow that classifies the task and runs an isolated verified update. This removes planning overhead to deliver fast fixes.

How does single-executor task routing handle different types of code modifications?

Single-executor task routing automatically classifies code modification requests into fix-bug, write-test, refactor, or write-feature flows. It then injects targeted methodology skills tied to the detected type to ensure the correct verification process.

When do I need worktree isolation for a quick bug fix or config change?

You need worktree isolation for a quick bug fix or config change when the task touches multiple files or modifies core logic. This isolation reduces the blast radius by separating the verified update from your primary working branch.

What is the best way to generate tests and verify small code changes quickly?

The best way to generate tests and verify small code changes quickly is to use a lean context workflow. It pulls only necessary git context, relevant ARCHITECTURE excerpts, and conventions to inject TDD methodology for the write-test task type.

Can I execute refactoring and config changes directly without gathering full project context?

Yes, you can execute refactoring and config changes directly. The workflow gathers lean context by pulling only the necessary branch, recent commits, relevant ARCHITECTURE.md excerpts, and CLAUDE.md conventions to build the executor prompt.

What are the limitations of using a single executor run for software refactoring?

A limitation of using a single executor run for software refactoring is that it is designed for small, clear changes. It removes the overhead of the full planning lifecycle, making it unsuitable for complex, multi-step feature development requiring extensive planning.