unified-context-stack

Retrieve tiered context across software development lifecycle phases.

6|Updated Feb 13, 2026

Search Tags:#context retrieval #software development #SDLC #phase-aware #contextual information

Ready to run

npx skills add https://github.com/damianpapadopoulos/auto-claude-skills --skill unified-context-stack

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: unified-context-stack
Source: https://github.com/damianpapadopoulos/auto-claude-skills/tree/main/skills/unified-context-stack
Command: npx skills add https://github.com/damianpapadopoulos/auto-claude-skills --skill unified-context-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

The unified-context-stack skill addresses the challenges of maintaining context during software development, such as the difficulty in retrieving and utilizing relevant information across different stages of the lifecycle.

Core Features & Use Cases

Context Retrieval: Offers tiered retrieval of context across external truth (documents), internal truth (dependencies), historical truth (memory), and intent truth (feature specs).
Phase-Aware Orchestration: Dynamically provides context tailored to each phase of the software development lifecycle, from design to review and ship.
Use Case: During the implementation phase, it assists by retrieving the most relevant architectural decisions, dependencies, and specifications, reducing the need for context switching.

Quick Start

Utilize the unified-context-stack skill in the planning phase by referencing the available capabilities in the 'Context Stack:' and accessing relevant phase-specific documents.

Frequently Asked Questions about unified-context-stack

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

FAQPage Schema

How do I retrieve relevant context across different phases of the software development lifecycle?▼

Context retrieval for the software development lifecycle is achieved by using tiered retrieval to dynamically provide information tailored to each phase. This phase-aware orchestration reduces context switching by fetching relevant architectural decisions and dependencies dynamically.

What is tiered context retrieval and how does it work for software development?▼

Tiered context retrieval works by sourcing information across four distinct layers: external truth, internal truth, historical truth, and intent truth. This mechanism ensures developers retrieve comprehensive and relevant contextual information dynamically throughout the software development lifecycle.

How do I stop losing architectural decisions and dependencies when switching between SDLC phases?▼

To stop losing architectural decisions during context switching, leverage phase-aware orchestration during implementation. It dynamically retrieves relevant dependencies, specifications, and historical truth, ensuring informed decision-making without manual context reconstruction.

Can I use phase-aware context orchestration during the planning and design phases?▼

Yes, you can use phase-aware orchestration during planning and design by referencing available capabilities in the Context Stack. This dynamically provides tailored context, allowing you to access relevant phase-specific documents and feature specs.

What's the best way to maintain feature specifications and dependencies context during implementation?▼

The best way to maintain feature specifications context is utilizing a unified context stack. It provides tiered retrieval across external documents, internal dependencies, historical memory, and intent specs, dynamically orchestrating context for streamlined implementation.

Why does my development process lose intent truth and historical memory between stages?▼

Your development process loses historical truth and intent truth between stages due to the lack of phase-aware orchestration. Implementing tiered context retrieval dynamically preserves and surfaces relevant contextual information, reducing the friction of context switching.