Create GitHub Issues for client deliverables in DaveX2001/deliverable-tracking repo (discovery: requirements-clarity). Evaluate at requirements-clarity when user mentions tracking, deliverables, commitments, or "create deliverable". Extracts What/Why/Done from conversation context, prompts for missing info via AskUserQuestion, applies dynamic client labels.
Inherits all available tools
Additional assets for this skill
This skill inherits all available tools. When active, it can use any tool Claude has access to.
Create structured GitHub Issues for client deliverables after clarity phases establish shared understanding.
Review the conversation above to extract:
Use AskUserQuestion to gather any fields not clearly extractable from context:
Required fields:
- Client name (for label and title prefix)
- Brief description (for title)
- What (if not clear from conversation)
- Why (if not clear from conversation)
- Definition of Done (if not clear from conversation)
Optional:
- Notes (references, blockers, context)
Format questions with 2-4 concrete options when possible. For free-form input, let user select "Other".
Title format: {Client}: {Brief description}
Body format:
## What?
[Deliverable description]
## Why?
[Motivation/importance]
## Definition of Done
[Success criteria - how we know it's complete]
## Notes
[Optional: references, blockers, context]
Check if client label exists:
gh label list --repo DaveX2001/deliverable-tracking | grep -i "{client}"
If label doesn't exist, create it with client color:
gh label create "{client}" --repo DaveX2001/deliverable-tracking --color "C5DEF5" --description "{Client} client"
Create the issue with label:
gh issue create --repo DaveX2001/deliverable-tracking \
--title "{Client}: {Brief description}" \
--body "{formatted body}" \
--label "{client}"
Report the created issue URL back to user.