Context Management
Project context loading, isolation, and persistent state management across CCPM sessions.
Best use case
Context Management is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Project context loading, isolation, and persistent state management across CCPM sessions.
Teams using Context Management should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/context-management/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Context Management Compares
| Feature / Agent | Context Management | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Project context loading, isolation, and persistent state management across CCPM sessions.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Context Management Project context loading, isolation, and persistent state management across CCPM sessions. ## Capabilities - Load project context from .claude/ directory structure - Maintain persistent context across sessions (PRD, epic, task states) - Isolate agent contexts per work stream - Context handoff between phases - Session state recovery ## Context Sources ``` .claude/ prds/ # PRD documents epics/ # Epic and task documents agents/ # Agent definitions context/ # Project-wide context commands/ # Command definitions rules/ # Reference rules ``` ## Context Flow 1. **Phase 1** (PRD): Loads project description, creates PRD context 2. **Phase 2** (Epic): Loads PRD, creates architecture context 3. **Phase 3** (Tasks): Loads PRD + Epic, creates task context 4. **Phase 4** (Sync): Loads all artifacts, syncs to GitHub 5. **Phase 5** (Exec): Loads stream-specific context per agent ## Isolation Each parallel agent receives only the context relevant to its stream, preventing context pollution and keeping agents focused.
Related Skills
translation-management
Integration with translation management systems and i18n workflows. Connect with Crowdin, Transifex, Weblate, manage translation memory, synchronize glossaries, and automate localization pipelines.
key-management-orchestrator
Cryptographic key lifecycle management orchestration including generation, rotation, and destruction across key management systems
ip-core-management
Vendor IP core configuration and integration expertise for FPGA designs
donor-relationship-management
Cultivate and steward donor relationships including prospect research, personalized engagement strategies, gift acknowledgment, and impact reporting
change-management
Skill for engineering change request and order processing through PLM systems
stormwater-management
Skill for integrated stormwater management and green infrastructure design with SWMM modeling, hydrologic analysis, BMP sizing, and MS4 permit compliance.
thermal-management
Vehicle and powertrain thermal management system design
influencer-kol-management
Industry influencer and key opinion leader relationship management
crisis-management-platform
Crisis response platform integration and real-time monitoring
social-media-management
Cross-platform social media operations and analytics
marketing-project-management
Marketing workflow and project management integration
content-management
CMS operations and content optimization tools