skills.rest
gannonh
gannonhCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

kata-execute-quick-task

Execute quick tasks in the Kata framework with tracked outcomes.

Updated Aug 27, 2026
Search Tags:#automation#planning#execution#state-tracking#kata#quick-task
One-click install
npx skills add https://github.com/gannonh/kata-orchestrator --skill kata-execute-quick-task
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kata-execute-quick-task
Source: https://github.com/gannonh/kata-orchestrator/tree/main/skills/kata-execute-quick-task
Command: npx skills add https://github.com/gannonh/kata-orchestrator --skill kata-execute-quick-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables performing small, one-off tasks within the Kata framework without going through full planning cycles, saving time while maintaining traceability through STATE.md.

Core Features & Use Cases

  • Quick mode execution path with planner and executor
  • Automatic creation of a numbered quick task directory under .planning/quick
  • Updates to STATE.md with completion records and per-task summaries
  • Ideal for small data cleanup, quick validations, and a few-line fixes that don't require roadmap changes

Quick Start

Describe the task you want to perform to kick off a quick task. The system will prompt for a description if needed, generate a slug, create the numbered quick task directory, and orchestrate a planner and executor sequence to produce PLAN.md and SUMMARY.md.

Frequently Asked Questions about kata-execute-quick-task

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

FAQPage Schema
How do I execute ad-hoc tasks without going through full planning cycles?▼

Quick ad-hoc task execution bypasses full planning cycles by automating planner and executor sequences. It creates a numbered directory under .planning/quick, generates PLAN.md and SUMMARY.md, and updates STATE.md without altering the main roadmap.

What is the best way to track small one-off fixes in STATE.md?▼

Tracking small one-off fixes in STATE.md is handled automatically by documenting completion records and per-task summaries. The process commits artifacts to .planning/quick and updates the state file to maintain traceability for time-bound tasks.

How do I run quick data cleanups and validations without changing the project roadmap?▼

Run quick data cleanups and validations using a quick-task mode designed for time-bound work. It orchestrates the execution and documents the outcome in STATE.md, ensuring the main project roadmap remains completely unaltered.

When should I use quick-task execution instead of a full planning workflow?▼

Use quick-task execution for small, time-bound tasks like a few-line fixes or quick validations that require minimal planning. If the work requires roadmap changes or extensive planning, a full planning workflow is necessary instead.

Does quick-task execution generate planning and summary artifacts?▼

Quick-task execution does generate planning and summary artifacts. It coordinates interactions to produce PLAN.md and SUMMARY.md files within a numbered quick task directory, alongside committing the final artifacts and updating STATE.md.

Related Skills

Explore More Software Engineering Skills→
Unified-Field-Theory-ResearchUnified-Field-Theory-Research

gpd-quick

Execute quick research tasks in GPD projects with atomic commits.

Official
Intermediate
qdzshqdzsh
12

handoff

Generate a continue.md handoff package and update STATE.md summaries.

Community
Intermediate
JHaugaardJHaugaard

workflow-status

Read handoff documents in .docs/ to display project workflow progress.

Community
Basic
novatech2210-cmdnovatech2210-cmd

gsd-quick

Execute quick ad-hoc tasks with atomic commits and STATE.md updates.

Community
Advanced