gormes-context-sourcing

To find exact upstream references for unfamiliar Go packages, identify and fetch the specific code snippet or doc excerpt defining expected behavior. This context sourcing reduces uncertainty by ensuring planning decisions are based on trusted, narrowly scoped sources.

Sourcing context for a Go planning task involves pinpointing exact file paths, function names, or API signatures from external frameworks. It fetches canonical documentation to summarize relevance and impact, guiding safe implementation of the planned work.

Yes, you can fetch specific API signatures and code snippets to inform Go feature planning. By pinpointing exact file paths and function names from reference projects, you evaluate how the evidence informs the plan while keeping the scope narrow.

Evaluate the relevance of external documentation for a Go integration by summarizing its impact on the planned work. Fetch the canonical docs that define constraints and expected behavior, ensuring your implementation decisions are guided by trusted sources.

You need to source external reference context for a Go project before starting a feature using unfamiliar packages, providers, or integration points. Fetching the exact upstream reference ensures decisions are based on trusted sources and reduces implementation uncertainty.

Yes, context sourcing keeps the fetched reference scope narrowly limited. It requires pinpointing specific file paths, function names, or API signatures and evaluating how that narrowly scoped evidence informs the plan.