# ckb-project-summary — edge cases Reference material for the `ckb-project-summary` skill. Read when a run hits an unusual situation the main steps don't cover. - **Empty or near-empty project entity page** - write a short, honest Overview and State, and let Actions/Risks/Assumptions be genuinely short rather than inventing content to fill the template. - **Conflicting information between two source pages** - prefer the page with the more recent `last_updated`; if they're the same date, note the conflict briefly in Project State rather than silently picking one. - **`PROJECT-OVERVIEW.md` already exists** - overwrite it; this file is always meant to reflect the current wiki, not accumulate history. If the user wants history, that's what `wiki/log.md` and `workload/` are for. - **Re-running with no wiki changes since the last run** - should produce essentially the same content each time; don't introduce random variation in section content or ordering between runs. --- *Licensed under the Apache License, Version 2.0 — see [LICENSE](../../../LICENSE) at the repository root, or .*