mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-10-16 10:17:06 +00:00
DonchitosandClaude Opus 5.5
be8993bbc5
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
2.0 KiB
2.0 KiB
/story-done — Phase 2: Read the Story
Part of
/story-done.SKILL.mdnames when to read this file; the settings it resolved and the rules under its later headings still apply here.
Phase 2: Read the Story
Read the full story file. Extract and hold in context:
- Story name and ID
- GDD Requirement TR-ID(s) referenced (e.g.,
TR-combat-001) - Manifest Version embedded in the story header (e.g.,
2026-03-10) - ADR reference(s) referenced
- Acceptance Criteria — the complete list (every checkbox item)
- Implementation files — files listed under "files to create/modify"
- Story Type — the
Type:field from the story header (Logic / Integration / Visual/Feel / UI / Config/Data) - Engine notes — any engine-specific constraints noted
- Definition of Done — if present, the story-level DoD
- Estimated vs actual scope — if an estimate was noted
Also read:
docs/architecture/tr-registry.yaml— grep the story's TR-IDs (Grep pattern="id: <each TR-ID>\s*$" path="docs/architecture/tr-registry.yaml" output_mode="content" -A 6), not a full read of the registry. Read the currentrequirementtext from each matched entry. This is the source of truth for what the GDD required — do not use any requirement text that may be quoted inline in the story (it may be stale).- The referenced GDD section — just the acceptance criteria and key rules, not the full document. Use this to cross-check the registry text is still accurate.
- The referenced ADR(s) — just the
## Decisionand## Consequencessections, never an unbounded full read. Map headings first (Grep pattern="^## " path="docs/architecture/[adr-file].md" output_mode="content" -n), then bounded-Readonly those two spans. This is the exact same content Phase 4 item 3's ADR constraints check needs — hold it here, do not re-read it there. docs/architecture/control-manifest.mdheader — extract the currentManifest Version:date (used in Phase 4 staleness check)