kata-issue-analysis

Name: kata-issue-analysis
Availability: InStock
Author: Guardia

Convert GitHub issues into structured briefs with optional Notion context.

Updated Sep 3, 2025

Search Tags:#github issues #brief generation #mcp integrations #issue-driven development #notion enrichment #workflow checkpoint #requirements triage

Ready to run

npx skills add https://github.com/guardiatechnology/design-system --skill kata-issue-analysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kata-issue-analysis
Source: https://github.com/guardiatechnology/design-system/tree/main/.claude/skills/kata-issue-analysis
Command: npx skills add https://github.com/guardiatechnology/design-system --skill kata-issue-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts a GitHub issue (including relevant discussion) into a structured, decision-ready brief enriched with related Notion context, so the next phase can move forward with clarity instead of guesswork.

Core Features & Use Cases

Reads issue metadata and comments to summarize what’s actually being requested, including labels, assignees, author, and the creation state.
Optionally enriches from Notion by extracting key terms from the issue and searching Notion for relevant pages, prioritizing under a configured root page when available.
Produces durable outputs by persisting the consolidated brief and creating a workflow checkpoint for the Issue-Driven flow.

Quick Start

Run the kata-issue-analysis skill by providing the GitHub owner/repo and issue number, and it will generate the brief at .ahrena/issues/{n}/01-brief.md (skipping Notion enrichment if the Notion MCP server is unavailable).

Frequently Asked Questions about kata-issue-analysis

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

FAQPage Schema

How do I convert a GitHub issue into a structured brief for requirements triage?▼

To convert a GitHub issue into a structured brief, provide the repository and issue number to generate a consolidated analysis at .ahrena/issues/{n}/01-brief.md, summarizing metadata and comments for requirements triage.

What is issue-driven development workflow phase 1?▼

Issue-driven development workflow phase 1 is the consolidation stage where issue metadata, comments, and domain context are gathered into a decision-ready brief, enabling design or requirements follow-up instead of guesswork.

Can I enrich GitHub issue context with related Notion pages?▼

You can enrich GitHub issue context with related Notion pages by extracting key terms from the issue and searching Notion, prioritizing results under a configured root page if the Notion MCP server is available.

Does issue brief generation work without the Notion MCP integration?▼

Issue brief generation works without the Notion MCP integration by skipping the Notion enrichment step entirely, relying solely on read-only GitHub retrieval to produce the structured brief and workflow checkpoint.

How do I persist a workflow checkpoint for issue-driven development?▼

To persist a workflow checkpoint for issue-driven development, the skill saves the consolidated brief and checkpoint data to fixed .ahrena paths, ensuring the next workflow phase can move forward with durable outputs.

What GitHub metadata is included when generating an issue analysis brief?▼

When generating an issue analysis brief, the tool reads GitHub issue metadata and comments to summarize the request, specifically including labels, assignees, author, and the creation state for decision-ready context.