lythoskill-project-scribelisted

# Project Scribe > Write what `ls` + `cat` + `git log` cannot recover. Skip everything else. ## Value Boundary **Scribe = session context dump for things WITHOUT structured carriers.** ``` 对话中产生了什么? ├── 有 task/adr/epic 载体 → 写到对应 carrier,不写 scribe └── 无载体 → 自评: 下一个 agent 需要知道吗? ├── 需要 → scribe └── 不需要 → 不写 ``` | File exploration recovers (~70%) | Scribe must dump (~30%) | |----------------------------------|------------------------| | Project structure, tech stack | Pitfalls from this session | | skill-deck.toml content | True working-tree state (prevents hallucination) | | cortex/ tasks and epics | Why we chose A not B (not ADR-worthy but still important) | | git log history | Specific next steps (not "test it") | | README, docs | Temp artifacts: location + purpose | | git diff (code changes) | Uncommitted modifications and their intent | | | Meta-observations that emerge mid-conversation | If the next agent can find it via `ls`, `cat`, or `git log` — don't repeat it. ## Pre-Handoff Checklist (mandatory before writing) ```bash # 1. Git state git status git log --oneline -5 # 2. Cortex state (if cortex is active) bunx @lythos/project-cortex@0.15.5 list # 3. Session recall — ask yourself: # - What did I modify but not commit? # - What pitfalls did I hit? # - What important decisions were made verbally? # - What temp files did I create and where? # - What would the next agent most likely misunderstand? ``` ## Core Operation: Write Daily Fil