mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-10-16 01:37:05 +00:00
Release 1.1.3 — long skills keep their later steps
Fix release for 1.1.2: the 14 longest skills keep their later phases after a compaction, a question nobody answered is never taken as an answer, settings read the same from a subfolder, the commit check works for a project in a subfolder of a larger repository, every skill opens with a title, and the shipped allow rules no longer approve deleting a branch or writing files without asking. Details in CHANGELOG.md; upgrade steps in UPGRADING.md (v1.1.2 → v1.1.3). Refs #83 Refs #133 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0185en4t76fPn7315q4c3nko
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
b21fa0f7f2
commit
be8993bbc5
@@ -59,23 +59,14 @@ When the user asks you to make a decision or resolve a conflict:
|
||||
- Once decided, commit fully — document and cascade the decision
|
||||
- Set up success metrics — "we'll know this was right if..."
|
||||
|
||||
#### Structured Decision UI
|
||||
#### Structured Decisions
|
||||
|
||||
Use the `AskUserQuestion` tool to present strategic decisions as a selectable UI.
|
||||
Follow the **Explain → Capture** pattern:
|
||||
|
||||
1. **Explain first** — Write full strategic analysis in conversation: options with
|
||||
pillar alignment, downstream consequences, risk assessment, recommendation.
|
||||
2. **Capture the decision** — Call `AskUserQuestion` with concise option labels.
|
||||
|
||||
**Guidelines:**
|
||||
- Use at every decision point (strategic options in step 3, clarifying questions in step 1)
|
||||
- Batch up to 4 independent questions in one call
|
||||
- Labels: 1-5 words. Descriptions: 1 sentence with key trade-off.
|
||||
- Add "(Recommended)" to your preferred option's label
|
||||
- For open-ended context gathering, use conversation instead
|
||||
- If running as a Task subagent, structure text so the orchestrator can present
|
||||
options via `AskUserQuestion`
|
||||
`AskUserQuestion` is not in your `tools:` grant, so whoever called you presents
|
||||
your decisions. At each decision point, write the full analysis first (pros/cons,
|
||||
theory, examples, pillar alignment), then end with the options as a short list:
|
||||
1-5 word labels, a one-sentence description each (for strategic decisions, the
|
||||
key trade-off), "(Recommended)" on your pick, at most 4 independent questions.
|
||||
Open-ended questions and file-write confirmations stay in plain conversation.
|
||||
|
||||
### Key Responsibilities
|
||||
|
||||
|
||||
Reference in New Issue
Block a user