fluxly Search skills… ⌘K 中文 Publish

pm/prd-writing

Writing Verified v1.0.0
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
Writing
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
92 / 100 · audit passed
Author / version / license
@echoVic · v1.0.0 · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No special requirements
Permissions
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview pm-prd-writing.preview 
---
name: pm/prd-writing
description: 完成需求穿透和调研分析后，需要输出一份完整的产品需求文档(PRD)，供设计师、开发者、测试人员使用。 参见 pm/requirement-penetration skill 的输出要求。 使用…
category: writing
runtime: no special runtime
---

# pm/prd-writing output preview

## PART A: Task fit
- Use case: 完成需求穿透和调研分析后，需要输出一份完整的产品需求文档(PRD)，供设计师、开发者、测试人员使用。 参见 pm/requirement-penetration skill 的输出要求。 使用 WebSearch 搜索相关竞品： | 竞品 | 核心功能 | 用户体验亮点 | 用户痛点 | 我们的机会 | |------|----------|--------------|----------|------------| runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “适用场景 / PRD 标准结构 / 1. 概述” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “完成需求穿透和调研分析后，需要输出一份完整的产品需求文档(PRD)，供设计师、开发者、测试人员使用。 参见 pm/requirement-penetration skill 的输出要求。 使用 WebSearch 搜索相关竞品： | 竞品 | 核心功能 | 用户体验亮点 | 用户痛点 | 我们的机会 | |------|----------|--------------|----------|------------| runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “适用场景 / PRD 标准结构 / 1. 概述” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.
Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

  • Core job: 完成需求穿透和调研分析后，需要输出一份完整的产品需求文档(PRD)，供设计师、开发者、测试人员使用。 功能名称：[清晰简洁的名称] 版本：1.0 日期：[当前日期] 作者：PM Agent 下游 Agent 请优先阅读本节，需要细节时再查阅完整文档。 核心…
  • Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
  • Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

  • Structure: The skill is organized around “适用场景”, “PRD 标准结构”, “1. 概述”, “摘要”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
  • Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
  • Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

  • Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
  • Invocation: Name pm/prd-writing directly; if the source includes slash commands, start with the command and then add task context.
  • Validation: Start small and check whether the result follows “适用场景 / PRD 标准结构 / 1. 概述” before expanding.

Boundaries And Review

  • Dependencies: It usually needs no extra API key, so start with a small validation task.
  • Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
  • Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.