d4767ac2e0
* fix: replace /gsd: command format with /gsd- skill format in all suggestions All next-step suggestions shown to users were still using the old colon format (/gsd:xxx) which cannot be copy-pasted as skills. Migrated all occurrences across agents/, commands/, get-shit-done/, docs/, README files, bin/install.js (hardcoded defaults for claude runtime), and get-shit-done/bin/lib/*.cjs (generate-claude-md templates and error messages). Updated tests to assert new hyphen format instead of old colon format. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: migrate remaining /gsd: format to /gsd- in hooks, workflows, and sdk Addresses remaining user-facing occurrences missed in the initial migration: - hooks/: fix 4 user-facing messages (pause-work, update, fast, quick) and 2 comments in gsd-workflow-guard.js - get-shit-done/workflows/: fix 21 Skill() literal calls that Claude executes directly (installer does not transform workflow content) - sdk/prompt-sanitizer.ts: update regex to strip /gsd- format in addition to legacy /gsd: format; update JSDoc comment - tests/: update autonomous-ui-steps, prompt-sanitizer to assert new format Note: commands/gsd/*.md frontmatter (name: gsd:xxx) intentionally unchanged — installer derives skillName from directory path, not the name field. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix(plan-phase): preserve --chain flag in auto-advance sync and handle ui-phase gate in chain mode Bug 1: step 15 sync-flag check only guarded against --auto, causing _auto_chain_active to be cleared when plan-phase is invoked without --auto in ARGUMENTS even though a --chain pipeline was active. Added --chain to the guard condition, matching discuss-phase behaviour. Bug 2: UI Design Contract gate (step 5.6) always exited the workflow when UI-SPEC was missing, breaking the discuss --chain pipeline silently. When _auto_chain_active is true, the gate now auto-invokes gsd-ui-phase --auto via Skill() and continues to step 6 without prompting. Manual invocations retain the existing AskUserQuestion flow. * fix: remove <sub>/clear</sub> pattern and duplicate old-format command in discuss-phase.md --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
106 lines
2.6 KiB
Markdown
106 lines
2.6 KiB
Markdown
<purpose>
|
|
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.
|
|
</purpose>
|
|
|
|
<process>
|
|
|
|
<step name="parse_task">
|
|
Parse `$ARGUMENTS` for the task description.
|
|
|
|
If empty, ask:
|
|
```
|
|
What's the quick fix? (one sentence)
|
|
```
|
|
|
|
Store as `$TASK`.
|
|
</step>
|
|
|
|
<step name="scope_check">
|
|
**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.
|
|
</step>
|
|
|
|
<step name="execute_inline">
|
|
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.
|
|
</step>
|
|
|
|
<step name="commit">
|
|
Commit the change atomically:
|
|
|
|
```bash
|
|
git add -A
|
|
git commit -m "fix: {concise description of what changed}"
|
|
```
|
|
|
|
Use conventional commit format: `fix:`, `feat:`, `docs:`, `chore:`, `refactor:` as appropriate.
|
|
</step>
|
|
|
|
<step name="log_to_state">
|
|
If `.planning/STATE.md` exists, append to the "Quick Tasks Completed" table.
|
|
If the table doesn't exist, skip this step silently.
|
|
|
|
```bash
|
|
# 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
|
|
```
|
|
</step>
|
|
|
|
<step name="done">
|
|
Report completion:
|
|
|
|
```
|
|
✅ Done: {what was changed}
|
|
Commit: {short hash}
|
|
Files: {list of changed files}
|
|
```
|
|
|
|
No next-step suggestions. No workflow routing. Just done.
|
|
</step>
|
|
|
|
</process>
|
|
|
|
<guardrails>
|
|
- 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
|
|
</guardrails>
|
|
|
|
<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>
|