技能项目
- 作者仓库星标 3,406
- 作者仓库 claude-octopus
- 领域
- 文档
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @nyldn · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
第 4 阶段:保存
写入用户指定的文件名或根据功能名称生成。现在从第 0 阶段澄清问题开始。
> **Host: Codex CLI** — This skill was designed for Claude Code and adapted for Codex.
> Cross-reference commands use installed skill names in Codex rather than `/octo:*` slash commands.
> Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it.
> For host tool equivalents, see `skills/blocks/codex-host-adapter.md`.
# STOP - SKILL ALREADY LOADED
**DO NOT call Skill() again. DO NOT load any more skills. Execute directly.**
## PHASE 0: CLARIFICATION (MANDATORY)
Before writing ANY PRD content, you MUST ask the user these questions:
```
I need to understand your requirements before creating the PRD.
1. **Target Users**: Who will use this? (developers, end-users, admins, etc.)
2. **Core Problem**: What specific pain point does this solve? Any metrics?
3. **Success Criteria**: How will you measure if this succeeds?
4. **Constraints**: Any technical, budget, or timeline constraints?
5. **Existing Context**: Is this greenfield or integrating with existing systems?
Please answer these (even briefly) so I can create a more targeted PRD.
```
**WAIT for user response before proceeding to Phase 1.**
If user says "skip" or provides the feature description inline, extract what you can and note assumptions.
## PHASE 1: QUICK RESEARCH (Max 2 searches)
Only search if topic is unfamiliar. Limit to 2 web searches max:
- One for domain/market context
- One for technical patterns (if needed)
Do NOT over-research. 60 seconds max for this phase.
## PHASE 2: WRITE PRD
Structure:
1. **Executive Summary** - Vision + key value prop
2. **Problem Statement** - Quantified pain points by user segment
3. **Goals & Metrics** - SMART goals, P0/P1/P2 priority, success metrics table
4. **Non-Goals** - Explicit boundaries (what we WON'T do)
5. **User Personas** - 2-3 specific personas with use cases
6. **Functional Requirements** - FR-001 format with acceptance criteria
7. **Implementation Phases** - Dependency-ordered, time-boxed
8. **Risks & Mitigations** - Top 3-5 risks with mitigation strategies
## PHASE 2.5: ADVERSARIAL PRD REVIEW (RECOMMENDED)
**After drafting the PRD but BEFORE self-scoring, dispatch the draft to a second provider for adversarial review.** A single-model PRD has blind spots — cross-provider challenge surfaces wrong assumptions, uncovered scenarios, and contradictory requirements.
Dispatch the PRD draft to a different provider (Codex, Gemini, or Sonnet as fallback) with this prompt:
> "Challenge this PRD. What assumptions are wrong? What user scenarios are missing? What requirements contradict each other? What will the first user complaint be? What risk does this PRD ignore?"
**After receiving the challenge:**
- Revise the PRD to address valid challenges
- Note dismissed challenges in the Risks section if they have partial merit
- Add to PRD footer: `Adversarial review: applied`
**Skip with `--fast` or when user requests speed over thoroughness.** See `prd.md` command for full dispatch syntax.
## PHASE 3: SELF-SCORE
Score against 100-point framework:
- AI-Specific Optimization: 25 pts (sequential phases, non-goals, structured format)
- Traditional PRD Core: 25 pts (problem statement, goals, personas, specs)
- Implementation Clarity: 30 pts (FRs with codes, NFRs, architecture, phases)
- Completeness: 20 pts (risks, dependencies, examples, doc quality)
## PHASE 4: SAVE
Write to user-specified filename or generate based on feature name.
**START WITH PHASE 0 CLARIFICATION QUESTIONS NOW.**
章节与文件索引
按说明文件中的顺序排列。
第 0 阶段:澄清(强制性)
第 1 阶段:快速研究(最多 2 次搜索)
第 2 阶段:编写 PRD
第 2.5 阶段:对抗性 PRD 审查(推荐)
第 3 阶段:自我评分
文件/命令 -> /octo:* · skills/blocks/codex-host-adapter.md · Adversarial review: applied · --fast · prd.md
内容校验值 -> 590aacc52722
当前原文的自动摘译,尚未人工审校。
第 0 阶段:澄清(强制性)
在编写任何 PRD 内容之前,您必须询问用户以下问题: 在进入第 1 阶段之前等待用户响应。如果用户说“跳过”或内联提供功能描述,请提取您可以提取的内容并记下假设。
第 1 阶段:快速研究(最多 2 次搜索)
仅在主题不熟悉时才搜索。最多限制 2 次网络搜索: 一项用于领域/市场背景 一项用于技术模式(如果需要) 不要过度研究。此阶段最多 60 秒。
第 2 阶段:编写 PRD
结构: 执行摘要 - 愿景 + 关键价值支柱 问题陈述 - 按用户细分量化痛点 目标和指标 - SMART 目标、P0/P1/P2 优先级、成功指标表 非目标 - 明确的边界(我们不会做的事情)
第 2.5 阶段:对抗性 PRD 审查(推荐)
起草 PRD 后但在自我评分之前,将草稿发送给第二个提供商进行对抗性审查。单一模型 PRD 存在盲点——跨提供商的挑战会带来错误的假设、未发现的场景和矛盾的需求。将 PRD 草案发送给不同的提供商(Codex、Gemini 或 Sonnet 作为后备),并提示:“挑战此 PRD。哪些假设是错误的?缺少哪些用户场景?哪些要求相互矛盾?第一个用户投诉是什么?此 PRD 忽略了哪些风险?”
第 3 阶段:自我评分
根据 100 分框架得分: AI 特定优化:25 分(顺序阶段、非目标、结构化格式) 传统 PRD 核心:25 分(问题陈述、目标、人物角色、规格) 实施清晰度:30 分(带有代码的 FR、NFR、架构、阶段) 完整性:20 分(风险、依赖性、示例、文档质量)