context-engineering-advisor

Diagnose context stuffing and design memory boundaries for AI-driven PM workflows.

6.4k|767|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/deanpeters/Product-Manager-Skills --skill context-engineering-advisor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-engineering-advisor
Source: https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/context-engineering-advisor
Command: npx skills add https://github.com/deanpeters/Product-Manager-Skills --skill context-engineering-advisor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams distinguish between context stuffing and proper context engineering, then designs and implements disciplined memory, boundary rules, and cycles to keep AI-driven PM work focused and reliable.

Core Features & Use Cases

  • Diagnostic framework: identifies symptoms of context hoarding and provides actionable steps (boundary ownership, context manifest, and memory architecture).
  • Memory & boundary design: prescribes a two-layer memory model (short-term conversational and long-term persistent memory) with retrieval strategies.
  • Implementation cycle: guides Research → Plan → Reset → Implement to prevent context rot, including templates and artifacts.
  • Use Case: for discovery planning, backlog prioritization, and multi-agent toolchains where context must be bounded and relevant.

Quick Start

Provide a high-density plan for your next AI-assisted PM task by running a diagnostic prompt that asks me to assess context usage and propose a Context Manifest; then implement the cycle.

Frequently Asked Questions about context-engineering-advisor

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

FAQPage Schema
What is the difference between context stuffing and context engineering in AI workflows?

Context engineering designs bounded memory and retrieval rules to keep AI focused, whereas context stuffing hoards unstructured data, causing context rot. This Skill diagnoses these symptoms and prescribes a structured Context Manifest to optimize AI-driven product management work.

How do I fix context rot in multi-agent RAG systems?

To fix context rot in multi-agent RAG systems, implement a reset-then-implement cycle using a two-layer memory architecture. This Skill guides you through boundary ownership and a Context Manifest to ensure persistent memory remains reliable.

How do I structure memory architecture for AI-driven product management tasks?

Structure memory architecture by defining a two-layer model separating short-term conversational state from long-term persistent memory. This Skill provides diagnostic frameworks to establish boundary ownership and retrieval strategies for product planning workflows.

Can I use this context engineering framework for backlog prioritization and discovery planning?

Yes, you can use this context engineering framework for backlog prioritization and discovery planning. It guides AI-driven product management workflows by applying a Research, Plan, Reset, Implement cycle to maintain bounded, relevant context.

When should I implement a reset cycle for AI memory boundaries?

Implement a reset cycle when teams experience context rot or AI outputs lose relevance during complex tasks. This Skill uses a structured reset-then-implement approach to clear short-term conversational memory and re-apply boundaries before continuing.