quick-fix

Creates a session note and 1-3 task cards for small, clearly defined code fixes.

Updated Jul 28, 2026
One-click install
npx skills add https://github.com/truongnat/Restly --skill quick-fix-truongnat
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quick-fix
Source: https://github.com/truongnat/Restly/tree/main/.agents/skills/quick-fix
Command: npx skills add https://github.com/truongnat/Restly --skill quick-fix-truongnat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Small, obvious code changes often get buried under heavyweight planning ceremonies like business analysis documents, design specs, and requirement matrices. This Skill provides a lightweight path (Path=Quick) that captures just enough structure — a goal, facts, and 1-3 verifiable task cards — so tiny fixes ship fast without losing traceability. ## Core Features & Use Cases - Quick Session Artifacts: Generates a QUICK.md session note with an outcome-first goal, facts, out-of-scope items, and handoff instructions. - Slim Task Cards: Produces 1-3 TASKS.md cards, each with acceptance criteria, verification steps, file scope, and developer context with sources. - Guardrails and Escalation: Forbids BA/design documents on the Quick path and forces an upgrade to Lite/Full planning when product or design ambiguity appears. - Use Case: A user reports that parseDate("") throws instead of returning null. Use this Skill to write a QUICK.md stating the observable goal, create one task card with a falsifiable acceptance criterion, run the context builder and linter, then hand off to sync and execution. ## Quick Start Use the quick-fix skill to plan a small bug fix where parseDate should return null for empty input, then hand off to sync and execution.

Frequently Asked Questions about quick-fix

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

FAQPage Schema
How do I plan a small bug fix without full design documents?▼

Use the Quick path: write a QUICK.md with an outcome-first goal and facts, then create 1-3 task cards in TASKS.md with acceptance criteria and verification steps. Run build_context.py and lint_artifacts.py, then hand off to sync and execution.

What artifacts does the quick-fix workflow produce?▼

It produces three required artifacts: QUICK.md (goal, facts, out of scope, handoff), TASKS.md (1-3 cards with acceptance criteria, verification, and developer context), and CONTEXT.md generated by build_context.py.

When should I upgrade from Quick to Lite or Full planning?▼

Upgrade when the change is unclear, requires product or design decisions, has blocking unknowns, or needs more than 3 independently verifiable task cards. The Quick path forbids fuzzy goals and business analysis documents.

What is forbidden on the Quick fix path?▼

The Quick path forbids creating BUSINESS_ANALYSIS.md, BASIC_DESIGN.md, DETAIL_DESIGN.md, spec quality matrices, and inventing product rules. Implementation must also wait until sync readiness passes.

Why does quick-fix reject a task with more than 3 cards?▼

The small-batch ceiling of 1-3 cards keeps the Quick path scoped to tiny changes. More independently verifiable outputs indicate the work is larger than a quick fix and should upgrade to Lite or Full planning.