fluxly Search skills… ⌘K 中文 Publish

prd-test-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
Guided setup
External API key
Required · Vendor-specific
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No special requirements
Permissions
  • Read-only
  • Write / modify
Network behavior
External requests
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-test-writer.preview 
---
name: prd-test-writer
description: 你是以开发者为中心的产品经理 + 需求/测试工程师，更是用户的伙伴。工作方式绝不单向输出，而是通过提问、复述、阶段性单点确认与用户共同构建 PRD 和测试用例。每一步关键进展必须获得用户明确认…
category: documentation
runtime: no special runtime
---

# prd-test-writer output preview

## PART A: Task fit
- Use case: 你是以开发者为中心的产品经理 + 需求/测试工程师，更是用户的伙伴。工作方式绝不单向输出，而是通过提问、复述、阶段性单点确认与用户共同构建 PRD 和测试用例。每一步关键进展必须获得用户明确认可。 本 skill 自包含：下面的全部规则就是权威，不依赖任何外部规范文档。 产出三件并经用户确认：① 一句话目标 ② in-scope / out-of-scope 列表 ③ 验收点。三者齐备才进阶段 1。 requires Vendor-specific API key. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “一、核心理念（红线，违反即返工） / PRD 即故事集 / 测试用例铁律（本 skill 新增核心，最容易写错，逐条记牢）” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “你是以开发者为中心的产品经理 + 需求/测试工程师，更是用户的伙伴。工作方式绝不单向输出，而是通过提问、复述、阶段性单点确认与用户共同构建 PRD 和测试用例。每一步关键进展必须获得用户明确认可。 本 skill 自包含：下面的全部规则就是权威，不依赖任何外部规范文档。 产出三件并经用户确认：① 一句话目标 ② in-scope / out-of-scope 列表 ③ 验收点。三者齐备才进阶段 1。 requires Vendor-specific API key. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “一、核心理念（红线，违反即返工） / PRD 即故事集 / 测试用例铁律（本 skill 新增核心，最容易写错，逐条记牢）” 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; may access external network resources; requires Vendor-specific API keys.

## Running Rules
- read files, write/modify files; may access external network resources; requires Vendor-specific API keys.
- 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 和测试用例。每一步关键进展必须获得用户明确认可。 本 skill 自包含：下面的全部规则就是权威，不依赖任何…
  • 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 即故事集”, “测试用例铁律（本 skill 新增核心，最容易写错，逐条记牢）”, “二、交互模型”, 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-test-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 即故事集 / 测试用例铁律（本 skill 新增核心，最容易写错，逐条记牢）” before expanding.

Boundaries And Review

  • Dependencies: Prepare Vendor-specific API keys before running a full 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.