Create comprehensive fundraising playbook covering timeline, investor targeting, outreach cadence, meeting progression, due diligence preparation, term sheet negotiation, and closing process. Run disciplined fundraising that maximizes leverage and closes on favorable terms.
Comprehensive brand identity system including brand strategy, visual identity (colors, typography, logo direction), messaging architecture (taglines, boilerplates), and tone of voice guidelines with before/after examples and implementation roadmap.
Rephrase tasks and requests by avoiding Demand Avoidance triggers for someone with PDA autism spectrum disorder. It transforms demands into exploration and autonomous actions.
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
Advises on growth strategy, user acquisition, retention, and scaling. Use when: discussing growth tactics, user acquisition, retention problems, platform strategies, understanding users, PLG, or scaling growth. Includes: Adjacent User Theory, Understand Work, Kindle Fire Strategy, Platform Cycles, Data Network Effects, PLG frameworks. Sources: Bangaly Kaba, Casey Winters, Brian Balfour, Elena Verna.
Use when planning market entry, designing PMF strategy, or applying Toss's 16-question framework. Includes Pain Point Score, Trojan Horse path, 10x improvement guide.
Conducts user experience research and analysis to inform design decisions. Reviews first-party and third-party user data, analyzes industry trends from UX and visual design perspectives, and plans user research studies. Creates personas, customer segments, design principles, design roadmaps, and research discussion guides.
Comprehensive community building strategy including platform selection, channel structure, member journey mapping, engagement ladder tactics, community programming rituals, moderation guidelines, launch plan, growth strategy, and success metrics for building thriving online communities
Guide for developing SCAPI Custom APIs on Salesforce B2C Commerce
通过提出最多5个高度针对性的澄清问题来识别当前功能规范中未明确定义的领域，并将答案编码回规范中。触发词包括："speckit-clarify"、"speckit澄清"、"规范澄清"、"功能澄清"、"识别模糊点"、"澄清需求"。
以测试与验证为先的方式，按序执行并实现已批准的规范提案。用于实施变更、应用提案、执行规范任务或按已批准计划构建。触发词包括 "openspec开发", "开发", "实施" "实现提案", "应用变更", "执行规范", "按顺序完成任务", "构建功能", "开始实施"。
Create a compelling 10-15 slide investor pitch deck that tells your startup story, demonstrates market opportunity, proves traction, and makes a clear ask. Build a deck that gets meetings, progresses conversations, and closes rounds.
Create design documents for features or systems. Use when architecture planning, API design, or technical decisions are needed before implementation.
Generates detailed actionable conversion specifications from audit results for architectural migration
機能要件と非機能要件の分類と定義スキル。要件を適切なカテゴリに分類し、漏れなく体系的に管理するための方法論を提供する。 Anchors: • ISO/IEC 25010 品質モデル / 適用: NFR分類と品質特性定義 / 目的: 8品質特性による網羅的カバレッジ • Don't Make Me Think (Steve Krug) / 適用: ユーザビリティ要件定義 / 目的: 直感性と認知負荷の測定基準 • Software Requirements (Karl Wiegers) / 適用: 要件品質検証 / 目的: SMART原則による検証可能性確保 Trigger: Use when classifying requirements into functional and non-functional categories, defining measurable quality attributes for NFRs, or validating requirements completeness and consistency. requirements, functional, non-functional, NFR, quality attributes, ISO 25010, SMART criteria, measurability
April Dunford's positioning framework for clear market differentiation. Creates positioning statements, messaging hierarchies, competitive positioning, and channel-specific messaging guides.
Competitive analysis - market research, feature gaps. Use when exploring what competitors do.
曖昧性検出と除去スキル。定性的・不明確な表現を具体的・測定可能な要件に変換します。 Anchors: • Don't Make Me Think（Steve Krug）/ 適用: ユーザビリティ判断とUI明確性 / 目的: ユーザーが「考えずに理解できる」表現基準の提供 • 5つの曖昧性パターン / 適用: 要件ドキュメント全体 / 目的: 定性的・曖昧な表現を体系的に検出・排除 • 定量化フレームワーク / 適用: 非機能要件の具体化 / 目的: 「速い」「多い」などの曖昧語を計測可能な指標へ変換 Trigger: 要件ドキュメントに「速い」「多い」「適切に」などの定性的表現や、定義・スコープ・条件が不明確な箇所があるとき。受容基準・パフォーマンス目標・条件の曖昧性を解決してから開発を開始する必要があるときに適用。
要件検証の専門スキル。要件の完全性・一貫性・実現可能性・検証可能性を体系的に評価し、品質を保証する。 品質チェックリストと検証スクリプトを用いて、レビュー結果の整理と改善提案まで行う。 Anchors: • Software Requirements (Karl Wiegers) / 適用: 要件検証全体 / 目的: 完全性・一貫性・実現可能性の評価 • IEEE 830 SRS Standard / 適用: 要件品質基準 / 目的: 検証可能な構造化 • Don't Make Me Think (Steve Krug) / 適用: ユーザー要件 / 目的: ユーザビリティ視点の確認 Trigger: Use when verifying requirements quality, checking consistency/completeness, assessing feasibility, or drafting verification reports. requirements verification, requirements quality, consistency check, completeness check, feasibility assessment, 要件検証, 要件レビュー
