@prd-improve/cli 1.1.0 → 1.1.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/dist/skill/prd-improve-forge/SKILL.md +1 -1
  2. package/package.json +1 -1
package/dist/skill/prd-improve-forge/SKILL.md CHANGED
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: prd-improve-forge
3
- description: Use when user wants to write, refine, or structure a PRD for a specific feature — converting vague ideas, meeting notes, chat snippets, or legacy docs into a complete, edge-specified spec following PRD Improve schema v0.2. Differentiator from generic PRD helpers — drives multi-round boundary questioning (P0/P1/P2 priorities) via feature-type checklists and outputs structured `.prd/features/<slug>/working/prd.yaml` (not free-form Markdown), so downstream `prd validate` / `prd freeze` / `prd context` CLI commands can consume it. Triggers on Chinese phrases like '写 PRD'、'整理需求'、'规范化需求'、'把 X 整理成 PRD'、'梳理功能边界'、'会议纪要整理成需求'、'聊天记录整理成 PRD'、'把这个想法变成规格'、'帮我做需求规格化' or English equivalents. DO NOT trigger for: (a) general product strategy / OKR / roadmap discussion without a specific feature scope; (b) writing code, implementation, architecture, or technical design docs; (c) editing a single field of an already-frozen PRD (use `prd` CLI directly); (d) high-level vision documents or pitch decks. Also triggers on PRD refresh requests — when an existing .prd/features/<slug>/working/prd.yaml needs to be updated against a new PRD version. Refresh triggers '同步新版 PRD'、'重新 sync'、'基于新版 PRD 更新'、'PRD 改了'、'PRD 升级了'、'feature 升级'、'对齐 PRD'、'incorporate PRD changes' or equivalents. Skill loads existing yaml + new PRD, runs structured field-level diff via `prd refresh`, walks PM through decisions, writes patches + appends working/CHANGELOG.md. DO NOT trigger refresh for PRD 大改 / 几乎重写(→ 重跑白板模式);单字段修订(→ 直接 edit yaml 或 prd CLI);现有 yaml 不存在(→ 自动 fallback 白板模式).
3
+ description: Use when the user wants to write, refine, or structure a PRD for a specific feature — turning vague ideas, meeting notes, chat snippets, or legacy docs into a complete, edge-case-specified requirements spec. Unlike generic PRD helpers, it drives multi-round boundary questioning (P0/P1/P2 priorities) through feature-type checklists and produces a structured YAML spec, not free-form Markdown. Triggers on phrases like '写 PRD'、'整理需求'、'规范化需求'、'把 X 整理成 PRD'、'梳理功能边界'、'会议纪要整理成需求'、'聊天记录整理成 PRD'、'把这个想法变成规格'、'帮我做需求规格化' or English equivalents. Also handles refresh mode — updating an existing PRD against a new or changed PRD version — triggered by '同步新版 PRD'、'重新 sync'、'基于新版 PRD 更新'、'PRD 改了'、'PRD 升级了'、'feature 升级'、'对齐 PRD'、'incorporate PRD changes' or equivalents. DO NOT trigger for: (a) general product strategy / OKR / roadmap discussion with no specific feature scope; (b) writing code, implementation, architecture, or technical design docs; (c) editing a single field of an already-finalized PRD; (d) high-level vision documents or pitch decks; (e) a near-total rewrite of an existing PRD (start a fresh PRD instead).
4
4
  ---
5
5
 
6
6
  # PRD Improve Forge
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@prd-improve/cli",
3
- "version": "1.1.0",
3
+ "version": "1.1.1",
4
4
  "description": "PRD Improve CLI - validate / freeze / context for .prd/features/*.yaml",
5
5
  "license": "MIT",
6
6
  "type": "module",