conversation-capture

To turn a conversation transcript into a GitHub issue, the Skill analyzes the text to extract decisions, analysis, and action items, then drafts a structured issue body with a link to the source for submission.

Capturing action items and decisions from a discussion involves analyzing the conversation to extract conclusions and tasks, categorizing the type for labeling, and generating a trackable issue with references for traceability.

Yes, you can auto-categorize a GitHub issue because the Skill classifies the conversation type during analysis and applies corresponding labels to the drafted issue before submission.

Creating a decision log with references involves extracting conclusions from the transcript and generating a structured GitHub issue that includes a direct header link to the source conversation and relevant references.

Yes, issue drafting from conversations works without external dependencies, as the Skill independently analyzes the transcript, drafts the issue body with context and constraints, and requires no additional components.

Before submitting a drafted GitHub issue from a conversation, you should review the extracted scope, constraints, success criteria, and action items to ensure the structured draft accurately reflects the source discussion.