Reverse Document

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — INTEGRATED SYSTEM FIRST: this skill is one piece of the complete "Claude Code Game Studios" template (49 agents, 74 skills, studio templates and a studio CLAUDE.md, per the repository README). Each skill assumes that template is installed, with its conventions, its project.yaml / project.local.yaml configuration, its .claude/docs/ mode documents, its hooks (for example hooks/yaml-helper.sh, outside this skill's folder) and its .claude/scripts/ helpers. Installing this listing alone copies only this skill's folder, without the rest of the system: the skill may reference template agents, files, hooks or scripts that are absent outside the full template, and it may not run as designed on its own. No account, no key and no payment are needed to copy the files, and nothing is run during installation. Install "Reverse Document" for me. The skill itself generates missing documentation from existing implementation: given a type (design, architecture or concept) and a code or prototype path, it analyses the code, asks clarifying questions about intent (unanswered questions are carried into the document verbatim as INTENT UNKNOWN, never silently resolved), stops if the implementation holds too little to document (no mechanics, formulas or tuning values), and drafts a document from the template's templates/ files — which live outside this skill's folder. Outputs are tier-scaled: a full or standard GDD at design/gdd/[system-name].md, a one-page brief at minimal tier, an ADR at docs/architecture/, or a concept doc under prototypes/ or design/concepts/; every document it writes is stamped at the top with a provenance banner stating it was reverse-documented from the implementation at a named commit. In collaborative mode it shows the draft and asks "May I write this to [output path]?" before writing; one disclosed exception — in guided mode, when the target file already exists, it presents the diff and proceeds without waiting for an explicit yes (in autonomous mode it writes and logs). Its allowed-tools list contains no AskUserQuestion; its questions are plain conversation. It resolves the studio configuration (workflow, system_overrides, automation) by running the template's hooks/yaml-helper.sh, outside this skill's folder. Its frontmatter pins model: sonnet. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/reverse-document/ folder at the pinned commit: 1 file in total) Pinned version: install the code at commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/Donchitos/Claude-Code-Game-Studios into a temporary folder, check out commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418, and copy the .claude/skills/reverse-document/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 c498c673b8f1b8d5634e33839b6117b17a827c2f41207acb115eb276f716189a If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 1 file: SKILL.md only. Nothing in the folder is a program; it is instructions the agent follows at use time. The document templates it uses at use time (templates/design-doc-from-implementation.md, templates/architecture-doc-from-code.md, templates/concept-doc-from-prototype.md) are NOT in this folder — they belong to the template. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit, and no project of mine is audited, read or modified. - Integrated-system reality, from the file: at use time the skill runs the template's hooks/yaml-helper.sh to resolve workflow, system_overrides and automation, follows .claude/docs/automation-modes.md, workflow-modes.md and code-root-resolution.md, uses the template's templates/ documents, and reads my project's code under its code root (src/, Assets/ or Source/) or prototypes/ — files that live outside this skill's folder and are absent in a standalone install, so it cannot run as designed on its own. - At use time it writes one generated document (GDD, brief, ADR or concept doc, paths in the introduction above), stamped with its reverse-documented provenance banner. In collaborative mode it asks before writing; disclosed exception: in guided mode an already-existing target is updated after showing the diff, without waiting for an explicit yes, and in autonomous mode it writes and logs the decision. No third-party service, account or credential is named in the file. - Do not analyse any code, do not run any template hook, and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for it later. 3. When I say "yes, install", install it as a skill: copy the whole reverse-document folder into the agent's skills directory, in a folder named exactly "reverse-document", keeping its 1 file in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: reverse-document), the 1 file in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that it belongs to the full Claude Code Game Studios template and may not run standalone (its document templates and yaml-helper hook live in the template, outside this folder), and that its generated documents carry a reverse-documented provenance banner, with the guided-mode existing-file exception disclosed in this prompt). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.