context-curation-base

Automate project context cleanup by folding persistent data into addendums and archiving outdated material.

5|2|Updated Nov 25, 2025

Search Tags:#workflow #documentation #context #retrospective #archiving #reference-docs

Ready to run

npx skills add https://github.com/ZachBeta/claude-as-coach --skill context-curation-base

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: context-curation-base
Source: https://github.com/ZachBeta/claude-as-coach/tree/main/skills/context-curation-base
Command: npx skills add https://github.com/ZachBeta/claude-as-coach --skill context-curation-base

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined process to manage and prune project context after retrospectives and planning, preventing context bloat and ensuring references stay current.

Core Features & Use Cases

Structured curation: fold-and-archive workflow that preserves essential data while removing noise.
Reference hygiene: maintains addenda and reference docs for quick state recall.
Use Case: after a weekly retro, run the curation to extract persistent data into addendums and fold them into main docs.

Quick Start

After completing a retro + planning cycle, invoke context curation to review dailies, generate addendums, and archive outdated material.

Frequently Asked Questions about context-curation-base

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent context bloat after project retrospectives?▼

To prevent context bloat after retrospectives, apply a fold-and-archive workflow that extracts persistent data into addendums, folds them into main docs, and archives outdated material. This keeps project references tidy and actionable.

What is the fold-before-archive workflow for documentation?▼

The fold-before-archive workflow extracts persistent data from retrospectives into addendums, folds those addendums into main project docs, and then archives outdated material using layer-based retention rules to maintain reference hygiene.

How do I extract persistent data from retrospectives into reference docs?▼

You extract persistent data from retrospectives by generating addendums after planning cycles, updating your reference docs with this extracted state, and folding the addendums into the main documentation for quick recall.

When should I run context curation for project planning cycles?▼

You should run context curation after completing weekly or monthly retrospectives and planning cycles. This timing ensures outdated material is archived and reference docs are updated before the next iteration begins.

What are layer-based retention rules for archiving project context?▼

Layer-based retention rules govern how outdated material is archived during context curation. They ensure essential data is preserved through addendum generation and reference doc updates before older project context is fully archived.

Can I use automated context cleanup for daily project logs?▼

Automated context cleanup targets dailies after a retro and planning cycle. It reviews daily logs to generate addendums and fold persistent information into main docs, rather than processing logs in isolation.