quick

Execute small ad-hoc tasks with atomic commits and STATE.md tracking.

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/sidunrealde/ArchVis --skill quick-sidunrealde
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quick
Source: https://github.com/sidunrealde/ArchVis/tree/main/.github/skills/quick
Command: npx skills add https://github.com/sidunrealde/ArchVis --skill quick-sidunrealde

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill allows for the execution of small, ad-hoc tasks with built-in guarantees for atomic commits and STATE.md tracking, ensuring reliability and traceability for quick operations.

Core Features & Use Cases

  • Atomic Task Execution: Ensures that each quick task is treated as a single, indivisible unit of work.
  • State Tracking: Updates .planning/STATE.md to maintain a clear record of completed quick tasks.
  • Optional Discussion & Verification: Supports an optional lightweight discussion phase to clarify requirements and an optional full mode for plan-checking and post-execution verification.
  • Use Case: Quickly update a README file with the latest project status, add a new entry to a changelog, or refactor a small piece of code, all while ensuring the changes are properly recorded and committed.

Quick Start

Use the quick skill to add a new entry to the project's changelog.

Frequently Asked Questions about quick

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

FAQPage Schema
How do I execute ad-hoc tasks with atomic commits and state tracking?

Executing ad-hoc tasks with atomic commits and state tracking involves treating each quick operation as an indivisible unit of work while automatically updating the `.planning/STATE.md` file to maintain a clear, traceable record of completed changes.

What is the best way to automate quick code refactoring while ensuring traceability?

Automating quick code refactoring with traceability is achieved by orchestrating task execution within a project's planning directory, ensuring small code updates are properly recorded via atomic commits and STATE.md tracking.

Can I use discussion and verification modes for quick task automation?

Yes, you can use an optional lightweight discussion phase to clarify requirements and an optional full mode for plan-checking and post-execution verification, providing enhanced reliability for quick task automation.

Does the Skill work without external dependencies for state tracking?

Yes, the Skill works without external dependencies for state tracking, relying solely on its internal orchestration of gsd-planner and gsd-executor to manage task execution and update the `.planning/STATE.md` file.

When should I not use ad-hoc task automation with atomic commits?

You should not use ad-hoc task automation with atomic commits for large, complex operations, as this approach is specifically designed for small, quick tasks like updating a README, adding changelog entries, or refactoring small code pieces.