nccgs 2.1.1 → 3.0.0-rc.2

package/.claude/skills/context-pack/references/astra.md

@@ -1,12 +0,0 @@
-# Context Pack — astra-claude
-
-Read [the pipeline protocol](../../../nccgs/protocols/astra-claude.md) and
-[generated routing](../../../nccgs/routing.generated.md). Use Astra's supplied plan,
-requirements, and exact context references. Never substitute a legacy procedure.
-
-Astra owns this workflow and its canonical outputs. Claude only inspects relevant
-inputs and returns factual constraints, missing information, or proposed amendments.
-Do not create a replacement plan/document or sign off as Astra.
-
-Use [task gate commands](../../../nccgs/protocols/task-gates.md) for evidence and
-state transitions. Report outcome, evidence, pending decisions, and next owner.

package/.claude/skills/context-pack/references/legacy.md

@@ -1,7 +0,0 @@
-# Context Pack
-
-Read `.nccgs/project.yaml`, `.nccgs/state.md`, and the active context packet when present. Preserve Product Owner authority and unrelated work.
-
-Read the [context packet protocol](../../../nccgs/protocols/context-packets.md) and project policy. Resolve the feature ID, objective, classification, domains, and accountable owner. Map exact canonical sections and decision summaries with source revisions; list writable, read-only, protected, and generated paths; record dependencies, constraints, out-of-scope behavior, verification, and PO gates. Create or update `.nccgs/context/<feature-id>.yaml` from the template. Do not paste whole documents. Mark contradictions and the exact reason for any required full-source read. Report packet path and unresolved inputs.
-
-Return outcome, evidence, affected records, blockers or decisions, residual risk, and the exact next workflow. Do not claim DONE unless this is the `closure` skill and every configured gate passes.

package/.claude/skills/dependency-review/SKILL.md

@@ -1,22 +0,0 @@
----
-name: dependency-review
-description: Evaluates a proposed Unity package, SDK, service, or external dependency for necessity, fit, licensing, security, maintenance, compatibility, lock-in, migration, and rollback before adoption.
-allowed-tools: Read, Glob, Grep, Bash, Agent, WebSearch, WebFetch
----
-
-# Dependency Review
-
-Resolve execution policy from .nccgs/execution.json before model routing. Missing
-execution.json means compatibility; model profile alone never removes obligations.
-
-- standalone: load the [shared standalone procedure](../../nccgs/protocols/standalone.md)
-  for this workflow, using its intake, mode, bounded domain steps and report rules.
-  Do not load the compatibility branches or inherit their external approval chain.
-- compatibility: read models.profile from .nccgs/project.yaml and load exactly one:
-  astra-claude uses [Astra/Claude procedure](references/astra.md); quality, balanced
-  or inherit uses [Legacy procedure](references/legacy.md). Existing task records
-  retain their original gates even after project execution policy changes.
-
-Unknown execution policies or model profiles are configuration errors. External
-review in standalone is off, advisory or required according to execution policy;
-configured routes do not prove actual provider model or effort.

package/.claude/skills/dependency-review/references/astra.md

@@ -1,17 +0,0 @@
-# Dependency Review — astra-claude
-
-Read [the pipeline protocol](../../../nccgs/protocols/astra-claude.md) and
-[generated routing](../../../nccgs/routing.generated.md). Use Astra's supplied plan,
-requirements, and exact context references. Never substitute a legacy procedure.
-
-Domain objective: Evaluates a proposed Unity package, SDK, service, or external dependency for necessity, fit, licensing, security, maintenance, compatibility, lock-in, migration, and rollback before adoption.
-
-Work only inside the supplied plan and assigned write set. Activate an optional
-specialist with the agents command only when its domain is required. Keep one writer
-per path and use official Unity Skills for Editor/assets/runtime operations.
-
-This procedure is read-only: return evidence-backed findings and decisions to Astra
-or the implementer. Supplemental analysis does not replace the mandatory Fable gate.
-
-Use [task gate commands](../../../nccgs/protocols/task-gates.md) for evidence and
-state transitions. Report outcome, evidence, pending decisions, and next owner.

package/.claude/skills/dependency-review/references/legacy.md

@@ -1,7 +0,0 @@
-# Dependency Review
-
-Read `.nccgs/project.yaml`, `.nccgs/state.md`, and the active context packet when present. Preserve Product Owner authority and unrelated work.
-
-Remain read-only. Define the capability need and compare build, buy, existing-project, and no-change options. Verify current authoritative documentation, supported Unity/platform versions, license, data/privacy, operational cost, update policy, failure behavior, transitive risk, and exit plan. Recommend with evidence. Adoption or replacement requires explicit Product Owner authority and an architecture decision.
-
-Return outcome, evidence, affected records, blockers or decisions, residual risk, and the exact next workflow. Do not claim DONE unless this is the `closure` skill and every configured gate passes.

package/.claude/skills/design/SKILL.md

@@ -1,24 +0,0 @@
----
-name: design
-description: Designs or revises player-facing mechanics, systems, UX, levels, economy, narrative, content, or accessibility before implementation. Routes to focused design roles and preserves Product Owner control of subjective and canonical decisions.
-allowed-tools: Read, Glob, Grep, Write, Edit, Agent, AskUserQuestion, WebSearch, WebFetch
----
-
-# Design
-
-Resolve execution policy from .nccgs/execution.json before model routing. Missing
-execution.json means compatibility; model profile alone never removes obligations.
-
-- standalone: load the [shared standalone procedure](../../nccgs/protocols/standalone.md)
-  for this workflow, using its intake, mode, bounded domain steps and report rules.
-  Also load the [standalone design lifecycle](../../nccgs/protocols/design-lifecycle.md)
-  and follow its specific procedure for this workflow.
-  Do not load the compatibility branches or inherit their external approval chain.
-- compatibility: read models.profile from .nccgs/project.yaml and load exactly one:
-  astra-claude uses [Astra/Claude procedure](references/astra.md); quality, balanced
-  or inherit uses [Legacy procedure](references/legacy.md). Existing task records
-  retain their original gates even after project execution policy changes.
-
-Unknown execution policies or model profiles are configuration errors. External
-review in standalone is off, advisory or required according to execution policy;
-configured routes do not prove actual provider model or effort.

package/.claude/skills/design/references/astra.md

@@ -1,12 +0,0 @@
-# Design — astra-claude
-
-Read [the pipeline protocol](../../../nccgs/protocols/astra-claude.md) and
-[generated routing](../../../nccgs/routing.generated.md). Use Astra's supplied plan,
-requirements, and exact context references. Never substitute a legacy procedure.
-
-Astra owns this workflow and its canonical outputs. Claude only inspects relevant
-inputs and returns factual constraints, missing information, or proposed amendments.
-Do not create a replacement plan/document or sign off as Astra.
-
-Use [task gate commands](../../../nccgs/protocols/task-gates.md) for evidence and
-state transitions. Report outcome, evidence, pending decisions, and next owner.

package/.claude/skills/design/references/legacy.md

@@ -1,13 +0,0 @@
-# Design
-
-Produce implementation-ready design truth with the smallest complete set of specialized perspectives.
-
-Read policy, state, relevant pillars/canon, interacting requirements, and the code constraints needed for feasibility. Distinguish exploration, focused design, and CONTROLLED cross-system change.
-
-Select the accountable design role and only the specialists required by the domain: systems, level, economy, UX, accessibility, narrative, art, audio, live ops, or prototyping. Use Opus leadership only for cross-creative conflict or product-wide synthesis.
-
-Separate established facts from proposals and Product Owner decisions. Batch meaningful choices with real alternatives, tradeoffs, and a recommendation. Do not ask implementation trivia.
-
-Define applicable rules, states, formulas, feedback, dependencies, edge cases, tuning surfaces, objective acceptance criteria, subjective gates, out-of-scope behavior, and traceable requirement IDs. Consult technical roles for feasibility without letting implementation redefine intended design.
-
-Persist accepted changes in mapped canonical sources; do not create a parallel GDD tree. Run `/design-review` for STANDARD or CONTROLLED changes. If implementation is included and decisions are closed, hand the accepted contract to `/work`.

package/.claude/skills/design-review/SKILL.md

@@ -1,24 +0,0 @@
----
-name: design-review
-description: Reviews a proposed or changed game design for clarity, player intent, systemic interactions, balance, UX, accessibility, canon, feasibility, and testability without approving subjective choices.
-allowed-tools: Read, Glob, Grep, Agent
----
-
-# Design Review
-
-Resolve execution policy from .nccgs/execution.json before model routing. Missing
-execution.json means compatibility; model profile alone never removes obligations.
-
-- standalone: load the [shared standalone procedure](../../nccgs/protocols/standalone.md)
-  for this workflow, using its intake, mode, bounded domain steps and report rules.
-  Also load the [standalone design lifecycle](../../nccgs/protocols/design-lifecycle.md)
-  and follow its specific procedure for this workflow.
-  Do not load the compatibility branches or inherit their external approval chain.
-- compatibility: read models.profile from .nccgs/project.yaml and load exactly one:
-  astra-claude uses [Astra/Claude procedure](references/astra.md); quality, balanced
-  or inherit uses [Legacy procedure](references/legacy.md). Existing task records
-  retain their original gates even after project execution policy changes.
-
-Unknown execution policies or model profiles are configuration errors. External
-review in standalone is off, advisory or required according to execution policy;
-configured routes do not prove actual provider model or effort.

package/.claude/skills/design-review/references/astra.md

@@ -1,17 +0,0 @@
-# Design Review — astra-claude
-
-Read [the pipeline protocol](../../../nccgs/protocols/astra-claude.md) and
-[generated routing](../../../nccgs/routing.generated.md). Use Astra's supplied plan,
-requirements, and exact context references. Never substitute a legacy procedure.
-
-Domain objective: Reviews a proposed or changed game design for clarity, player intent, systemic interactions, balance, UX, accessibility, canon, feasibility, and testability without approving subjective choices.
-
-Work only inside the supplied plan and assigned write set. Activate an optional
-specialist with the agents command only when its domain is required. Keep one writer
-per path and use official Unity Skills for Editor/assets/runtime operations.
-
-This procedure is read-only: return evidence-backed findings and decisions to Astra
-or the implementer. Supplemental analysis does not replace the mandatory Fable gate.
-
-Use [task gate commands](../../../nccgs/protocols/task-gates.md) for evidence and
-state transitions. Report outcome, evidence, pending decisions, and next owner.

package/.claude/skills/design-review/references/legacy.md

@@ -1,7 +0,0 @@
-# Design Review
-
-Read `.nccgs/project.yaml`, `.nccgs/state.md`, and the active context packet when present. Preserve Product Owner authority and unrelated work.
-
-Remain read-only. Review the target against pillars, canonical decisions, interacting systems, platform constraints, and implementation evidence only where relevant. Use focused specialists for economy, UX, accessibility, level, narrative, art, or audio lenses. Separate contradictions, exploitable/degenerate behavior, untestable requirements, and optional improvements. Return prioritized findings, PO decisions, and implementation-readiness verdict.
-
-Return outcome, evidence, affected records, blockers or decisions, residual risk, and the exact next workflow. Do not claim DONE unless this is the `closure` skill and every configured gate passes.

package/.claude/skills/evidence-review/SKILL.md

@@ -1,22 +0,0 @@
----
-name: evidence-review
-description: Independently evaluates whether accumulated tests, runtime observations, builds, reports, and manual gates actually prove each requirement and support the claimed closure state.
-allowed-tools: Read, Glob, Grep, Bash, Agent
----
-
-# Evidence Review
-
-Resolve execution policy from .nccgs/execution.json before model routing. Missing
-execution.json means compatibility; model profile alone never removes obligations.
-
-- standalone: load the [shared standalone procedure](../../nccgs/protocols/standalone.md)
-  for this workflow, using its intake, mode, bounded domain steps and report rules.
-  Do not load the compatibility branches or inherit their external approval chain.
-- compatibility: read models.profile from .nccgs/project.yaml and load exactly one:
-  astra-claude uses [Astra/Claude procedure](references/astra.md); quality, balanced
-  or inherit uses [Legacy procedure](references/legacy.md). Existing task records
-  retain their original gates even after project execution policy changes.
-
-Unknown execution policies or model profiles are configuration errors. External
-review in standalone is off, advisory or required according to execution policy;
-configured routes do not prove actual provider model or effort.

package/.claude/skills/evidence-review/references/astra.md

@@ -1,17 +0,0 @@
-# Evidence Review — astra-claude
-
-Read [the pipeline protocol](../../../nccgs/protocols/astra-claude.md) and
-[generated routing](../../../nccgs/routing.generated.md). Use Astra's supplied plan,
-requirements, and exact context references. Never substitute a legacy procedure.
-
-Domain objective: Independently evaluates whether accumulated tests, runtime observations, builds, reports, and manual gates actually prove each requirement and support the claimed closure state.
-
-Work only inside the supplied plan and assigned write set. Activate an optional
-specialist with the agents command only when its domain is required. Keep one writer
-per path and use official Unity Skills for Editor/assets/runtime operations.
-
-This procedure is read-only: return evidence-backed findings and decisions to Astra
-or the implementer. Supplemental analysis does not replace the mandatory Fable gate.
-
-Use [task gate commands](../../../nccgs/protocols/task-gates.md) for evidence and
-state transitions. Report outcome, evidence, pending decisions, and next owner.

package/.claude/skills/evidence-review/references/legacy.md

@@ -1,7 +0,0 @@
-# Evidence Review
-
-Read `.nccgs/project.yaml`, `.nccgs/state.md`, and the active context packet when present. Preserve Product Owner authority and unrelated work.
-
-Read the [evidence protocol](../../../nccgs/protocols/evidence.md), requirements, evidence records, test outputs, runtime/build observations, baseline, and waivers. Map every criterion to PASS, FAIL, NOT PROVEN, PO GATE, or N/A. Detect stale source revisions, unexplained count/skip changes, evidence produced before the final diff, and claims based only on inspection. Return closure impact and exact evidence still required.
-
-Return outcome, evidence, affected records, blockers or decisions, residual risk, and the exact next workflow. Do not claim DONE unless this is the `closure` skill and every configured gate passes.

package/.claude/skills/hotfix/SKILL.md

@@ -1,22 +0,0 @@
----
-name: hotfix
-description: Runs a tightly scoped CONTROLLED workflow for urgent production or release-critical defects with containment, minimal change, accelerated evidence, rollback, and follow-up debt.
-allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Agent, AskUserQuestion
----
-
-# Hotfix
-
-Resolve execution policy from .nccgs/execution.json before model routing. Missing
-execution.json means compatibility; model profile alone never removes obligations.
-
-- standalone: load the [shared standalone procedure](../../nccgs/protocols/standalone.md)
-  for this workflow, using its intake, mode, bounded domain steps and report rules.
-  Do not load the compatibility branches or inherit their external approval chain.
-- compatibility: read models.profile from .nccgs/project.yaml and load exactly one:
-  astra-claude uses [Astra/Claude procedure](references/astra.md); quality, balanced
-  or inherit uses [Legacy procedure](references/legacy.md). Existing task records
-  retain their original gates even after project execution policy changes.
-
-Unknown execution policies or model profiles are configuration errors. External
-review in standalone is off, advisory or required according to execution policy;
-configured routes do not prove actual provider model or effort.

package/.claude/skills/hotfix/references/astra.md

@@ -1,30 +0,0 @@
-# Hotfix — astra-claude
-
-Read [the pipeline protocol](../../../nccgs/protocols/astra-claude.md) and
-[generated routing](../../../nccgs/routing.generated.md). Use Astra's supplied plan,
-requirements, and exact context references. Never substitute a legacy procedure.
-
-Domain objective: Runs a tightly scoped CONTROLLED workflow for urgent production or release-critical defects with containment, minimal change, accelerated evidence, rollback, and follow-up debt.
-
-Work only inside the supplied plan and assigned write set. Activate an optional
-specialist with the agents command only when its domain is required. Keep one writer
-per path and use official Unity Skills for Editor/assets/runtime operations.
-
-For code changes: task init with Astra's plan and --risk FAST|STANDARD|CONTROLLED
-(default STANDARD), bind the session, and use the recorded implementation route.
-Keep one accountable implementer; use the scout only for missing facts. Implement,
-run relevant checks, and run task check --id ID --target review before requesting
-independent Fable review. Keep only one Fable review in flight for the task. Fix actionable findings
-within scope and re-review only within the remaining task budget. Re-recording
-implementation does not reset that budget. Exhaustion without a usable PASS means
-stop with evidence for an explicit external decision, never automatic approval.
-After task check --target report passes, write and record the report for Astra.
-Stop at AWAITING_ASTRA_CHECK. Astra checking and explicit Product Owner acceptance
-happen outside the Claude implementation session. FAST uses concise plan/report
-artifacts and keeps the full acceptance chain.
-
-Publication and other external release actions still require explicit Product Owner
-authority; successful local verification grants no publication permission.
-
-Use [task gate commands](../../../nccgs/protocols/task-gates.md) for evidence and
-state transitions. Report outcome, evidence, pending decisions, and next owner.

package/.claude/skills/hotfix/references/legacy.md

@@ -1,7 +0,0 @@
-# Hotfix
-
-Read `.nccgs/project.yaml`, `.nccgs/state.md`, and the active context packet when present. Preserve Product Owner authority and unrelated work.
-
-Confirm affected version, severity, user/data impact, reproduction, containment, release branch, and rollback. Build the smallest safe fix with one accountable writer; preserve compatibility and avoid unrelated refactors. Run targeted regression plus the release-critical checks justified by blast radius. Record evidence, known gaps, approval, release steps, rollback trigger, and required follow-up. Publication still requires explicit authority.
-
-Return outcome, evidence, affected records, blockers or decisions, residual risk, and the exact next workflow. Do not claim DONE unless this is the `closure` skill and every configured gate passes.

package/.claude/skills/incident-recovery/SKILL.md

@@ -1,22 +0,0 @@
----
-name: incident-recovery
-description: Coordinates evidence-preserving response to data loss, corruption, broken builds, failed migrations, or production-impacting Unity incidents.
-allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Agent, AskUserQuestion
----
-
-# Incident Recovery
-
-Resolve execution policy from .nccgs/execution.json before model routing. Missing
-execution.json means compatibility; model profile alone never removes obligations.
-
-- standalone: load the [shared standalone procedure](../../nccgs/protocols/standalone.md)
-  for this workflow, using its intake, mode, bounded domain steps and report rules.
-  Do not load the compatibility branches or inherit their external approval chain.
-- compatibility: read models.profile from .nccgs/project.yaml and load exactly one:
-  astra-claude uses [Astra/Claude procedure](references/astra.md); quality, balanced
-  or inherit uses [Legacy procedure](references/legacy.md). Existing task records
-  retain their original gates even after project execution policy changes.
-
-Unknown execution policies or model profiles are configuration errors. External
-review in standalone is off, advisory or required according to execution policy;
-configured routes do not prove actual provider model or effort.

package/.claude/skills/incident-recovery/references/astra.md

@@ -1,27 +0,0 @@
-# Incident Recovery — astra-claude
-
-Read [the pipeline protocol](../../../nccgs/protocols/astra-claude.md) and
-[generated routing](../../../nccgs/routing.generated.md). Use Astra's supplied plan,
-requirements, and exact context references. Never substitute a legacy procedure.
-
-Domain objective: Coordinates evidence-preserving response to data loss, corruption, broken builds, failed migrations, or production-impacting Unity incidents.
-
-Work only inside the supplied plan and assigned write set. Activate an optional
-specialist with the agents command only when its domain is required. Keep one writer
-per path and use official Unity Skills for Editor/assets/runtime operations.
-
-For code changes: task init with Astra's plan and --risk FAST|STANDARD|CONTROLLED
-(default STANDARD), bind the session, and use the recorded implementation route.
-Keep one accountable implementer; use the scout only for missing facts. Implement,
-run relevant checks, and run task check --id ID --target review before requesting
-independent Fable review. Keep only one Fable review in flight for the task. Fix actionable findings
-within scope and re-review only within the remaining task budget. Re-recording
-implementation does not reset that budget. Exhaustion without a usable PASS means
-stop with evidence for an explicit external decision, never automatic approval.
-After task check --target report passes, write and record the report for Astra.
-Stop at AWAITING_ASTRA_CHECK. Astra checking and explicit Product Owner acceptance
-happen outside the Claude implementation session. FAST uses concise plan/report
-artifacts and keeps the full acceptance chain.
-
-Use [task gate commands](../../../nccgs/protocols/task-gates.md) for evidence and
-state transitions. Report outcome, evidence, pending decisions, and next owner.

package/.claude/skills/incident-recovery/references/legacy.md

@@ -1,7 +0,0 @@
-# Incident Recovery
-
-Read `.nccgs/project.yaml`, `.nccgs/state.md`, and the active context packet when present. Preserve Product Owner authority and unrelated work.
-
-Prioritize containment and evidence preservation. Record incident scope, affected versions/data, current state, timeline, hypotheses, and irreversible-action boundaries. Avoid destructive cleanup and speculative rewrites. Build a recovery graph with backups, reproducible diagnostics, validation, and rollback. Apply only authorized recovery changes; maintain an incident record and follow-up prevention actions. Data deletion or production actions require explicit authority.
-
-Return outcome, evidence, affected records, blockers or decisions, residual risk, and the exact next workflow. Do not claim DONE unless this is the `closure` skill and every configured gate passes.