mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-10-16 01:37:05 +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
58 lines
3.1 KiB
Markdown
58 lines
3.1 KiB
Markdown
# /architecture-decision — Retrofit Mode
|
|
|
|
> Part of `/architecture-decision`. `SKILL.md` names when to read this file; the settings it
|
|
> resolved and the rules under its later headings still apply here.
|
|
|
|
**If the argument starts with `retrofit` followed by a file path**
|
|
|
|
(e.g., `/architecture-decision retrofit docs/architecture/adr-0001-event-system.md`):
|
|
|
|
Enter **retrofit mode**:
|
|
|
|
1. Read the existing ADR file completely.
|
|
2. Identify which template sections are present by scanning headings:
|
|
- `## Status` — **BLOCKING if missing**: `/story-readiness` cannot check ADR acceptance
|
|
- `## ADR Dependencies` — HIGH if missing: dependency ordering breaks
|
|
- `## Engine Compatibility` — HIGH if missing: post-cutoff risk unknown
|
|
- `## GDD Requirements Addressed` — MEDIUM if missing: traceability lost
|
|
- `## Date` — MEDIUM if missing, and no `## Last Verified` either: `/create-stories`
|
|
stamps stories with it and `/dev-story` compares against it, so without it a
|
|
story can never tell whether the ADR changed
|
|
3. Present to the user:
|
|
```
|
|
## Retrofit: [ADR title]
|
|
File: [path]
|
|
|
|
Sections already present (will not be touched):
|
|
✓ Status: [current value, or "MISSING — will add"]
|
|
✓ [section]
|
|
|
|
Missing sections to add:
|
|
✗ Status — BLOCKING (stories cannot validate ADR acceptance without this)
|
|
✗ ADR Dependencies — HIGH
|
|
✗ Engine Compatibility — HIGH
|
|
```
|
|
4. Ask: "Shall I add the [N] missing sections? I will not modify any existing content."
|
|
If no: write nothing, and report the missing sections by name.
|
|
5. If yes:
|
|
- For **Status**: ask the user — "What is the current status of this decision?"
|
|
Options: "Proposed", "Accepted", "Deprecated", "Superseded by ADR-XXXX"
|
|
An `Accepted` answer — a decision already in force — is not written as
|
|
given: write `Proposed`, add the other missing sections, then run
|
|
acceptance mode (below) on this ADR. Its dependency check, confirmation and
|
|
story unblocking apply here too; it stays the only path that sets `Accepted`.
|
|
- For **ADR Dependencies**: ask — "Does this decision depend on any other ADR?
|
|
Does it enable or block any other ADR or epic?" Accept "None" for each field.
|
|
- For **Engine Compatibility**: read the engine reference docs (same as Step 1 below)
|
|
and ask the user to confirm the domain. Then generate the table with verified data.
|
|
- For **GDD Requirements Addressed**: ask — "Which GDD systems motivated this decision?
|
|
What specific requirement in each GDD does this ADR address?"
|
|
- Append each missing section to the ADR file using the Edit tool.
|
|
- For **Date** (counted only when there is no `## Last Verified`): append
|
|
`## Date` with today's date — even when it is the only missing section, the
|
|
case `/dev-story` sends you here for — and say that it records the retrofit,
|
|
not when the decision was made.
|
|
- **Never modify any existing section.** Only append or fill absent sections.
|
|
6. Suggest: "Run `/architecture-review` to re-validate coverage now that this ADR
|
|
has its Status and Dependencies fields."
|