원클릭으로
product-capability
将PRD意图、路线图需求或产品讨论转化为可实施的方案计划,在开始多服务工作之前暴露约束、不变性、接口和未解决的决策。当用户需要ECC原生的PRD到SRS通道,而不是模糊的规划文本时使用。
메뉴
将PRD意图、路线图需求或产品讨论转化为可实施的方案计划,在开始多服务工作之前暴露约束、不变性、接口和未解决的决策。当用户需要ECC原生的PRD到SRS通道,而不是模糊的规划文本时使用。
Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents. v2.1 adds project-scoped instincts to prevent cross-project contamination.
Orchestrate building a brand-new feature end to end — research, plan, TDD implementation, review, and gated commit — by delegating each phase to the matching ECC agent. Use when adding a capability that does not exist yet.
Orchestrate bootstrapping a working MVP from a design or spec document — ingest the doc, plan thin vertical slices, scaffold the first end-to-end slice, then TDD-implement, review, and gated commit. Use to turn an SDD/PRD into a running starting point.
Orchestrate altering an existing, working feature to new desired behavior — update its tests to the new spec, change the implementation to match, review, and gated commit. Use when behavior is not broken but should be different.
Orchestrate fixing a bug — reproduce it as a failing regression test, fix to green, review, and gated commit — by delegating each phase to the matching ECC agent. Use when existing behavior is broken or wrong.
Shared orchestration engine for the orch-* skill family. Defines the gated Research-Plan-TDD-Review-Commit pipeline, the size classifier, the agent map, and the two human gates that the orch-* operation skills delegate to. Not usually invoked directly.
| name | product-capability |
| description | 将PRD意图、路线图需求或产品讨论转化为可实施的方案计划,在开始多服务工作之前暴露约束、不变性、接口和未解决的决策。当用户需要ECC原生的PRD到SRS通道,而不是模糊的规划文本时使用。 |
| origin | ECC |
该技能将产品意图转化为明确的工程约束。
当问题不在于"我们应该构建什么?",而在于"在开始实现之前,必须明确哪些条件?"时使用。
如果仓库中存在持久化的产品上下文文件,例如 PRODUCT.md、docs/product/ 或程序规范目录,请在此处更新。
如果尚不存在能力清单,请使用以下模板创建:
docs/examples/product-capability-template.md目标不是创建另一个规划栈,而是使隐藏的能力约束变得持久且可复用。
仅读取必要内容:
PRODUCT.md、设计文档、RFC、迁移笔记、运营模式文档将需求压缩为一个精确的陈述:
如果此陈述薄弱,实现将会偏离方向。
提取实现前必须满足的约束:
这些往往是仅存在于高级工程师记忆中的内容。
制定一份SRS风格的能力计划,包含:
以精确的交接点结束:
如有帮助,可指向下一个ECC原生通道:
project-flow-opsworkspace-surface-auditapi-connector-builderdashboard-buildertdd-workflowverification-loop按以下顺序返回结果:
能力
- 一段重新陈述
约束条件
- 固定规则、不变项和边界
实现契约
- 参与者
- 界面
- 状态与转换
- 接口/数据影响
非目标
- 该通道明确不负责的内容
待定问题
- 仍需解决的阻碍或产品决策
交接
- 下一步应执行的操作及应由哪个ECC通道负责