agentleFS
Sign inStart free
ChianWChianW/C31/skills/utils/gsd-quick/SKILL.md

gsd-quick

Skill1 starsChanged 3 months agoMITView on GitHub

Output language: Respond automatically in the user's conversation language. Execute a small task without the overhead of full GSD workflow. No .planning/phases/ files. Minimal ceremony. Maximum speed. Use gsd-quick when: - Task takes < 15 minutes - No design decisions needed - No risk of breaking existing work - User explicitly says "quick" or "小事" Do NOT use when: - Task touches core architecture - Task requires user research or validation - Task is part of a milestone deliverable →…

5 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use gsd-next and gsd-onboard.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • open-gsdSkill

    gsd-next

    Smart entry — detect project state and route to the right next GSD action.

    Also in 3 projects that use this

  • open-gsdSkill

    gsd-onboard

    Guide existing codebase onboarding through mapping, doc ingest, and planning setup

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No design decisions needed

    line 27
  2. Distinctive:

    No risk of breaking existing work

    line 28
  3. Very specific:

    Read memory/.planning/STATE.md (if exists) — note current position only

    line 41
  4. Distinctive:

    Ask user (or infer from context):

    line 42
  5. Distinctive:

    Do the task directly — no subagents unless necessary

    line 49
  6. Distinctive:

    Use surgical changes (Karpathy Principle 3)

    line 50
  7. Very specific:

    If error occurs → switch to C31-debug automatically

    line 51
  8. Distinctive:

    No STATE.md update. No ROADMAP.md update: Keep project state clean.

    line 77

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Multilingual Triggers

LanguageTrigger phrases
ENquick, quickly, fast, 速战速决, 小事, 改一下, 查一下, 看一下, 简单, trivial, just do it
ZH快速, 简单改一下
JA素早く, 簡単な変更

Output language: Respond automatically in the user's conversation language.

gsd-quick — Just Do It

Execute a small task without the overhead of full GSD workflow. No .planning/phases/ files. Minimal ceremony. Maximum speed.

When to Use

Use gsd-quick when:

  • Task takes < 15 minutes
  • No design decisions needed
  • No risk of breaking existing work
  • User explicitly says "quick" or "小事"

Do NOT use when:

  • Task touches core architecture
  • Task requires user research or validation
  • Task is part of a milestone deliverable → Use full C31 workflow instead

Workflow

Phase 1: Load & Triage (10 seconds)

  1. Read memory/.planning/STATE.md (if exists) — note current position only
  2. Ask user (or infer from context):
    • What exactly to do?
    • Any constraints? (read-only? specific file?)
    • Expected output?

Phase 2: Execute (Immediate)

  1. Do the task directly — no subagents unless necessary
  2. Use surgical changes (Karpathy Principle 3)
  3. If error occurs → switch to C31-debug automatically

Phase 3: Record (Lightweight)

Write to memory/.planning/quick/YYMMDD-slug.md:

# Quick Task — <date>

## Request
<what_user_asked>

## Done
<what_was_done>

## Files Changed
- <file_1>
- <file_2>

## Time Spent
<minutes>

## Notes
<anything_to_remember>

No STATE.md update. No ROADMAP.md update. Keep project state clean.

Success Output

✅ Quick task done — <minutes> min

Changed:
  - <file_1>
  - <file_2>

Recorded: memory/.planning/quick/YYMMDD-slug.md

Example Tasks

"Quick: fix the typo in README"
"Fast: check why cron job failed yesterday"
"小事: add timezone note to AGENTS.md"
"查一下: what does this error mean"

Auto-Invoke

<auto_invoke> <trigger_phrases>

  • "quick"
  • "quickly"
  • "fast"
  • "速战速决"
  • "小事"
  • "改一下"
  • "查一下"
  • "看一下"
  • "简单"
  • "trivial"
  • "just do it"
  • "顺手" </trigger_phrases> </auto_invoke>

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free