fix: separate parallelization question from config creation
Moves config.json creation to its own step so the parallelization question isn't skipped. Matches pattern used by mode and depth steps. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -264,6 +264,10 @@ Use AskUserQuestion:
|
|||||||
|
|
||||||
**Parallelization allows `/gsd:execute-phase` to spawn multiple agents for independent plans.** Useful for "walk away, come back to completed work" execution. Can be changed later in config.json.
|
**Parallelization allows `/gsd:execute-phase` to spawn multiple agents for independent plans.** Useful for "walk away, come back to completed work" execution. Can be changed later in config.json.
|
||||||
|
|
||||||
|
</step>
|
||||||
|
|
||||||
|
<step name="config">
|
||||||
|
|
||||||
Create `.planning/config.json` with chosen mode, depth, and parallelization using `templates/config.json` structure.
|
Create `.planning/config.json` with chosen mode, depth, and parallelization using `templates/config.json` structure.
|
||||||
|
|
||||||
</step>
|
</step>
|
||||||
|
|||||||
Reference in New Issue
Block a user