context-engineering-advisor

Diagnose context stuffing and guide teams toward bounded memory architectures.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/roberttmadsen13-del/TOURney --skill context-engineering-advisor-roberttmadsen13-del
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-engineering-advisor
Source: https://github.com/roberttmadsen13-del/TOURney/tree/main/SKILLS/Product-Manager-Skills-main/skills/context-engineering-advisor
Command: npx skills add https://github.com/roberttmadsen13-del/TOURney --skill context-engineering-advisor-roberttmadsen13-del

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose context stuffing vs context engineering. Use when an AI workflow feels bloated, brittle, or hard to steer reliably.

Core Features & Use Cases

  • Identify and differentiate context stuffing from context engineering to ground AI in a purposeful information architecture.
  • Define context boundaries, ownership, and retrieval strategies to reduce noise and token waste.
  • Guide teams through the Research → Plan → Reset → Implement cycle to prevent context rot and improve reliability.

Quick Start

Run the diagnostic to identify context stuffing and implement boundary-driven memory and retrieval practices.

Frequently Asked Questions about context-engineering-advisor

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

FAQPage Schema
What is context stuffing in AI workflows and how does it differ from context engineering?

Context stuffing bloats AI workflows with unbounded information, causing brittleness and unreliable steering. Context engineering replaces this by defining purposeful information architecture with strict boundaries, ownership, and retrieval strategies to reduce noise and token waste.

How do I diagnose and fix bloated AI agent memory and high token waste?

Run a diagnostic to identify context stuffing and implement bounded, task-focused memory architectures. Apply the Context Manifest template to define boundary ownership and retrieval strategies, reducing token waste and improving AI agent reliability.

What's the best way to structure retrieval-augmented generation for product management tasks?

Use a structured Research, Plan, Reset, Implement cycle to prevent context rot. Define strict context boundaries, enforce ownership, and apply targeted retrieval strategies to ground AI agents co-creating decisions across information boundaries.

Can I use this context engineering approach for AI agents that plan and execute across multiple information boundaries?

Yes, this approach specifically targets product management contexts where AI agents co-create decisions, plan, and execute across information boundaries. It enforces bounded memory architectures and structured cycles to maintain reliability.

Why does my AI workflow feel brittle and hard to steer reliably during planning and execution?

Your AI workflow likely suffers from context stuffing, where unbounded information causes context rot. Implementing boundary-driven memory architectures and a Research, Plan, Reset, Implement cycle restores reliable steering and reduces noise.

When should I use a Context Manifest template for AI product management?

Use a Context Manifest template when AI workflows become bloated and token waste increases. It helps define context boundaries, establish ownership, and map retrieval strategies to prevent context rot and improve agent reliability.