PRD
归档记录,不对外
# (EN) PRD Authoring Prompt
You are senior product manager, your goal is to create a comprehensive Product Requirements Document (PRD) based on the following instructions:
<prd_instructions>
{PROJECT_DESCRIPTION} <-- Include the full PROJECT_DESCRIPTION here -->
</prd_instructions>
Follow these steps to create your PRD
1. Begin with a brief introduction stating the purpose of the document.
2. Organize your PRD into the following sections:
<prd_outline>
# Title
## 1. Title and Overview
### 1.1 Document Title & Version
### 1.2 Product Summary
## 2. User Personas
### 2.1 Key User Types
### 2.2 Basic Persona Details
## 3. Role-based Access
### 3.1 Briefly describe each user role (e.g., Admin, Registered User, Guest) and the main features/permissions available to that role.
## 4. User Stories
</prd_outline>
3. For each section, provide detailed and relevant information based on the PRD instructions. Ensure that you:
- Use clean and concise language
- Provide specific details and metrics where required
- Maintain consistency throughout the document
- Address all points mentioned in each section
4. When creating user stories and acceptance criteria:
- LIST ALL necessary user stories including primary, alternative, and edge-case scenarios.
- Assign a unique requirement ID (e.g., US-001) to each user story for direct traceability
- Include at least one user story specifically for secure access or authentication if the application requires user identification or access restrictions
- Ensure no potential user interaction is omitted
- Make sure each user story is testable
<user_story>
- ID
- Title
- Description
- Acceptance Criteria
</user_story>
5. After completing the PRD, review it against this Final CheckList:
- Is each user story testable?
- Are acceptance criteria clear and specific?
- Do we have enough user stories to build a fully functional application for it?
- Have we addressed authentication and authorization requirements (if applicable)?
6. Format your PRD:
- Maintain consistent formatting and numbering.
- Don't format text in markdown bold "**", we don't need this.
- List ALL User Stories in the output!
- Format the PRD in valid Markdown, with no extraneous disclaimers.
# (ZH)PRD 编写提示
你是一名资深产品经理,你的目标是根据以下指令撰写一份完善的《产品需求文档(PRD)》:
<prd_instructions>
{PROJECT_DESCRIPTION} ← 在此粘贴完整的 PROJECT_DESCRIPTION
</prd_instructions>
按以下步骤创建你的 PRD:
1. 先用简短的引言说明本文档的目的。
2. 将 PRD 组织为以下章节:
<prd_outline>
# 标题
## 1. 标题与概览
### 1.1 文档标题与版本
### 1.2 产品摘要
## 2. 用户画像
### 2.1 关键用户类型
### 2.2 基本画像信息
## 3. 基于角色的访问
### 3.1 简要描述每个用户角色(如管理员、注册用户、访客)及该角色可用的主要功能/权限。
## 4. 用户故事
</prd_outline>
3. 针对每个章节,依据 PRD 指令提供详尽且相关的信息,并确保:
- 使用清晰简洁的语言
- 需要时提供具体细节与指标
- 保持整份文档的一致性
- 覆盖该章节提到的所有要点
4. 在编写用户故事与验收标准时:
- **列出所有**必要的用户故事,包括主路径、备选路径与边界情景
- 为每个用户故事分配**唯一需求 ID**(如 US-001),以便直接追溯
- 若应用需要用户身份识别或访问限制,至少包含**一个**与**安全访问/认证**相关的用户故事
- 确保不遗漏任何可能的用户交互
- 确保每个用户故事**可被测试**
<user_story>
- ID(编号)
- Title(标题)
- Description(描述)
- Acceptance Criteria(验收标准)
</user_story>
5. 完成 PRD 后,按以下**最终检查清单**复核:
- 每个用户故事都可测试吗?
- 验收标准是否清晰且具体?
- 是否具备足够的用户故事来构建一个**可完整运行**的应用?
- 是否已经处理认证与授权需求(如适用)?
6. PRD 格式要求:
- 保持一致的排版与编号
- **不要**使用 Markdown 加粗 “**”,不需要
- 在输出中**列出全部用户故事**
- 以**合法的 Markdown** 格式呈现 PRD,**不要**额外添加免责声明
思路梳理
-
统一前置条件与环境:Node.js、npm、权限、TTY 下操作。
-
Claude Code(SiliconFlow)部分:安装 + 设置 settings.json + apiKeyHelper,跳过 /login。
-
Codex CLI:官方安装,用 npm;启动后会弹网页授权。
-
Gemini CLI:官方安装,用 npm;首次启动 OAuth 登录,后续可用 API key。
-
补充说明:权限、授权后续(token 保存)、TTY 注意事项等。
# 1) 写入 apiKeyHelper(官方支持字段)
mkdir -p ~/.claude
cat > ~/.claude/anthropic_key.sh <<'SH'
#!/usr/bin/env sh
printf "%s" "sk-arjqhheuumlersmtiuxopjklxqjmoarzdekgwayrdjssjnyk"
SH
chmod +x ~/.claude/anthropic_key.sh
# 2) 合并你的 settings.json(保留 env;新增 apiKeyHelper)
cat > ~/.claude/settings.json <<'JSON'
{
"env": {
"ANTHROPIC_BASE_URL": "https://api.siliconflow.cn/",
"ANTHROPIC_MODEL": "zai-org/GLM-4.5",
"ANTHROPIC_API_KEY": "sk-arjqhheuumlersmtiuxopjklxqjmoarzdekgwayrdjssjnyk"
},
"apiKeyHelper": "~/.claude/anthropic_key.sh"
}
JSON
# 3) 重新登录 shell 让配置接管
exec bash -l
# 4) 用“真 TTY”启动(不要 heredoc/管道)
claude
# 在 Claude 的提示符里手动敲:
# /status (回车后再按一次Enter退出状态页)
# write a file named PING.txt that contains: PONG