---
id: on-load
app: wkappbot-workflow
description: "T1 core tier. Session-start decision rules: when to run mandatory loads, gg trigger, bare-keyword routing. Execution detail -> wkappbot skill read on-load-howto. History -> wkappbot skill read on-load-ref."
tags: [skill-tree, 스킬트리, 세션시작]
---

> **Refresh**: `wkappbot skill read on-load --if-newer` — v1.111 (2026-05-08)

# On Load (T1 core)

## Steps

1. WHEN TO RUN. (A) session start or post-compaction -> load mandatory skills (see on-load-howto step 1) + run handoff (on-load-howto step 3) + run suggest backlog (on-load-howto step 4). (B) user sends exactly gg or ggg -> run GG TRIGGER (T1 step 2). (C) mid-task or casual greeting -> SKIP full pipeline.
2. GG TRIGGER. User message exactly gg or ggg -> locate the gg Main Workflow section in project root markdown rules file and execute every step sequentially end-to-end NO confirmation, finish with repo-health-doctor. If section missing: ask user for recurring tasks, add the gg Main Workflow section, then run it same session. Quota/limit error: mark handoff_pending, do NOT retry same CLI.
3. BARE KOREAN KEYWORD RULE. If user drops an isolated Korean keyword or short phrase, run wkappbot skill search term FIRST. Never guess intent before the skill search resolves a matching skill.
4. NAVIGATION. Execution details (commands, mandatory loads, agent rules, file-edit discipline, skill-edit discipline, TODO sync) -> wkappbot skill read on-load-howto. History or incident notes or dated bug accumulation -> wkappbot skill read on-load-ref. Both are part of this cluster.
5. AGENT DISPATCH PRE-FLIGHT (before every delegation): wkappbot skill read agent-dispatch-preflight. Sequence: (0) Read CLAUDE.md first (Edit fails without Read). (1) Edit CLAUDE.md to add Pending entry. (2) Agent() MUST have run_in_background:true. (3) Prompt needs 3 skill reads. This session burned 4 attempts and ~4x tokens before getting it right -- read this skill every session to prevent recurrence.
6. MEMORY ORGAN. For predecessor questions and session-memory lookup, use wkhippo recall/foresee/export/status; wkrecall is archived and must not be presented as active.
