mirror of https://github.com/Donchitos/Claude-Code-Game-Studios.git synced 2026-10-16 10:17:06 +00:00

Files

T

DonchitosandClaude Opus 5.5 be8993bbc5 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

2026-10-08 17:52:48 +11:00

1.9 KiB

Raw Permalink Blame History

/create-architecture — Phase 5: ADR Audit and Traceability Check

Part of /create-architecture. SKILL.md names when to read this file; the settings it resolved and the rules under its later headings still apply here.

Phase 5: ADR Audit + Traceability Check

Review all existing ADRs from Phase 0c against both the architecture built in Phases 1-4 AND the Technical Requirements Baseline from Phase 0b.

ADR Quality Check

For each ADR:

Does it have an Engine Compatibility section?
Is the engine version recorded?
Are post-cutoff APIs flagged?
Does it have a "GDD Requirements Addressed" section?
Does it conflict with the layer/ownership decisions made in this session?
Is it still valid for the pinned engine version?

ADR	Engine Compat	Version	GDD Linkage	Conflicts	Valid
ADR-0001: [title]	✅/❌	✅/❌	✅/❌	None/[conflict]	✅/⚠️

Traceability Coverage Check

Map every requirement from the Technical Requirements Baseline to existing ADRs. For each requirement, check if any ADR's "GDD Requirements Addressed" section or decision text covers it:

Req ID	Requirement	ADR Coverage	Status
TR-combat-001	Hitbox detection per-frame	ADR-0003	✅
TR-combat-002	Combo state machine	—	❌ GAP

Count: X covered, Y gaps. For each gap, it becomes a Required New ADR.

Required New ADRs

List all decisions made during this architecture session (Phases 1-4) that do not yet have a corresponding ADR, PLUS all uncovered Technical Requirements. Group by layer — Foundation first:

Foundation Layer (must create before any coding):

/architecture-decision [title] → covers: TR-[id], TR-[id]

Core Layer:

/architecture-decision [title] → covers: TR-[id]

1.9 KiB Raw Permalink Blame History