implementation-guidance-generator

Convert Linear issue details into structured implementation guidance documents.

3|1|Updated Jun 20, 2016

Search Tags:#markdown #implementation #guidance #linear #issue-tracking #code-references

Ready to run

npx skills add https://github.com/paulchiu/dotfiles --skill implementation-guidance-generator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implementation-guidance-generator
Source: https://github.com/paulchiu/dotfiles/tree/main/.config/opencode/skills/implementation-guidance-generator
Command: npx skills add https://github.com/paulchiu/dotfiles --skill implementation-guidance-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Generates structured implementation guidance documents for technical issues, bug fixes, and feature development, enabling actionable plans with references to files and code locations, following Obsidian markdown formatting standards.

Core Features & Use Cases

Generates implementation guidance documents that adhere to a standardized formatting style.
Transforms issue descriptions into actionable plans with file references, code locations, and step-by-step approaches.
Applies Obsidian markdown formatting and supports GitHub links for code references.

Quick Start

Provide the Linear issue URL, fetch full issue details via Linear MCP, identify affected files, generate structured guidance, and apply the formatting standards.

Frequently Asked Questions about implementation-guidance-generator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I convert Linear issues into implementation guidance documents?▼

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.

What is the best way to generate actionable plans from issue tracking tickets?▼

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.

Does implementation guidance generation work with Obsidian markdown formatting?▼

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.

Can I use Linear MCP to fetch issue details for codebase 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.

What should be included in an implementation guidance document for feature work?▼

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.

How to apply Obsidian formatting to bug fix implementation plans?▼

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.