skills.rest
BreakerOfStems
BreakerOfStemsCOMMUNITY
Explore all skills by this author →
GitHub

obsidian-issue-from-doc

Convert Obsidian Markdown documents into structured GitHub issues.

Updated Aug 27, 2026
Search Tags:#automation#project management#documentation#github#obsidian#issues
One-click install
npx skills add https://github.com/BreakerOfStems/claude-skills --skill obsidian-issue-from-doc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: obsidian-issue-from-doc
Source: https://github.com/BreakerOfStems/claude-skills/tree/main/skills/obsidian-issue-from-doc
Command: npx skills add https://github.com/BreakerOfStems/claude-skills --skill obsidian-issue-from-doc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill bridges the gap between documentation and actionable work by converting detailed Obsidian documents into well-structured GitHub issues, ensuring clarity and traceability.

Core Features & Use Cases

  • Automated Issue Generation: Transforms specifications, design docs, or bug analyses into GitHub issues with pre-defined templates.
  • Structured Data Extraction: Identifies and extracts key components like title, problem statement, acceptance criteria, and technical context from documents.
  • Use Case: You've just finished a detailed feature specification in Obsidian. Use this Skill to automatically create a GitHub issue with all necessary details, ready for your development team to pick up.

Quick Start

Convert the Obsidian document located at 'specs/user-logout.md' into a GitHub issue.

Frequently Asked Questions about obsidian-issue-from-doc

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

FAQPage Schema
How do I convert Obsidian documents into GitHub issues?▼

To convert Obsidian documents into GitHub issues, this Skill parses Markdown content to extract relevant fields like the title, problem statement, and technical context, structuring them automatically into actionable tasks for your repository.

How does automated issue generation from Markdown specifications work?▼

Automated issue generation works by identifying and extracting key components from Markdown specifications, such as acceptance criteria and problem statements, then mapping them directly to pre-defined GitHub issue templates.

Can I use this to create GitHub issues from design docs and bug analyses?▼

Yes, you can create GitHub issues from design docs and bug analyses. The Skill transforms these Obsidian documents into structured issues with clear technical context and acceptance criteria.

What is the best way to turn project management documentation into actionable tasks?▼

The best way to turn project management documentation into actionable tasks is using a parser that extracts problem statements and acceptance criteria directly from Markdown files to generate structured GitHub issues.

Do I need to format my Obsidian notes in a specific way to extract acceptance criteria?▼

You need standard Markdown formatting in your Obsidian notes for the parser to extract acceptance criteria and technical context accurately. The Skill relies on identifying these structured fields within the document.

Related Skills

Explore More Software Engineering Skills→
tech-with-sethtech-with-seth
4

prd

Generate a structured markdown PRD from a feature prompt.

Official
Basic
Steve-Smith-CODESteve-Smith-CODE

speckit-taskstoissues

Convert local task lists into GitHub issues with duplicate detection.

Community
Advanced
ToqsickToqsick

github-grayhack-workflow

Automate GitHub issue creation, branch management, pull requests, and documentation updates.

Community
Advanced
nkabbarankabbara

to-tickets

Convert spoken plans or written specs into structured tickets with blocking dependencies.

Community
Intermediate