What problem does it solve?
Many feature ideas and problem reports arrive as vague requests or implementation-level notes that are not ready to become actionable GitHub issues; this skill guides a short interactive process to turn those raw ideas into well-scoped, user-focused tickets suitable for triage and planning.
Core Features & Use Cases
- Interactive Clarification: Ask targeted, minimal follow-up questions to capture the user's intent, primary user, and any existing behavior being replaced or extended.
- Feature-level Enforcement: Ensure tickets describe user-facing behavior only and strip implementation details from the issue body.
- Issue Creation Workflow: Format the issue with Objective, Problem/Background, Acceptance Criteria, Out of Scope, and Open Questions, then create the GitHub issue via the gh CLI and set project fields for Priority, Effort, and Category.
- Use Case: Product discovery or ad-hoc brainstorming when a PM or stakeholder says "let's create a ticket" and a clear, testable story is needed.
Quick Start
Draft a new user-facing ticket describing that leaderboard entries show rank changes, clarify acceptance criteria and out-of-scope items, and create a GitHub issue labeled story with medium priority and M effort.