Explorar skills

Side-by-side comparison of 2-4 business ideas on 8 weighted dimensions. Produces a ranked matrix with scores, trade-off analysis, and a clear recommendation of which idea to pursue first. Use when user runs `/idea-comparison`, asks to "compare these ideas", "which idea should I pursue", "rank my ideas", "prioritize between ideas", or has multiple business concepts and needs to choose.

Problem existence and pain validation for bootstrapped founders. Assesses whether the problem is real, how severe the pain is, willingness to pay, buyer persona clarity, and urgency triggers — separating founder assumptions from market evidence. Use when user runs `/problem-analysis`, asks about "is this a real problem", "pain severity", "willingness to pay", "buyer persona", "customer pain", "pro

Use when you want to audit project dependencies — scans all lockfiles for CVEs, outdated major versions, and license violations. Run before releases or periodically as a health check.

Use when you are about to create a git commit — generates a conventional commit message with type(scope): TICKET description format. Auto-detects ticket from branch name or arguments. Always use this instead of running git commit directly.

Use when you encounter a bug, error, or unexpected behavior during a task — follows a reproduce → isolate → fix → verify cycle. Invoke this instead of guessing at a fix.

Use when starting work on a GitHub or Jira issue — reads the issue, explores affected code, and produces a ready-to-execute implementation plan. Invoke this at the start of any ticket-driven task instead of jumping straight to /plan.

Use at the start of a session on an unfamiliar or returning project — reads architecture docs, recent activity, open work, and coding conventions to prime context before starting any task. Invoke this before /plan or /issue when you haven't worked on the project recently.

Use when a file or module has grown too complex — removes unnecessary abstractions, dead code, and over-engineering without changing behavior. Invoke after implementing a feature when the code feels over-engineered.

Use before writing any code for a new feature, task, or significant change — produces a structured implementation plan with affected files, ordered steps, risks, and open questions. Always invoke this at the start of any non-trivial implementation task and wait for explicit approval before writing code.

Use when you are about to open a GitHub pull request — generates a semver-prefixed title ([PATCH/MINOR/MAJOR] TICKET: description) and structured body from commits. Always invoke this instead of running gh pr create directly.

Score and prioritize all open GitHub Issues by Impact x Effort x Urgency. Outputs a triage matrix (TRIAGE.md), applies priority labels, and suggests a sprint plan. Use when your issue backlog is overwhelming, you don''t know what to work on next, or you want a structured sprint plan. Triggers on: "issue 整理", "バックログ整理", "何から手をつける", "issue優先度", "sprint plan", "issue-triage", "issue triage". DO NOT U

Use before implementing a complex, high-stakes, or cross-cutting feature — produces a full technical specification including data model, API contract, edge cases, and open questions. The planning layer above /plan. Invoke this when /plan alone isn't detailed enough.