manage-context

Audit and reconcile .project/context files against current project evidence.

7|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/MajesteitBart/delano --skill manage-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-context
Source: https://github.com/MajesteitBart/delano/tree/main/.agents/skills/manage-context
Command: npx skills add https://github.com/MajesteitBart/delano --skill manage-context

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill repairs stale or contradictory project context so the .project/context/ files stay trustworthy for handoffs, restarts, and ongoing execution.

Core Features & Use Cases

  • Context auditing: Check context files against specs, plans, workstreams, decisions, and recent evidence.
  • Drift repair: Remove placeholder language, normalize terminology, and update progress claims to match implementation reality.
  • Handoff readiness: Surface contradictions, evidence gaps, and unresolved uncertainty instead of hiding them.
  • Use case: A project has changed scope or architecture and the context pack still reads like a template, so this Skill refreshes the documentation to match the current state.

Quick Start

Ask the agent to audit .project/context/ against the current project sources and refresh only the sections supported by evidence.

Frequently Asked Questions about manage-context

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

FAQPage Schema
How do I fix stale project documentation drift after a scope or architecture change?

Repair stale project documentation drift by auditing `.project/context/` files against current delivery evidence, normalizing terminology, removing placeholder language, and updating progress claims to match implementation reality.

What is the best way to prepare project context files for a team handoff?

Prepare project context for handoffs by reconciling specs, plans, workstreams, and decisions against recent evidence, surfacing contradictions and unresolved uncertainties instead of hiding missing facts.

How does evidence-based context auditing work for project restarts?

Evidence-based context auditing for project restarts checks `.project/context/` files against current sources, validating terminology, scope, constraints, non-goals, and open uncertainties without inventing missing facts.

Can I update progress claims in `.project/context/` files without inventing missing facts?

Update progress claims by matching them to current implementation reality through evidence-based reconciliation, ensuring terminology, scope, constraints, and non-goals reflect actual delivery status without fabricating unsupported information.

When should I run a context audit on my delivery workflow?

Run a context audit during handoffs, restarts, milestone reviews, and post-change documentation updates when `.project/context/` files risk contradicting current delivery reality across specs, plans, workstreams, and decisions.

Why does my project context still read like a template after the architecture changed?

Project context reads like a template when documentation drift occurs after scope or architecture changes, requiring an evidence-based refresh to replace placeholder language with current delivery reality.