docs(workflow): require gsd worktrees before edits

This commit is contained in:
curo1305
2026-06-23 14:10:41 +02:00
parent fac7721dd9
commit 3514fdcf3a
2 changed files with 8 additions and 0 deletions
+4
View File
@@ -102,6 +102,10 @@ View (thin data-provider)
This project uses the GSD (Get Shit Done) planning workflow. Planning artifacts live in `.planning/`. This project uses the GSD (Get Shit Done) planning workflow. Planning artifacts live in `.planning/`.
### Worktree-first rule (Non-Negotiable)
Before any GSD workflow or agent edits project files, create or switch into a dedicated git worktree for that GSD task. Discussion, read-only inspection, and status checks may run in the main checkout, but planning artifacts, code changes, docs changes, and workflow state mutations must happen inside the task worktree. If a workflow would edit files and no worktree exists yet, stop and create one first.
### Key files ### Key files
| File | Purpose | | File | Purpose |
+4
View File
@@ -108,6 +108,10 @@ View (thin data-provider)
This project uses the GSD (Get Shit Done) planning workflow. Planning artifacts live in `.planning/`. This project uses the GSD (Get Shit Done) planning workflow. Planning artifacts live in `.planning/`.
### Worktree-first rule (Non-Negotiable)
Before any GSD workflow or agent edits project files, create or switch into a dedicated git worktree for that GSD task. Discussion, read-only inspection, and status checks may run in the main checkout, but planning artifacts, code changes, docs changes, and workflow state mutations must happen inside the task worktree. If a workflow would edit files and no worktree exists yet, stop and create one first.
### Key files ### Key files
| File | Purpose | | File | Purpose |