Explorar skills

Distill raw observations and research data into meaningful, actionable product insights. Use this skill when a team has research data and needs to move from observations to insights that can drive decisions.

Run a pre-mortem analysis to identify ways a product initiative could fail before it launches. Use this skill when a team wants to proactively surface failure modes and plan mitigations before committing to execution.

GitHub Issue の実装計画を作成・更新する。コードベースを分析し、影響範囲・実装手順・リスクを整理して Issue コメントまたは新規 Issue として投稿する。 ユーザーが「計画立てて」「実装計画」「設計して」「#123 の計画」「/smart-issue-plan #123」と言ったら起動する。 smart-issue-resolve（実装着手）とは別物。計画だけ作りたいときに使う。 -codex-loop を付けると投稿前に Codex レビューループを実施する（Claude Code + Codex プラグイン環境前提）。

한국 시장 대상 프론트엔드 프로젝트의 공통 로컬라이제이션 오버라이드. Pretendard 폰트, word-break keep-all, 한국어 콘텐츠 패턴, standalone HTML 출력. taste-skill 계열 디자인 skill과 함께 적용.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when converting wiki-exported requirement documents (containing docx, xlsx, md, images) into standardized templates (functional requirement docs + FAQ docs), with a gaps checklist for product managers to supplement missing information.

Use when tempted to treat the current session as interchangeable with past or future ones — the every-session-is-unique discipline, and the invocation surface that fires durable-fix skills a fungible-session mindset would skip. Fires when about to defer something to "a future session" as if that session will reconstitute this exact context, when a memory-aware agent assumes "I'll just re-derive it

Design and refine team rituals and operating rhythms that build alignment and operating discipline. Use this skill when a team wants to improve how they work together through intentional recurring practices.

Verify Phase D doc updates are accurate. Binary pass/fail gate — checks stat accuracy, file path validity, code-doc sync, completeness. Runs after /update-docs.

Guide for working through a Jira story efficiently by separating context gathering, immutable evidence collection, codebase exploration, human-in-the-loop specification refinement, execution planning, and implementation. Use when turning a ticket into a reliable engineering workflow instead of jumping straight to code.

Run the graph-retriever subagent — intelligent, iterative retrieval over the derived graph query layer. The maintainer asks a free-form information-need question ("where is X", "what depends on Y", "which findings concern Z"); the agent constructs a strong query, runs a bounded retrieve→read→judge→refine loop (≤10 iterations) with adaptive traversal, and returns a cited answer set. Emits substrate

Market timing and entry window assessment for bootstrapped founders. Evaluates whether the moment is right — strategic inflection points, adoption stage, buyer behavior shifts, regulatory catalysts, incumbent vulnerability windows, and bootstrapper timing fit. Use when user runs `/timing-analysis`, asks about "why now", "market timing", "is it too late", "is it too early", "entry window", "inflect