load-context

To consolidate git history and requirements into one context summary, aggregate work state, brainstorms, proposals, product knowledge, and git history by running a context aggregation command with your ticket slug or query. This produces a unified, phase-aware context report with handoff options.

Aggregating project context for a ticket involves collecting all available work state, brainstorms, proposals, requirements KB, and product knowledge into a single summary. This approach uses fuzzy local search and prior-art loading to ensure you have the full historical context before continuing work.

Yes, you can create new context when nothing exists. The context aggregation process supports optional creation of new context if searches return no results, ensuring you always have a structured starting point for your topic or ticket.

Yes, configuring storage locations is required before aggregating work state and proposals. The context aggregation process requires setup of storage locations and tool support to successfully collect and present your unified context report.

Fuzzy search for loading prior-art context matches approximate queries against stored brainstorms, proposals, and requirements. This allows you to retrieve relevant historical project data using a slug or search term, even without an exact match, to inform your current work phase.

Limitations of aggregating multi-source context include dependency on configured storage locations and tool support. If your storage locations are not properly set up, the context aggregation cannot collect the required work state, brainstorms, and git history to generate the unified summary.