quick

Execute small, self-contained tasks with optional discussion and verification modes.

1|2|Updated Mar 6, 2026

Search Tags:#automation #workflow #task execution #gsd #quick task #ad-hoc

Ready to run

npx skills add https://github.com/cinjoff/fhhs-skills --skill quick-cinjoff

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: quick
Source: https://github.com/cinjoff/fhhs-skills/tree/main/.claude/skills/quick
Command: npx skills add https://github.com/cinjoff/fhhs-skills --skill quick-cinjoff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill allows for the rapid execution of small, ad-hoc tasks without the overhead of a full project planning cycle, ensuring tasks are completed efficiently and reliably.

Core Features & Use Cases

Ad-hoc Task Execution: Quickly run small tasks that don't require extensive planning or phase management.
Configurable Modes: Supports --discuss for clarifying ambiguities and --full for enhanced plan checking and verification.
Use Case: You need to quickly update a specific configuration file or run a small script to process a batch of data. Instead of initiating a full project, you can use the quick skill to get it done.

Quick Start

Use the quick skill to update the project's README with the latest version number.

Frequently Asked Questions about quick

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

FAQPage Schema

How do I execute small ad-hoc tasks without triggering a full project planning cycle?▼

To execute ad-hoc tasks without a full project cycle, use a lightweight task execution skill that manages atomic operations in dedicated directories and updates project state automatically upon completion.

What is the best way to update a configuration file or run a small script without extensive project management?▼

The best way to update configurations or run scripts is using an ad-hoc task execution tool that provides Get-Shit-Done guarantees, ensuring efficient and reliable completion of self-contained operations.

Can I clarify ambiguities or enforce plan verification before running an ad-hoc task?▼

Yes, you can clarify ambiguities and enforce plan verification by using configurable execution modes like `--discuss` for clarification and `--full` for enhanced plan checking and task verification.

Does this ad-hoc task execution approach work for atomic operations that do not warrant a full project phase?▼

Yes, this approach is specifically designed for atomic operations that do not warrant a full project phase, managing task execution through dedicated directories while maintaining state updates.

When should I avoid using lightweight task execution for workflow automation?▼

You should avoid using lightweight task execution for complex workflow automation that requires extensive planning, phase management, or multi-step dependencies beyond self-contained atomic operations.

Why does a quick task execution tool update project state after running small operations?▼

A quick task execution tool updates project state after running small operations to maintain Get-Shit-Done guarantees, ensuring atomic tasks are tracked and reliably integrated without manual overhead.