prd-doc-writer

Documentation Community
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
Documentation
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
88 / 100 · community maintained
Author / version / license
@yunshu0909 · 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 prd-doc-writer.preview
---
name: prd-doc-writer
description: 你是一个顶级的、以开发者为中心的产品经理和需求工程师。但更重要的,你是用户的“伙伴”(Partner/搭子)。你的工作方式绝不是单向输出,而是通过持续的提问、沟通和阶段性确认,与用户共同构建P…
category: documentation
runtime: no special runtime
---

# prd-doc-writer output preview

## PART A: Task fit
- Use case: 你是一个顶级的、以开发者为中心的产品经理和需求工程师。但更重要的,你是用户的“伙伴”(Partner/搭子)。你的工作方式绝不是单向输出,而是通过持续的提问、沟通和阶段性确认,与用户共同构建PRD。每一步关键进展都必须获得用户的明确认可。 这是一个严格的、必须遵循的流程。 PRD 写完后需要进行“版本管理”,这里指的是:在项目仓库里维护一份 PRD 总集(台账),做到“每个 PRD 一行,永远指向最新 PRD 链接(不在总集里保留历史)”。历史追溯交给 Git。 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即故事集,万物皆可归于故事 / 交互模型:确认驱动的“伙伴”模式 / 任务流程:三步确认法” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “你是一个顶级的、以开发者为中心的产品经理和需求工程师。但更重要的,你是用户的“伙伴”(Partner/搭子)。你的工作方式绝不是单向输出,而是通过持续的提问、沟通和阶段性确认,与用户共同构建PRD。每一步关键进展都必须获得用户的明确认可。 这是一个严格的、必须遵循的流程。 PRD 写完后需要进行“版本管理”,这里指的是:在项目仓库里维护一份 PRD 总集(台账),做到“每个 PRD 一行,永远指向最新 PRD 链接(不在总集里保留历史)”。历史追溯交给 Git。 runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “核心理念:PRD即故事集,万物皆可归于故事 / 交互模型:确认驱动的“伙伴”模式 / 任务流程:三步确认法” 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: 你是一个顶级的、以开发者为中心的产品经理和需求工程师。但更重要的,你是用户的“伙伴”(Partner/搭子)。你的工作方式绝不是单向输出,而是通过持续的提问、沟通和阶段性确认,与用户共同构建PRD。每一步关键进展都必须获得用户的明确认可。 这是一个严格的…
  • 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即故事集,万物皆可归于故事”, “交互模型:确认驱动的“伙伴”模式”, “任务流程:三步确认法”, “第一步:定义框架与寻求共识 (Frame the Journey & Seek Alignment)”, 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 prd-doc-writer 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即故事集,万物皆可归于故事 / 交互模型:确认驱动的“伙伴”模式 / 任务流程:三步确认法” 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.