skill-phase-contextlisted

# Phase Context Loading Protocol This skill defines **skill loading tiers** to optimize token consumption while preserving automation capabilities. > [!IMPORTANT] > **Single Source of Truth for Skill Loading Strategy.** > Reference this skill to understand WHEN to load WHICH skills. ## TIER 0: System Foundation — ALWAYS LOADED > [!CAUTION] > **NEVER lazy-load TIER 0 skills. They enable core automation.** > These skills MUST be available in EVERY session at bootstrap. | Skill | Tokens | Why Always Load | |-------|--------|-----------------| | `core-principles` | ~519 | Anti-hallucination rules, Stub-First, Documentation First | | `skill-safe-commands` | ~927 | **Enables automation** — `mv`, `ls`, `git`, tests auto-run | | `artifact-management` | ~636 | Archiving protocol, file management, dual state tracking | | **TOTAL** | **~2,082** | **Non-negotiable system foundation** | ### TIER 0 Loading Rule - Load at session bootstrap (via `GEMINI.md` / `.cursorrules`) - These skills are loaded BEFORE any phase begins - Never remove or defer loading of TIER 0 skills --- ## TIER 1: Phase-Triggered — Load on Phase Entry These skills are phase-specific and loaded when entering the corresponding phase. | Phase | Skills to Load | Approx. Tokens | |-------|----------------|----------------| | **Analysis** | `requirements-analysis`, `skill-task-model`, `artifact-formalizer` (contract only), (`skill-archive-task` if new task) | ~3,100-4,000 | | **Architecture** | `architecture-design