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.
If empty, ask:
What's the quick fix? (one sentence)
Store as $TASK.
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.
- Read the relevant file(s)
- Make the change(s)
- Verify the change works (run existing tests if applicable, or do a quick sanity check)
No PLAN.md. Just do it.
git add -A
git commit -m "fix: {concise description of what changed}"
Use conventional commit format: fix:, feat:, docs:, chore:, refactor: as appropriate.
# 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
✅ Done: {what was changed}
Commit: {short hash}
Files: {list of changed files}
No next-step suggestions. No workflow routing. Just done.