context-engineering-advisor

From README

Purpose Guide product managers through diagnosing whether they're doing context stuffing (jamming volume without intent) or context engineering (shaping structure for attention). Use this to identify context boundaries, fix "Context Hoarding Disorder," and implement tactical practices like bounded domains, episodic retrieval, and the Research→Plan→Reset→Implement cycle. Key Distinction: Context stuffing assumes volume = quality ("paste the entire PRD"). Context engineering treats AI attention as a scarce resource and allocates it deliberately. This is not about prompt writing—it's about designing the information architecture that grounds AI in reality without overwhelming it with noise. Input Works best with: A description of the AI workflow, agent, or prompt that feels bloated, brittle, or hard to steer. Also useful: What you've already stuffed into context (docs, transcripts, schemas) and where outputs go wrong.