Menu
Analyze GitHub issues and create a comprehensive plan to solve them. Triggers: "analyze issue", "plan issue", "investigate issue".
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | gh-issue |
| description | Analyze GitHub issues and create a comprehensive plan to solve them. Triggers: "analyze issue", "plan issue", "investigate issue". |
| allowed-tools | Bash(git:*), Bash(gh:*), Glob, Grep, Read, mcp__github__* |
| agent | plan |
Deep-dive on one or more GitHub issues. Find the problem and generate a plan. Do not write code. Explain the problem clearly and propose a comprehensive plan to solve it.
/gh-issue <issues...>
issues (required): One or more GitHub issue numbers (assumes videojs/v10 repo) or full GitHub issue URLs/gh-issue 123
/gh-issue 123 456 789
/gh-issue https://github.com/videojs/v10/issues/123
/gh-issue 123 https://github.com/other/repo/issues/456
$ARGUMENTS
Fetch details for each issue using GitHub tools. Arguments can be issue numbers (assumes videojs/v10 repo) or full GitHub issue URLs. When multiple issues are provided, analyze them together to understand relationships and create a unified plan.
You are an experienced software developer tasked with diagnosing issues.
Labels — Look for:
api, rfc, breaking-change → API/Architecturedocs, documentation → Documentationdx, types, typescript → Developer Experiencea11y, accessibility → Accessibilityui, component → UI Componentsbug, fix → Bug fixenhancement, feature → New featureTitle and Body Keywords:
| Keywords | Type |
|---|---|
| "API", "design", "RFC", "architecture", "breaking" | API/Architecture |
| "ergonomics", "types", "inference", "DX", "developer experience" | DX |
| "documentation", "docs", "README", "guide", "handbook" | Documentation |
| "accessibility", "keyboard", "screen reader", "ARIA", "focus" | Accessibility |
| "component", "compound", "render prop", "polymorphism" | UI Components |
Affected Packages (from file paths or mentions):
packages/core/, packages/store/ → Core architecturepackages/html/, packages/react/ → UI/Componentssite/ → DocumentationBased on detected type, load the relevant skill for domain expertise:
| Detected Type | Load Skill | Why |
|---|---|---|
| API proposal, RFC, architecture | api | Extensibility, progressive disclosure, type safety principles |
| DX, ergonomics, types | api | DX principles, TypeScript patterns, state/adapter patterns |
| Documentation | docs | Tone, structure, code examples, Diátaxis types |
| Component reference pages | api-reference | API reference page structure, builder conventions |
| Accessibility | aria | Keyboard, focus, ARIA patterns |
| UI component implementation | component | Compound components, polymorphism, styling patterns |
| Bug/Feature (general) | api | General principles apply |
Load the skill before proceeding to analysis.
Notes:
aria) instead of generic apiExplain the issue in detail, including:
Create a plan to solve the issue that includes:
Core Changes:
Quality Assurance:
Risk Assessment:
Skill-Specific Considerations:
For API/Architecture/DX issues (with api skill):
For Documentation issues (with docs skill):
For Accessibility issues (with aria skill):
For UI Component issues (with component skill):
render prop or asChild?Include:
ONLY CREATE A PLAN. DO NOT WRITE ANY CODE. Your task is to create a thorough, comprehensive strategy for understanding and resolving the issues.
Implement a feature documented in the SPF feature registry. Consumes a feature doc at internal/design/spf/features/<name>.md and produces the engine-side code: new behaviors, updates to existing behaviors, media-layer / network-layer primitives, and tests. The implementation analog of /spf-document-feature (which produces the doc; this consumes it). Walks through resolving the doc's open questions before coding, maps phases to discrete chunks, applies the SPF conventions catalog, routes to downstream skills (/spf-create-behavior, /spf-update-behavior, /refactor-behavior) per chunk shape, and updates the feature doc's Status / Implementation surface / Verification sections as code lands. Triggers: "implement feature", "implement SPF feature", "build feature", "code feature", "scope feature implementation", "implement <feature-name>".
Create a new SPF behavior with conventions-aligned shape. Walks through purpose articulation (carries /refactor-behavior's purpose-first discipline), signal type choice, slot map design, composition placement, cleanup pattern selection, test placement, and engine wiring. Distinct from /refactor-behavior (which modifies an existing behavior preserving its purpose) and /spf-update-behavior (which modifies an existing behavior whose purpose is changing). Triggers: "create behavior", "new behavior", "create SPF behavior", "add behavior", "scaffold behavior", "new SPF behavior".
Produce or update an entry in the SPF use-case-composition registry at internal/design/spf/use-cases/. Triangulates context from multiple sources (Notion, GitHub, pasted writeups, existing use-case docs, constituent feature docs, codebase), grounds the use case in the four composition mechanisms (subtract / add / alternative-impl / alternative-default-config), applies use-case-specific cross-cutting concern checks, drafts the doc at the appropriate definition depth, and cascades narrow updates to constituent feature docs and sibling use cases. Triggers: "document use case", "register use case", "use case doc", "update use case doc", "deepen use-case stub", "new SPF use case", "use case composition", "draft use-case registry entry", "new use case composition".
Implement a use-case composition documented in the SPF use-case-composition registry. Consumes a use-case doc at internal/design/spf/use-cases/<name>.md and produces the engine-side code: a variant engine factory, a parallel adapter, composition wiring, use-case-specific behaviors (if any), and tests. The implementation analog of /spf-document-use-case (which produces the doc; this consumes it). Walks through disambiguation + routing (verify the request is actually a use case, check constituent-feature implementation status), resolves the doc's open questions with the user, maps phases to chunks, routes to downstream skills (/spf-implement-feature for unimplemented constituents, /spf-create-behavior, /spf-update-behavior, /refactor-behavior), and updates both the use-case doc and constituent feature docs as code lands. Treats the use-case doc as a starting point for planning, not a hardened specification. Triggers: "implement use case", "implement SPF use case", "implement use-case composition", "build use ca
Update an existing SPF behavior whose purpose is changing or expanding. Distinct from /refactor-behavior, which preserves purpose — this skill handles cases where the behavior gains new responsibility (new state slot to react to, new lifecycle phase, new constraint, new code path). Carries /refactor-behavior's purpose-first discipline applied to the *purpose change*. Triggers: "update behavior", "extend behavior", "modify behavior", "change behavior purpose", "expand behavior responsibility".
Produce or update an entry in the SPF feature registry at internal/design/spf/features/. Triangulates context from multiple sources (Notion, GitHub, pasted writeups, existing feature docs, codebase), grounds the feature in the cluster heuristics, applies cross-cutting concern checks, drafts the doc at the appropriate definition depth, and cascades narrow updates to related feature docs. Triggers: "document feature", "register feature", "feature doc", "update feature doc", "deepen feature stub", "draft feature registry entry", "new SPF feature".