feat: add sub-command router and sprint ceremony workflows to rhdh-jira

[schultzp2020]

Summary

Adds a sub-command router and 5 workflow references to the rhdh-jira skill, covering all applicable Scrum ceremonies for the RHDH team. Also updates the skill-maker skill with patterns learned during development.

rhdh-jira: New sub-commands

Command	Ceremony	Description
assign	Any time	5-layer deep assignee analysis: team roster (GraphQL team.teamV2), expertise profiling, sprint capacity, soft signals (bus factor, growth), context proximity
refine	Backlog Refinement	6-check refinement: missing fields per exit criteria, duplicates, hierarchy integrity, unaddressed comments, staleness, sprint readiness
plan	Sprint Planning	Carryover report, velocity trend, per-member capacity, ready-for-planning queue, sprint fill suggestions, critical customer bugs, retro action items
sprint-report	Sprint Review/Demo	Committed vs completed, per-member breakdown, epic progress, demo checklist with naming conventions and venue routing
release	Feature Refinement + SOS	PI funnel states, feature matrix, epic roll-up, cross-team dependency map, blocker bugs, RN readiness, risk assessment. Intended to replace rhdh-release-triage

Architecture

• Sub-command router with scripts/command-metadata.json as single source of truth
• API preference order: acli → GraphQL → REST API (skip acli for bulk operations)
• Cross-cutting conventions centralized in SKILL.md (confirmation flow, error handling, team conventions)
• Data flow documentation between sub-commands (plan reuses assign capacity, sprint-report shares velocity pattern, release invokes assign)
• Exit criteria single-sourced in references/workflows.md — refine and release point to it

Key GraphQL discoveries

• team.teamV2(id, siteId) returns full team roster directly — no REST Teams API needed
• JiraComponentsField fragment works: components { edges { node { name } } }
• JiraTeamViewField.selectedTeam.fullTeam.members returns roster via issue context
• No GraphQL mutation exists for issue assignment — acli/REST for writes
• "Team[Team]" = {teamId} works in JQL (corrected Gotcha 5)

skill-maker updates

• Deduplication check with intentional duplication exception (avoid transitive loading)
• Avoid hardcoded thresholds writing pattern — describe the signal, not an arbitrary number
• Multi-API preference order pattern for skills wrapping CLI + GraphQL + REST
• Router evolution guidance — when and how to upgrade from reference files
• Cross-cutting conventions and data flow documentation patterns

Reviewed by

Two specialized reviewer agents (2 rounds each):

• Skills expert — spec compliance, architecture, reference independence, description optimization
• Agile/Scrum expert — ceremony coverage, workflow alignment with RHDH Agile process, output practicality

Files changed

New (6):

• references/assign.md (269 lines)
• references/refine.md (298 lines)
• references/plan.md (219 lines)
• references/sprint-report.md (207 lines)
• references/release.md (296 lines)
• scripts/command-metadata.json

Modified (7):

• SKILL.md — router, API preference, conventions, workflows, description
• references/auth.md — GRAPHQL_URL, ORG_ID with discovery
• references/graphql-queries.md — team roster query, field types, 3-way API table
• skills/skill-maker/SKILL.md — dedup exception, hardcoded thresholds
• skills/skill-maker/references/api-skill-patterns.md — multi-API pattern
• skills/skill-maker/references/architecture-patterns.md — router evolution, conventions, data flow
• README.md — all 5 sub-commands documented