implementation-guidance-generator

To convert Linear issues into implementation guidance, you provide the Linear issue URL and fetch details via Linear MCP. The tool then generates a structured guidance document with file references, code locations, and Obsidian markdown formatting.

Generating actionable plans from issue tracking tickets involves transforming issue descriptions into structured documents with primary approaches, precise code locations, and example snippets. This process ensures technical bugs or features have clear, step-by-step implementation paths.

Yes, implementation guidance generation applies Obsidian markdown formatting standards. The output documents include structured sections for primary approaches, multiple alternatives, context constraints, and GitHub links for code references.

Yes, you can use Linear MCP to fetch full issue details. Once fetched, the system identifies affected files and generates structured guidance with precise code locations and example snippets across your codebases.

An implementation guidance document for feature work should include a primary approach, precise code locations, example snippets, multiple approaches if needed, and relevant context or constraints. It transforms technical issues into actionable plans with file references.

To apply Obsidian formatting to bug fix implementation plans, the system converts issue details into structured markdown documents. This includes adding GitHub links for code references, file locations, and step-by-step approaches following standardized formatting styles.