flow-create-issue

To turn brainstormed ideas into structured GitHub issues, capture the conversation context and file a pre-planned issue. The issue embeds an Implementation Plan with Context, Exploration, Risks, Approach, Dependency Graph, and Tasks for direct Plan-phase extraction.

Automating task decomposition involves filing a GitHub issue containing a structured Implementation Plan. This plan allows the workflow's Plan phase to extract concrete tasks and code changes directly from the brainstorming context without re-derivation.

Yes, you need prior brainstorming context in the conversation to create a pre-planned GitHub issue. Context gating ensures brainstorming context exists before filing, preventing premature issues and ensuring the Implementation Plan is populated.

Context gating works by verifying that brainstorming context exists in the conversation before allowing issue creation. This mechanism prevents premature issues and requires a session-scoped identifier for file and path management in flow-style projects.

An Implementation Plan section for a GitHub issue should include Context, Exploration, Risks, Approach, Dependency Graph, and Tasks. This structure allows the Plan phase to parse the issue and generate concrete tasks and code changes automatically.

Workflow issue creation fails without a session-scoped identifier because it is required for file and path management. This identifier, along with prior brainstorming context, ensures the pre-planned issue is filed correctly within the flow-style project.