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
@@ -7,7 +7,9 @@ allowed-tools: Read, Glob, Grep, Write, Edit, AskUserQuestion, Bash(bash "*/.cla
|
||||
model: sonnet
|
||||
---
|
||||
|
||||
!`bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys automation`
|
||||
!`bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys automation,workflow`
|
||||
|
||||
# Tech Debt
|
||||
|
||||
|
||||
|
||||
@@ -135,7 +137,7 @@ one decimal and written to Priority. Higher scores first; ties go to the older
|
||||
`Added` date. An item whose Impact or Effort is `—` gets no score: list it after
|
||||
the scored items as "not scored — [column] not judged" rather than guessing one.
|
||||
|
||||
Re-sort the register by priority score and recommend which items to include in the next sprint.
|
||||
Re-sort the register by priority score and recommend which items to include in the next sprint (at `workflow: minimal`, which has no sprints, which to build next).
|
||||
|
||||
Present the re-prioritized register to the user.
|
||||
|
||||
@@ -167,7 +169,7 @@ Output the report to the user. This mode is read-only — no files are written.
|
||||
|
||||
## Phase 3: Next Steps
|
||||
|
||||
- Run `/sprint-plan` to schedule high-priority debt items into the next sprint.
|
||||
- Run `/sprint-plan` to schedule high-priority debt items into the next sprint (at `workflow: minimal`, which has no sprints, add them to the brief's build order instead).
|
||||
- Run `/tech-debt report` at the start of each sprint to track debt trends over time.
|
||||
|
||||
### Debt Register Format
|
||||
|
||||
Reference in New Issue
Block a user