skills.rest
MariusWilsch
MariusWilschCOMMUNITY
Explore all skills by this author →
GitHub

deliverable-tracking

Generate GitHub Issues for client deliverables with What, Why, and Definition of Done.

Updated Aug 27, 2026
Search Tags:#workflow#github#issues#tracking#deliverables#project-management#rubber-duck
One-click install
npx skills add https://github.com/MariusWilsch/claude-code-conversation-store --skill deliverable-tracking
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deliverable-tracking
Source: https://github.com/MariusWilsch/claude-code-conversation-store/tree/main/plugins/claude-code-team-plugin/skills/deliverable-tracking
Command: npx skills add https://github.com/MariusWilsch/claude-code-conversation-store --skill deliverable-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates turning fragmented client conversations into traceable deliverable work items, reducing manual handoffs and miscommunication.

Core Features & Use Cases

  • Extract What/Why/Definition of Done from conversation context
  • Prompt for missing fields with AskUserQuestion to fill gaps
  • Create GitHub Issue with a title using the client name and a brief description, and link a DoD tracking file
  • Route to the appropriate repository based on client (e.g., DaveX2001/claude-code-improvements for CLAUDE-CODE-IMPROVEMENTS, otherwise DaveX2001/deliverable-tracking)

Quick Start

Create a GitHub Issue for the deliverable by extracting What, Why, and DoD from the conversation and prompting for any missing fields.

Frequently Asked Questions about deliverable-tracking

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

FAQPage Schema
How do I turn client conversations into GitHub Issues for deliverable tracking?▼

To turn client conversations into GitHub Issues, this skill extracts the What, Why, and Definition of Done from context, prompts for missing fields, and creates a structured issue with client labels for sprint planning.

What is the best way to track project deliverables using GitHub Issues?▼

Tracking project deliverables using GitHub Issues is best handled by enforcing a structured Definition of Done and Acceptance Criteria, which this skill automates by linking a DoD tracking file directly in the issue body.

Can I automatically create GitHub Issues from chat without manual data entry?▼

Yes, you can automatically create GitHub Issues from chat without manual data entry; the skill uses a discovery phase to collect required fields from conversation context and fills gaps by prompting you with targeted questions.

Does this deliverable tracking skill route issues to different GitHub repositories based on the client?▼

Yes, deliverable tracking routes issues to different GitHub repositories based on the client name, directing specific clients like CLAUDE-CODE-IMPROVEMENTS to dedicated repos while sending others to a default tracking repository.

How do I ensure Definition of Done and Acceptance Criteria are enforced in GitHub Issues?▼

To ensure Definition of Done and Acceptance Criteria are enforced in GitHub Issues, the skill enforces structured DoD and AC content during issue creation and attaches a tracking file to the issue body for verification.

Related Skills

Explore More Product & Management Skills→
lexmountlexmount
19

create-pr

Automate standardized GitHub pull request creation with the gh CLI.

Official
Intermediate
xloxn69xloxn69
7

agileflow-sprint-planner

Generate a balanced Markdown sprint plan from backlog stories and team capacity.

Community
Intermediate
mistakeknotmistakeknot
2

lane

Manage thematic work lanes for sequencing, starvation tracking, and progress visibility.

Community
Intermediate
braselogbraselog
3

summarize-meeting

Summarize meeting transcripts into action items, decisions, and key points.

Community
Basic