general-context-loader

To infer requirements from a GitHub issue without a specification, analyze the issue body and related code to extract essential context. This process identifies missing information and generates AskUserQuestion prompts to resolve ambiguities, producing an actionable spec-context.

The best way to collect missing context from user instructions is to scan related code and discussions alongside the text. This structured workflow assembles a coherent context and generates AskUserQuestion prompts to resolve ambiguities when directions are incomplete.

You generate clarification prompts for ambiguous project requirements by reading issue content and searching related code. Identifying gaps in the available context allows you to create targeted AskUserQuestion prompts that ask the user to resolve specific ambiguities.

Yes, you can extract a clear specification from incomplete directions by scanning related code and discussions. The workflow reads issue text, infers essential requirements, and outputs an actionable spec-context even when a formal spec is absent.

You need to infer spec context from GitHub issues when a formal specification document is absent but development must proceed. It is applicable when you have issue bodies, user instructions, and related code that need to be assembled into coherent requirements.