Install
$ agentstack add skill-xinyiai0724-tools-report-to-planning-suggestion ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
报告转产品规划建议 (Report to Planning Suggestion)
概述
读取已落盘的竞品分析报告,结合 gather-product-context 产出的最新产品快照,经 brainstorming 融合分析后,委托 planning-draft 生成符合 DESIGN-DOC 规范的产品规划建议草稿。
本 Skill 仅输出到对话上下文,不落盘任何文件。 落盘由调用 Agent 在用户确认后走 engineering-docs 与 validate-doc。
输入参数
| 参数 | 必填 | 说明 | |------|------|------| | reportPath | 是 | 竞品报告路径,形如 docs/competitive/reports/{competitor-id}-{YYYY-MM-DD}.md | | focus | 否 | 规划焦点提示(如 "v0.16" / "2026-Q3" / "AI 能力"),传给 planning-draft |
前置条件
reportPath必须存在,且为docs/competitive/reports/下的合法报告文件- 报告 frontmatter 必须包含
competitorId与reportDate - workspace 存在可读的
docs/product-planning/_index.yml、specs/_index.yml或change-requests/_backlog.yml(gather-product-context能够产出快照)
执行流程
① 读 reportPath → 提取 frontmatter + 正文 5 个章节
校验 frontmatter.competitorId 是否存在
↓
② 委托 gather-product-context → 获取结构化产品快照
↓
③ 委托 brainstorming → 输入 {报告摘要, 产品快照, focus 提示}
探索:
- 本次竞品动向是否暴露我方空白点
- 是否与 baseline spec 或在途 CR 冲突、重叠
- 可能影响的版本主题与优先级
↓
④ 委托 planning-draft → 传入 brainstorming 结论 + 产品快照
生成符合 DESIGN-DOC 规范的规划建议草稿(Markdown)
↓
⑤ 将完整草稿输出到对话,并明确提示:
「以上为草稿,仅基于 {reportPath} 与产品快照生成;
确认后由 competitive-analyst-agent 调用 engineering-docs
落盘到 docs/product-planning/,再调 validate-doc 校验。」
输出内容(仅对话,不落盘)
输出为两段:
- 溯源说明(顶部):
- 来源报告:
reportPath - 对应竞品:
competitorId+ name(从报告 frontmatter 读取) - 产品快照生成时间
- focus(若提供)
- 规划建议草稿(主体):
沿用 product-planning-agent 定义的 DESIGN-DOC 结构:
- YAML Frontmatter(由后续
engineering-docs生成,此处仅展示内容主体) - 规划背景与目标
- 现状分析(含竞品动向摘要)
- 版本规划建议
- 依赖与风险
- 成功指标
- 下一步行动建议
读写清单
report-to-planning-suggestion:
read:
- docs/competitive/reports/*.md
write: []
delegates:
- gather-product-context
- brainstorming
- planning-draft
- engineering-docs # 仅由调用 Agent 在用户确认后触发
- validate-doc # 同上
错误处理
| 场景 | 行为 | |------|------| | reportPath 不存在或不在 docs/competitive/reports/ 下 | 中止并提示用户先用 write-competitive-report 生成报告 | | 报告 frontmatter 缺少 competitorId | 中止并提示报告格式异常,建议重新生成 | | gather-product-context 快照为空 | 降级提示:当前产品上下文为空,规划建议仅基于竞品动向,可能粒度较粗 | | brainstorming / planning-draft 失败 | 透传错误,返回部分产出并注明降级 |
注意事项
- 只读入口:本 Skill 不落盘;落盘必须由调用 Agent 在用户确认后显式走
engineering-docs - 完整展示:规划草稿不得省略章节
- 草稿状态提示:输出时必须明确标注「以上为草稿」
- 溯源可追:输出顶部必须展示
reportPath与competitorId,便于审阅者回到报告原文核对 - 前端入口契约:平台前端竞品报告详情页「转为规划建议」按钮后续通过
reportPath入参触发本 Skill
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: xinyiai0724
- Source: xinyiai0724/tools
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.