b181c2f8c3
* fix(#3039): clamp max/xhigh effort to high for Claude-runtime skills effort: max in plan-phase, execute-phase, and autonomous SKILL.md frontmatter was passed through as output_config.effort, which the Anthropic API rejects when extended thinking is disabled (400: effort 'max' is not supported when thinking is disabled on this model). The frontmatter is static at install time and the installer cannot know whether thinking will be on or off at invocation. normalizeClaudeSkillEffort now clamps both 'max' and 'xhigh' to 'high' — the maximum value that works in both thinking states on all supported models. Applied in both src/runtime-artifact-conversion.cts and bin/install.js. * chore(#3039): backfill changeset PR number 3119 * fix(#3039): regenerate skills with clamped effort: high --------- Co-authored-by: sim <sim@local>
66 lines
2.8 KiB
Markdown
66 lines
2.8 KiB
Markdown
---
|
|
name: gsd-execute-phase
|
|
description: "Execute all plans in a phase with wave-based parallelization"
|
|
argument-hint: "<phase-number> [--wave N] [--gaps-only] [--interactive] [--tdd]"
|
|
effort: high
|
|
allowed-tools:
|
|
- Read
|
|
- Write
|
|
- Edit
|
|
- Glob
|
|
- Grep
|
|
- Bash
|
|
- Agent
|
|
- TodoWrite
|
|
- AskUserQuestion
|
|
---
|
|
|
|
<objective>
|
|
Execute all plans in a phase using wave-based parallel execution.
|
|
|
|
Orchestrator stays lean: discover plans, analyze dependencies, group into waves, spawn subagents, collect results. Each subagent loads the full execute-plan context and handles its own plan.
|
|
|
|
Optional wave filter:
|
|
- `--wave N` executes only Wave `N` for pacing, quota management, or staged rollout
|
|
- phase verification/completion still only happens when no incomplete plans remain after the selected wave finishes
|
|
|
|
Flag handling rule:
|
|
- The optional flags documented below are available behaviors, not implied active behaviors
|
|
- A flag is active only when its literal token appears in `$ARGUMENTS`
|
|
- If a documented flag is absent from `$ARGUMENTS`, treat it as inactive
|
|
|
|
Context budget: ~15% orchestrator, 100% fresh per subagent.
|
|
</objective>
|
|
|
|
<execution_context>
|
|
@~/.claude/gsd-core/workflows/execute-phase.md
|
|
@~/.claude/gsd-core/references/ui-brand.md
|
|
</execution_context>
|
|
|
|
<runtime_note>
|
|
**Copilot (VS Code):** Use `vscode_askquestions` wherever this workflow calls `AskUserQuestion`. They are equivalent — `vscode_askquestions` is the VS Code Copilot implementation of the same interactive question API.
|
|
</runtime_note>
|
|
|
|
<context>
|
|
Phase: $ARGUMENTS
|
|
|
|
**Available optional flags (documentation only — not automatically active):**
|
|
- `--wave N` — Execute only Wave `N` in the phase. Use when you want to pace execution or stay inside usage limits.
|
|
- `--gaps-only` — Execute only gap closure plans (plans with `gap_closure: true` in frontmatter). Use after verify-work creates fix plans.
|
|
- `--interactive` — Execute plans sequentially inline (no subagents) with user checkpoints between tasks. Lower token usage, pair-programming style. Best for small phases, bug fixes, and verification gaps.
|
|
|
|
**Active flags must be derived from `$ARGUMENTS`:**
|
|
- `--wave N` is active only if the literal `--wave` token is present in `$ARGUMENTS`
|
|
- `--gaps-only` is active only if the literal `--gaps-only` token is present in `$ARGUMENTS`
|
|
- `--interactive` is active only if the literal `--interactive` token is present in `$ARGUMENTS`
|
|
- If none of these tokens appear, run the standard full-phase execution flow with no flag-specific filtering
|
|
- Do not infer that a flag is active just because it is documented in this prompt
|
|
|
|
Context files are resolved inside the workflow via `gsd-tools query init.execute-phase` and per-subagent `<files_to_read>` blocks.
|
|
</context>
|
|
|
|
<process>
|
|
Execute end-to-end.
|
|
Preserve all workflow gates (wave execution, checkpoint handling, verification, state updates, routing).
|
|
</process>
|