mcpField
C
context-management

context-management

github.com/dralgorhythmDevelopment12972 installsUpdated 14w ago
Repository

About context-management

A context-management skill for development teams to capture project, technical, and historical knowledge, then use it for onboarding and handoffs.

Key features

  1. 01Separates project, technical, and historical context
  2. 02Records rationale in decision logs
  3. 03Organizes README, ADRs, and other project docs
  4. 04Outlines onboarding and handoff steps

Use cases

  1. 01Document architecture decisions and their rationale
  2. 02Orient new team members
  3. 03Hand off work with risks and open questions

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/dralgorhythm/claude-agentic-framework --skill context-management

After installing, type/context-managementin Claude Code to confirm it loaded.

Details

From the project README

Context Management

Why Context Matters

  • Reduces ramp-up time
  • Prevents repeated mistakes
  • Enables informed decisions
  • Facilitates collaboration

Context Types

Project Context
  • What the project does
  • Why it exists
  • Who uses it
  • Key constraints
Technical Context
  • Architecture decisions (ADRs)
  • Technology choices
  • Coding conventions
  • Known issues
Historical Context
  • Why decisions were made
  • What was tried before
  • Lessons learned

Context Capture

Decision Log
## Decision: [Title]
**Date**: [Date]
**Context**: [Why this came up]
**Decision**: [What was decided]
**Rationale**: [Why this choice]
**Consequences**: [What changed]
Knowledge Base
  • README for project overview
  • ADRs for architecture
  • CONTRIBUTING for development
  • CHANGELOG for history
Code Comments
// CONTEXT: This retry logic exists because the external API
// has intermittent failures. See incident-123 for details.
// We chose exponential backoff after testing showed it
// reduces error rate by 80%.

Context Sharing

New Team Member
  1. Start with README
  2. Review key ADRs
  3. Pair on first task
  4. Introduce to stakeholders
Handoff
  1. Document current state
  2. List open questions
  3. Identify risks
  4. Warm handoff meeting

Best Practices

  1. Write it down: Don't rely on memory
  2. Keep it current: Update as things change
  3. Make it findable: Organize logically
  4. Be specific: Include the "why"
  5. Review regularly: Remove stale info

Comments

Markdown supported