42 skills
testing
对比多个方案文档,输出差异、隐含成本、风险与推荐结论。;use for proposal, comparison, decision workflows;do not use for 忽略用户给的约束, 伪造数据支持结论.
testing
Conducts evidence-based product discovery through customer interviews and assumption testing. Use at project start to validate problem-solution fit.
testing
Dispatches an expert reviewer agent to critique workflow artifacts. Use when a roadmap, implementation, or step needs quality review before proceeding.
tools
# SKILL: IDEATION & DREAMING **Goal:** Define the plugin concept and initialize the project state. **Trigger:** `/dream [Name]` **Output Location:** `plugins/[Name]/` ## ⛔ OUTPUT RESTRICTIONS (MANDATORY) * **NO C++ Code.** * **NO Build Scripts.** * **NO CMake configurations.** ## STEP 1: THE INTERVIEW **Do NOT generate files yet.** If the user prompt is vague, ask 3 clarifying questions: 1. **Sonic Goal:** What is the character? (e.g., "Dirty Tape Delay", "Clean EQ") 2. **Controls:**
tools
思考拍档 - 陪你从混沌中理清局面,锁定核心问题,拆解卡点,共创解法,落地行动
tools
产品命名协作流程。当用户想给产品/项目/模块起名字时使用。通过"灵魂挖掘 → 约束提取 → 路线发散 → 方向选择 → 竞品验证 → 最终确认"的结构化流程,从模糊想法产出有品牌生命力的名字,避免拍脑袋起名。
tools
Load your current context at session start. Shows what you were working on, active priorities, and unresolved flags. Also trigger when resuming after a break or when the user asks what am I working on.
testing
Create a concise morning or evening briefing with notable product, repo, news, and weather updates.
tools
通过苏格拉底式访谈细化需求,优先使用 planning-with-files 文件计划模式生成持久化实施计划,不可用时降级为原生 Plan 模式。适用于需求细化、技术方案设计等场景。
development
Product design, feature planning, and technical architecture for new projects. Explores the problem space through deep requirements gathering, suggests creative features, makes architecture decisions, and produces a structured MVP plan with scope boundaries, a future roadmap, and a deliverable tracker. Uses plan mode for deliberate thinking before writing any artifacts. Use when the user says "mvp", "plan a product", "design features", "what should I build", "feature planning", "scope an MVP", or describes a product they want to plan.
tools
EM-PM conversation to review and prioritize the technical debt backlog. Triggers on demand or when open item count exceeds 20.
testing
Use when the PM asks for staff input on a plan or review, when the EM needs multi-perspective planning or critique, or when deciding between /staff-session and /review-dispatch. Guides tier selection, team composition, and scoping.
development
Interview the user about a feature before writing any code. Produces a reusable SPEC.md artifact. Use when starting any non-trivial feature.
data-ai
Analyze product retention using the Hook Model (trigger, action, reward, investment). Use when users aren't coming back, engagement is low, you need to improve retention, or designing a habit loop for a product feature.
tools
문제 선택 + ICP 초안 + 가설 수립. 어떤 문제를 풀지 좁히는 단계.
testing
Revenue Readiness Audit — 45분 진단, Clarity Dimensions 정량 평가, Track A/B/C 추천. 프로젝트 진단, 매출 준비도 확인 시 사용.
tools
Bun's roadmap and long-term plans
documentation
Create a PRD from scratch. Use when the user says "lets create a product requirements document" or "I want to create a new PRD"
development
Detect potential duplicates across Logics documents. Use when Codex should scan titles and content of requests/backlog/tasks/specs/product briefs/architecture docs to find similar items and propose merge, split, or de-duplication.
documentation
Ask clarifying questions with suggested defaults to raise Understanding/Confidence above 90% for Logics request/backlog/task docs, and to strengthen product or architecture companion docs with a clarified `# Clarifications` section plus optional status updates.