context-management
Context Management loads and maintains project state across Claude Code sessions by retrieving documents from a .claude/ directory structure containing PRDs, epics, tasks, and agent definitions. Use this skill to enable persistent workflow continuity across multiple project phases, isolate context per parallel work stream, and recover session state without losing project information.
git clone --depth 1 https://github.com/a5c-ai/babysitter /tmp/context-management && cp -r /tmp/context-management/library/methodologies/ccpm/skills/context-management ~/.claude/skills/context-managementSKILL.md
# 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.
Review TypeScript code changes for consistency, type safety, and monorepo patterns across babysitter packages
Generate and validate documentation for @a5c-ai/babysitter-sdk CLI commands and exported APIs
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
Architect code review with DRY, YAGNI, abstraction, and test coverage principle enforcement