← ClaudeAtlas

spec-sessionlisted

This skill should be used when a session SPECIFIES a Genesis change before it is planned or built: shaping the problem, the PRD, the architecture and the tickets a build session will take. Load `genesis-development` (the shared core) first. Do NOT load it for building (`build-session`), closing open PRs (`closing-session`), or post-merge verification (`validating-merges`).
WingedGuardian/GENesis-AGI · ★ 103 · AI & Automation · score 84
Install: claude install-skill WingedGuardian/GENesis-AGI
# Spec session **Load `genesis-development` (the shared core) first** if this session has not: it holds the review-chain, evidence and private-data rules every session uses. A minimal skill for now; its process is designed later. Also read: - the core's "Due diligence before building" and "Architecture Review" (`.claude/skills/genesis-development/SKILL.md`); - `.claude/skills/genesis-development/references/due-diligence.md` and `.claude/skills/genesis-development/references/plan-docs.md`; - `.claude/docs/premise-check.md`, and the `evaluate` skill for any external candidate; - `build-session`'s "Generalizability Gate" before a spec names where code runs. **Intent scenarios, when the install keeps a holdout.** If `.venv/bin/python scripts/holdout_runner.py --has-holdout` (from the main checkout) prints `holdout: present`, then once the issue's intent is final and before it goes to a builder, spawn the `holdout-writer` subagent IN THE FOREGROUND with the issue number and "intent". It adds scenarios that fail on the default branch until the change lands, and reports only their ids and `Protects` lines. Keep the scenarios out of the issue and the spec, and put this line in the issue: "The PR that finishes this issue must say `Closes #N`; if the work is split, earlier PRs say `Part of #N`." An intent scenario is judged only against a PR that closes its issue. `docs/reference/holdout.md` has the rules. ### Plan documents carry a structured header A plan doc that outlives