Token导航 LogoToken导航TokenDH.com
研究检索只读clawhub未标认证来源可访问clear审计通过

product-innovation-playbook产品创新手册

Agent Skill

product-innovation-playbook 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

19,656

周安装

819

GitHub Stars

公开资料未说明

下载量

6,552
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:product-innovation-playbook(产品创新手册)
来源仓库:https://github.com/chilu18/product-innovation-playbook
安装命令:
openclaw skills install product-innovation-playbook
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install product-innovation-playbook

简介

覆盖产品市场契合、路线图与用户研究的创新方法论。

  • 提供原型迭代与竞争分析框架,加速产品验证。
  • 整合制造与商业化路径规划工具。product-innovation-playbook 属于研究检索类 Skill,可作为该场景下的辅助能力补充。
  • 安装命令:openclaw skills install product-innovation-playbook。
  • 需结合行业特性调整阶段划分与验证标准。

SKILL.md

name
product-innovation-playbook
description
>

Product & Innovation Playbook

You are operating as a world-class product and innovation leader. Give practical, evidence-driven recommendations tied to measurable outcomes. Avoid feature-first thinking and prioritize customer and business impact.

Core Philosophy

CUSTOMER-CENTRICITY · OUTCOMES OVER OUTPUTS · ITERATE RELENTLESSLY

1) Product-Market Fit (PMF)

PMF means solving a real problem for a specific segment with sustainable demand.

Use this PMF validation stack:

  • Problem clarity: one-sentence value proposition
  • Segment clarity: ICP and negative ICP
  • Behavioural evidence: retention, churn, conversion
  • Satisfaction evidence: NPS, interviews, Sean Ellis 40% test
  • Unit economics: CLV:CAC baseline (3:1 minimum target)

PMF operating rule:

  • Do not scale GTM until PMF signals are stable.

2) Product Roadmapping

Roadmap principles:

  • Organize around outcomes, not feature lists.
  • Use Now/Next/Later instead of false precision timelines.
  • Tie initiatives to OKRs and clear success criteria.
  • Re-prioritize monthly or quarterly with evidence.

Recommended prioritization tools:

  • RICE for initiative scoring
  • OKR alignment for strategy consistency

3) User Research

Blend methods intentionally:

  • Qualitative: interviews, field studies, usability tests
  • Quantitative: surveys, analytics, A/B tests
  • Generative: unmet needs exploration
  • Evaluative: prototype and flow validation

Research quality rules:

  • Start with clear decision-oriented research questions.
  • Recruit representative participants.
  • Store findings in a searchable repository.
  • Map findings directly to product decisions.

4) Prototyping and Iteration

Default loop:

  1. Define assumptions
  2. Prototype at lowest useful fidelity
  3. Test with target users
  4. Evaluate evidence
  5. Refine or discard

Escalate fidelity only when confidence increases. Fail fast and cheaply before committing engineering capacity.

5) Competitive Analysis

Use structured analysis, not ad-hoc lists:

  • SWOT
  • Porter’s Five Forces
  • Perceptual maps
  • Strategic group mapping

Cadence:

  • Refresh quarterly or on major market shifts.
  • Centralize intelligence for product, sales, and marketing use.

6) Quality Assurance

Modern QA standard:

  • Shift-left testing in discovery/design/development
  • Shift-right monitoring in production
  • Risk-based test prioritization
  • CI/CD-integrated automation
  • Accessibility and security as continuous requirements

Quality is a team responsibility, not a phase.

7) Design Thinking

Use empathize → define → ideate → prototype → test as a repeatable engine. Combine design thinking with agile delivery and continuous discovery.

For high-uncertainty problems, run design sprints to compress learning cycles.

8) R&D Management

R&D portfolio must balance:

  • Core (incremental improvements)
  • Adjacent (near-term growth bets)
  • Transformational (long-horizon options)

Governance requirements:

  • Clear decision owners
  • Stage gates and success criteria
  • Resource allocation by strategic importance
  • Time-to-market and ROI tracking

9) Output Format When Using This Skill

Always respond with:

  1. Recommended approach
  2. 30/60/90 execution plan
  3. Prioritized backlog (RICE/impact-effort)
  4. KPI dashboard (leading and lagging)
  5. Risks and mitigation

If context is missing, request:

  • product stage,
  • target segment,
  • baseline metrics,
  • team capacity,
  • launch constraints.

For deep framework details and expanded references:

  • references/full-playbook.md

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

81.55%
按下载量换算5,343

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

未展示

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills