Best fit
- 将PRD意图、路线图需求或产品讨论转化为可实施的方案计划，在开始多服务工作之前暴露约束、不变性、接口和未解决的决策。当用户需要ECC原生的PRD到SRS通道，而不是模糊的规划文本时使用。
affaan-m/ECC
product-capability
将PRD意图、路线图需求或产品讨论转化为可实施的方案计划，在开始多服务工作之前暴露约束、不变性、接口和未解决的决策。当用户需要ECC原生的PRD到SRS通道，而不是模糊的规划文本时使用。
69Collecting
See how to use itView GitHub source
npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/product-capability"Automated source guide
Source checked Jul 28, 2026·Refresh due Oct 26, 2026
Reorganized from the pinned upstream SKILL.md
Turn product-capability's source instructions into a guide you can follow
According to the pinned SKILL.md from affaan-m/ECC: 当问题不在于"我们应该构建什么？"，而在于"在开始实现之前，必须明确哪些条件？"时使用。
npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/product-capability"Bring this context
- A concrete task that matches the documented purpose of product-capability.
- The files, examples, or context the task depends on.
- Your constraints, target environment, and definition of done.
Expected outputs
- A result that follows the pinned product-capability instructions.
- A concise record of assumptions, inputs used, and unresolved questions.
- A final check against the source workflow and relevant permission signals.
Key source sections
Read product-capability through these 5 source sections
Sections are extracted automatically from the pinned SKILL.md and link back to the source.
使用时机
存在PRD、路线图项、讨论或创始人笔记，但实现约束仍然隐式未明 某个功能跨越多个服务、仓库或团队，在编码前需要一份能力契约 产品意图明确，但架构、数据、生命周期或策略影响仍然模糊 高级工程师在评审中反复重申相同的隐藏假设 你需要一份可跨工具链和会话复用的持久化工件
存在PRD、路线图项、讨论或创始人笔记，但实现约束仍然隐式未明某个功能跨越多个服务、仓库或团队，在编码前需要一份能力契约产品意图明确，但架构、数据、生命周期或策略影响仍然模糊
规范工件
如果仓库中存在持久化的产品上下文文件，例如 PRODUCT.md、docs/product/ 或程序规范目录，请在此处更新。
docs/examples/product-capability-template.md如果仓库中存在持久化的产品上下文文件，例如 PRODUCT.md、docs/product/ 或程序规范目录，请在此处更新。目标不是创建另一个规划栈，而是使隐藏的能力约束变得持久且可复用。
不可妥协的规则
不要编造产品事实。明确标记未解决的问题。 将用户可见的承诺与实现细节分开。 明确指出哪些是固定策略、哪些是架构偏好、哪些仍待定。 如果请求与现有仓库约束冲突，请明确说明，而非粉饰太平。 优先使用一份可复用的能力工件，而非零散的临时笔记。
不要编造产品事实。明确标记未解决的问题。将用户可见的承诺与实现细节分开。明确指出哪些是固定策略、哪些是架构偏好、哪些仍待定。
输入
1. 产品意图 issue、讨论、PRD、路线图笔记、创始人消息 2. 当前架构 相关仓库文档、契约、模式、路由、现有工作流 3. 现有能力上下文 PRODUCT.md、设计文档、RFC、迁移笔记、运营模式文档 4. 交付约束 认证、计费、合规、发布、向后兼容、性能、评审策略
产品意图issue、讨论、PRD、路线图笔记、创始人消息当前架构
核心工作流
用户或操作者是谁 此功能上线后存在什么新能力 因此带来了什么结果变化
用户或操作者是谁此功能上线后存在什么新能力因此带来了什么结果变化
SkillSignal prompt templates
Provide the task, context, and acceptance criteria
These prompts were written by SkillSignal from the source structure; they are not upstream text.
Task-start prompt
Confirm source fit, inputs, and outputs before acting.
Use product-capability to help me with: [specific task]. Context: [files, data, or background]. Constraints: [environment, scope, and prohibited actions]. Before acting, check the pinned SKILL.md and explain which sections apply, what inputs are still missing, and what you will deliver.
Source-guided execution
Make the Agent explicitly follow the key extracted sections.
Apply the pinned product-capability source to [task]. Pay particular attention to these source sections: “使用时机”, “规范工件”, “不可妥协的规则”, “输入”, “核心工作流”. Preserve the important decision at each step. Mark facts not covered by the source as “needs confirmation” instead of inventing them. Then verify the result against my acceptance criteria: [criteria].
Result-review prompt
Check omissions, permissions, and source drift before delivery.
Review the current product-capability result: (1) does it satisfy the original task; (2) were any applicable steps or limits in the pinned SKILL.md missed; (3) did it perform any unauthorized file, command, network, or data action; and (4) which conclusions remain unverified? List issues first, then fix only what the source or user authorization supports.
Output checklist
Verify each item before delivery
The task matches the purpose documented in the SKILL.md.
The source section “使用时机” has been checked.
The source section “规范工件” has been checked.
The source section “不可妥协的规则” has been checked.
The source section “输入” has been checked.
Inputs, constraints, and acceptance criteria are explicit.
Unverified facts, compatibility, and outcome claims are clearly marked.
Any file, command, network, or data action has been reviewed.
Choose a different workflow
When another Skill is the better fit
product-capability
Translate PRD intent, roadmap asks, or product discussions into an implementation-ready capability plan that exposes constraints, invariants, interfaces, and unresolved decisions before multi-service work starts. Use when the user needs an ECC-native PRD-to-SRS lane instead of vague planning prose.
A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.
Open source detailproduct-capability
日本語翻訳：このファイルは product-capability 用の日本語翻訳が必要です
A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.
Open source detailab-testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.
Open source detailFAQ
What does product-capability do?
当问题不在于"我们应该构建什么？"，而在于"在开始实现之前，必须明确哪些条件？"时使用。
How do I start using product-capability?
The catalog detected this source-specific install command: npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/product-capability". Inspect the command and pinned source before running it.
Which Agent platforms does it declare?
No dedicated Agent platform is declared in the pinned source record.
Repository stars
234,327
Repository forks
35,711
Quality
69/100
Source repository last pushed
Quality breakdown
Based on traceable docs and repository signals; stars are not treated as quality.
Documentation23/30
Specificity14/25
Maintenance20/20
Trust signals12/25
Compare before choosing
Related Agent Skills and source variants
These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.
product-capability by affaan-m
Translate PRD intent, roadmap asks, or product discussions into an implementation-ready capability plan that exposes constraints, invariants, interfaces, and unresolved decisions before multi-service work starts. Use when the user needs an ECC-native PRD-to-SRS lane instead of vague planning prose.
product-capability by affaan-m
日本語翻訳：このファイルは product-capability 用の日本語翻訳が必要です
ab-testing by coreyhaines31
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
churn-prevention by coreyhaines31
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o
design-intelligence by event4u-app
Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.
View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 1 min
产品能力
该技能将产品意图转化为明确的工程约束。
当问题不在于"我们应该构建什么？"，而在于"在开始实现之前，必须明确哪些条件？"时使用。
使用时机
- 存在PRD、路线图项、讨论或创始人笔记，但实现约束仍然隐式未明
- 某个功能跨越多个服务、仓库或团队，在编码前需要一份能力契约
- 产品意图明确，但架构、数据、生命周期或策略影响仍然模糊
- 高级工程师在评审中反复重申相同的隐藏假设
- 你需要一份可跨工具链和会话复用的持久化工件
规范工件
如果仓库中存在持久化的产品上下文文件，例如 PRODUCT.md、docs/product/ 或程序规范目录，请在此处更新。
如果尚不存在能力清单，请使用以下模板创建：
docs/examples/product-capability-template.md
目标不是创建另一个规划栈，而是使隐藏的能力约束变得持久且可复用。
不可妥协的规则
- 不要编造产品事实。明确标记未解决的问题。
- 将用户可见的承诺与实现细节分开。
- 明确指出哪些是固定策略、哪些是架构偏好、哪些仍待定。
- 如果请求与现有仓库约束冲突，请明确说明，而非粉饰太平。
- 优先使用一份可复用的能力工件，而非零散的临时笔记。
输入
仅读取必要内容：
- 产品意图
- issue、讨论、PRD、路线图笔记、创始人消息
- 当前架构
- 相关仓库文档、契约、模式、路由、现有工作流
- 现有能力上下文
PRODUCT.md、设计文档、RFC、迁移笔记、运营模式文档
- 交付约束
- 认证、计费、合规、发布、向后兼容、性能、评审策略
核心工作流
1. 重述能力
将需求压缩为一个精确的陈述：
- 用户或操作者是谁
- 此功能上线后存在什么新能力
- 因此带来了什么结果变化
如果此陈述薄弱，实现将会偏离方向。
2. 解析能力约束
提取实现前必须满足的约束：
- 业务规则
- 范围边界
- 不变性条件
- 信任边界
- 数据所有权
- 生命周期转换
- 发布/迁移要求
- 故障与恢复预期
这些往往是仅存在于高级工程师记忆中的内容。
3. 定义面向实现的契约
制定一份SRS风格的能力计划，包含：
- 能力摘要
- 明确的非目标
- 角色与界面
- 所需状态与转换
- 接口/输入/输出
- 数据模型影响
- 安全/计费/策略约束
- 可观测性与运维要求
- 阻碍实现的未解决问题
4. 转化为执行
以精确的交接点结束：
- 可直接实现
- 需先进行架构评审
- 需先明确产品细节
如有帮助，可指向下一个ECC原生通道：
project-flow-opsworkspace-surface-auditapi-connector-builderdashboard-buildertdd-workflowverification-loop
输出格式
按以下顺序返回结果：
能力
- 一段重新陈述
约束条件
- 固定规则、不变项和边界
实现契约
- 参与者
- 界面
- 状态与转换
- 接口/数据影响
非目标
- 该通道明确不负责的内容
待定问题
- 仍需解决的阻碍或产品决策
交接
- 下一步应执行的操作及应由哪个ECC通道负责
良好成果
- 产品意图已足够具体，无需在PR评审中重新发现隐藏约束即可实现。
- 工程评审拥有持久化工件，而非依赖记忆或Slack上下文。
- 生成的计划可在Claude Code、Codex、Cursor、OpenCode和ECC 2.0规划界面中复用。
- Source repo
- affaan-m/ECC
- Skill path
- docs/zh-CN/skills/product-capability/SKILL.md
- Commit SHA
- 4e973d3eaf92
- Repository license
- MIT
- Data collected