Files
msd-core/get-shit-done/workflows/fast.md
Tom Boucher 73c1af5168 fix(#2543): replace legacy /gsd-<cmd> syntax with /gsd:<cmd> across all source files (#2595)
Commands are now installed as commands/gsd/<name>.md and invoked as
/gsd:<name> in Claude Code. The old hyphen form /gsd-<name> was still
hardcoded in hundreds of places across workflows, references, templates,
lib modules, and command files — causing "Unknown command" errors
whenever GSD suggested a command to the user.

Replace all /gsd-<cmd> occurrences where <cmd> is a known command name
(derived at runtime from commands/gsd/*.md) using a targeted Node.js
script. Agent names, tool names (gsd-sdk, gsd-tools), directory names,
and path fragments are not touched.

Adds regression test tests/bug-2543-gsd-slash-namespace.test.cjs that
enforces zero legacy occurrences going forward. Removes inverted
tests/stale-colon-refs.test.cjs (bug #1748) which enforced the now-obsolete
hyphen form; the new bug-2543 test supersedes it. Updates 5 assertion
tests that hardcoded the old hyphen form to accept the new colon form.

Closes #2543

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-22 12:04:25 -04:00

2.6 KiB

Execute a trivial task inline without subagent overhead. No PLAN.md, no Task spawning, no research, no plan checking. Just: understand → do → commit → log.

For tasks like: fix a typo, update a config value, add a missing import, rename a variable, commit uncommitted work, add a .gitignore entry, bump a version number.

Use /gsd:quick for anything that needs multi-step planning or research.

Parse `$ARGUMENTS` for the task description.

If empty, ask:

What's the quick fix? (one sentence)

Store as $TASK.

**Before doing anything, verify this is actually trivial.**

A task is trivial if it can be completed in:

  • ≤ 3 file edits
  • ≤ 1 minute of work
  • No new dependencies or architecture changes
  • No research needed

If the task seems non-trivial (multi-file refactor, new feature, needs research), say:

This looks like it needs planning. Use /gsd:quick instead:
  /gsd:quick "{task description}"

And stop.

Do the work directly:
  1. Read the relevant file(s)
  2. Make the change(s)
  3. Verify the change works (run existing tests if applicable, or do a quick sanity check)

No PLAN.md. Just do it.

Commit the change atomically:
git add -A
git commit -m "fix: {concise description of what changed}"

Use conventional commit format: fix:, feat:, docs:, chore:, refactor: as appropriate.

If `.planning/STATE.md` exists, append to the "Quick Tasks Completed" table. If the table doesn't exist, skip this step silently.
# Check if STATE.md has quick tasks table
if grep -q "Quick Tasks Completed" .planning/STATE.md 2>/dev/null; then
  # Append entry — workflow handles the format
  echo "| $(date +%Y-%m-%d) | fast | $TASK | ✅ |" >> .planning/STATE.md
fi
Report completion:
✅ Done: {what was changed}
   Commit: {short hash}
   Files: {list of changed files}

No next-step suggestions. No workflow routing. Just done.

- NEVER spawn a Task/subagent — this runs inline - NEVER create PLAN.md or SUMMARY.md files - NEVER run research or plan-checking - If the task takes more than 3 file edits, STOP and redirect to /gsd:quick - If you're unsure how to implement it, STOP and redirect to /gsd:quick

<success_criteria>

  • Task completed in current context (no subagents)
  • Atomic git commit with conventional message
  • STATE.md updated if it exists
  • Total operation under 2 minutes wall time </success_criteria>