skills.rest
alexandrbasis
alexandrbasisCOMMUNITY
Explore all skills by this author ā†’
Websiteš•@alexandrbasisGitHub

quick

Plan and implement small software changes touching five or fewer files.

12|2|Updated Nov 20, 2025
Search Tags:#workflow#planning#decomposition#config#bugfix#task#quick
One-click install
npx skills add https://github.com/alexandrbasis/claudops --skill quick-alexandrbasis
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: quick
Source: https://github.com/alexandrbasis/claudops/tree/main/.claude/skills/si-quick
Command: npx skills add https://github.com/alexandrbasis/claudops --skill quick-alexandrbasis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a fast-path for small, untracked changes or bug fixes with clear scope, avoiding the formal task or tech-decomposition processes.

Core Features & Use Cases

  • Fast-path planning with minimal ceremony and guardrails to ensure scope is preserved.
  • Redirects to the formal tracked flow when changes exceed the quick task criteria or involve new modules.
  • Use case: applying a small config change or a bug fix that touches five or fewer files.

Quick Start

Explain the quick task you want to accomplish and confirm the quick plan before proceeding.

Frequently Asked Questions about quick

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

FAQPage Schema
How do I handle quick bug fixes without a formal planning process?ā–¼

To handle quick bug fixes, use a fast-path workflow that enforces a concise 3-step process: scope gate, quick plan, and implement. This avoids formal task decomposition for small, untracked changes.

What is the best way to apply small config updates safely?ā–¼

The best way to apply small config updates is using a quick task workflow with minimal ceremony and guardrails. It ensures scope is preserved by confirming a quick plan before implementation.

When should I use a quick task workflow instead of formal tech decomposition?ā–¼

You should use a quick task workflow when handling minor refactors, small config updates, or bug fixes that touch five or fewer files. If changes exceed these criteria or involve new modules, formal tracking is required.

Can I do a minor refactor if it touches more than five files?ā–¼

You cannot do a minor refactor using the quick task path if it touches more than five files. The workflow redirects changes exceeding the five-file limit or involving new modules to formal tracked paths.

What are the steps to implement a quick change in a software project?ā–¼

The steps to implement a quick change involve a 3-step process: passing a scope gate, creating a quick plan, and implementing the change. You explain your task and confirm the plan before proceeding.

Related Skills

Explore More Software Engineering Skillsā†’
yabafreyabafre
2

aped-quick

Draft quick specs and run compressed TDD cycles for small isolated changes.

Community
Intermediate
bitovibitovi
9

writing-plans

Automate implementation plan creation with task decomposition and file mapping.

Official
Advanced
HugopeckHugopeck

decompose

Break project briefs into parallelizable Track task files and decomposition plans.

Community
Advanced
EarthmanWebEarthmanWeb
1

swe-swarm-orchestrate

Coordinate multi-agent swarms for large software tasks across multiple topologies.

Community
Advanced