CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
OpenPrd 需求入口与 PRD 分流 skill：判断用户可见需求类型和内部 L0/L1/L2 路由码，决定直接澄清、mini-plan 或正式 PRD，并选择通用 / 面向个人消费者场景 / 面向企业服务场景 / 以 Agent 为主要使用场景的 PRD 视角。对用户复述时不要直接把 consumer / b2b / agent 当展示词；这些枚举值只用于内部记录和命令。
Install Openprd Requirement Intake
$ npx skills add DavidLam-oss/obsidian-wechat-converter --skill openprd-requirement-intake -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install DavidLam-oss/obsidian-wechat-converter openprd-requirement-intake --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/DavidLam-oss/obsidian-wechat-converter.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/openprd-requirement-intake .claude/skills/openprd-requirement-intake && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "openprd-requirement-intake" agent skill from https://github.com/DavidLam-oss/obsidian-wechat-converter/tree/main/.codex/skills/openprd-requirement-intake into .claude/skills/openprd-requirement-intake/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openprd-requirement-intake", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/DavidLam-oss/obsidian-wechat-converter/tree/main/.codex/skills/openprd-requirement-intakeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add DavidLam-oss/obsidian-wechat-converter --skill openprd-requirement-intake -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install DavidLam-oss/obsidian-wechat-converter openprd-requirement-intake --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DavidLam-oss/obsidian-wechat-converter.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/openprd-requirement-intake .agents/skills/openprd-requirement-intake && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "openprd-requirement-intake" agent skill from https://github.com/DavidLam-oss/obsidian-wechat-converter/tree/main/.codex/skills/openprd-requirement-intake into .agents/skills/openprd-requirement-intake/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openprd-requirement-intake", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add DavidLam-oss/obsidian-wechat-converter --skill openprd-requirement-intake -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install DavidLam-oss/obsidian-wechat-converter openprd-requirement-intake --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DavidLam-oss/obsidian-wechat-converter.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/openprd-requirement-intake .cursor/skills/openprd-requirement-intake && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "openprd-requirement-intake" agent skill from https://github.com/DavidLam-oss/obsidian-wechat-converter/tree/main/.codex/skills/openprd-requirement-intake into .cursor/skills/openprd-requirement-intake/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openprd-requirement-intake", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/DavidLam-oss/obsidian-wechat-converter.git --path .codex/skills/openprd-requirement-intake--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add DavidLam-oss/obsidian-wechat-converter --skill openprd-requirement-intake -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install DavidLam-oss/obsidian-wechat-converter openprd-requirement-intake --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DavidLam-oss/obsidian-wechat-converter.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/openprd-requirement-intake .gemini/skills/openprd-requirement-intake && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "openprd-requirement-intake" agent skill from https://github.com/DavidLam-oss/obsidian-wechat-converter/tree/main/.codex/skills/openprd-requirement-intake into .gemini/skills/openprd-requirement-intake/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openprd-requirement-intake", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install DavidLam-oss/obsidian-wechat-converter openprd-requirement-intakeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add DavidLam-oss/obsidian-wechat-converter --skill openprd-requirement-intake -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/DavidLam-oss/obsidian-wechat-converter.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/openprd-requirement-intake .github/skills/openprd-requirement-intake && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "openprd-requirement-intake" agent skill from https://github.com/DavidLam-oss/obsidian-wechat-converter/tree/main/.codex/skills/openprd-requirement-intake into .github/skills/openprd-requirement-intake/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openprd-requirement-intake", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add DavidLam-oss/obsidian-wechat-converter --skill openprd-requirement-intake -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install DavidLam-oss/obsidian-wechat-converter openprd-requirement-intake --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DavidLam-oss/obsidian-wechat-converter.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/openprd-requirement-intake .opencode/skills/openprd-requirement-intake && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "openprd-requirement-intake" agent skill from https://github.com/DavidLam-oss/obsidian-wechat-converter/tree/main/.codex/skills/openprd-requirement-intake into .opencode/skills/openprd-requirement-intake/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openprd-requirement-intake", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
openprd-requirement-intake- GitHub stars
- 334
- Token cost
- ~1.5k tokens
- SKILL.md length
- 357 words
- Files
- 4 (incl. references)
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- MIT
At a glance
OpenPrd 需求入口与 PRD 分流 skill：判断用户可见需求类型和内部 L0/L1/L2 路由码，决定直接澄清、mini-plan 或正式 PRD，并选择通用 / 面向个人消费者场景 / 面向企业服务场景 / 以 Agent 为主要使用场景的 PRD 视角。对用户复述时不要直接把 consumer / b2b / agent 当展示词；这些枚举值只用于内部记录和命令。
- Works in 5 steps: 读取 .openprd/ 状态和 openprd run .… → 用 references/routing-rubric.md 判断… → 如果是 L2，读取… → …
- Tasks that involve PRD writing
- SKILL.md covers 作用, 分流原则, 工作流 and 输出合同, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Openprd Requirement Intake is an agent skill from DavidLam-oss/obsidian-wechat-converter. OpenPrd 需求入口与 PRD 分流 skill：判断用户可见需求类型和内部 L0/L1/L2 路由码，决定直接澄清、mini-plan 或正式 PRD，并选择通用 / 面向个人消费者场景 / 面向企业服务场景 / 以 Agent 为主要使用场景的 PRD 视角。对用户复述时不要直接把 consumer / b2b / agent 当展示词；这些枚举值只用于内部记录和命令。
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/prd-template-lenses.md`, `references/routing-rubric.md` and `references/startup-validation-lens.md`).
It sits in Product & Project Management, covering PRD writing. The repository describes itself as: Obsidian 公众号排版（支持自定义 CSS和公众号贴图）、飞书云同步与多平台（小红书、知乎等）发布插件。Markdown 转微信文章 / Feishu docs / 知乎、小红书、今日头条等草稿，支持数学公式、本地图片、GIF 和 Mermaid。 The licence is MIT.
When your agent uses it
- Tasks that involve PRD writing
Example prompts
- “/openprd-requirement-intake”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- 读取 .openprd/ 状态和 openprd run . --context，但把它当作建议。
- 用 references/routing-rubric.md 判断 L0/L1/L2。
- 如果是 L2，读取 references/prd-template-lenses.md 选择 PRD 场景视角。
- 输出一个短的需求类型判断
- 把执行交回 $openprd-harness。
What it can do on your machine
Read from SKILL.md and the folder at commit 3fef612. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Openprd Requirement Intake loads about 1.5k tokens when it runs, and up to ~5.7k if it reads all its reference files. Until then it costs about 54 tokens; SKILL.md has 357 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from DavidLam-oss/obsidian-wechat-converter at commit 3fef612, republished under its MIT licence (© DavidLam-oss). 357 words, ~1,461 tokens.
Download SKILL.mdSave it as
.claude/skills/openprd-requirement-intake/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- openprd-requirement-intake
- description
- OpenPrd 需求入口与 PRD 分流 skill：判断用户可见需求类型和内部 L0/L1/L2 路由码，决定直接澄清、mini-plan 或正式 PRD，并选择通用 / 面向个人消费者场景 / 面向企业服务场景 / 以 Agent 为主要使用场景的 PRD 视角。对用户复述时不要直接把 consumer / b2b / agent 当展示词；这些枚举值只用于内部记录和命令。
<!-- OPENPRD:GENERATED
adapter=codex
source=openprd-requirement-intake
version=0.1.19
checksum=3a481efa6bdd4b05
-->OpenPrd Requirement Intake
作用
这份 skill 只做需求入口分流，不负责实现代码。
- 判断当前用户输入的用户可见需求类型和内部 L0/L1/L2 路由码
- 决定下一步是直接澄清、mini-plan，还是正式 PRD
- 为 L2 选择通用、面向个人消费者场景、面向企业服务场景或以 Agent 为主要使用场景的 PRD 视角；
base/consumer/b2b/agent只用于内部记录和命令 - 把用户当前需求和历史 active change 分开，避免“继续任务”吞掉新范围
- 给
$openprd-harness输出下一步行动合同
分流原则
不要按关键词判断。按影响面、未知数、决策成本和验证成本判断。
如果用户明确说“帮我梳理下”“先想清楚”“进入脑暴模式”，或需求只有一句话但明显需要先收敛业务方向、用户、商业目标、竞品和复用能力，必须先进入脑暴模式，不要直接压进 PRD，也不要先拿一版 requirement 摘要代替脑暴产物。默认使用：
openprd brainstorm . --topic <当前主题> --open- 如需让 Agent 先提炼展示文案，再补
openprd brainstorm-presentation . --template
脑暴模式是独立 lane，不等于普通 clarify：
- 目的不是只补字段，而是先判断值不值得做、给谁做、为什么现在做、有哪些方向、当前工作区能复用什么。
- 每轮至少要把这几类关键点补齐：第一批最容易触达的社区或人群、你为什么算这个社区里的自己人、现在怎么解决、当前 workaround 到底有多痛、如果先不做完整产品怎么手工交付、能否先用 spreadsheet 或 no-code 跑起来、什么真实承诺最能证明不是口头兴趣、有没有 10 个样本和更强付费信号、达到什么条件才允许产品化、先怎么低成本验证、验证阶段怎样先活下来，以及什么情况下先停。
- 资料来源默认同时包含 benchmark、knowledge、当前工作区文档/代码和开放问题。
- 如果用户能提供更大的工作区或历史项目目录，优先一起扫描可复用能力、旧流程和已有产品做法。
- 用户没有明确要求时，Agent 只能“建议进入脑暴模式”，不能静默切换。
- 用户认可脑暴方向后，再回到
capture -> classify -> synthesize -> review -> change -> tasks。
| 用户可见需求类型 | 内部路由码 | 判断含义 | 默认处理方式 |
|---|---|---|---|
| 直接处理 | L0 | 单点、低风险、可逆、验收清楚 | 可以直接处理并事后说明 |
| 现有功能优化 | L1 | 目标明确，但影响多个文件、状态或用户可见行为 | 先给对话内 mini-plan，再执行 |
| 新功能/新流程方案 | L2 | 新产品、模块、入口、流程、权限、计费、账号、AI/第三方、云服务、数据迁移、跨系统、长期工作流，或目标/验收/影响面不清 | 先走 PRD/review/change/tasks |
用户审查时优先把路由码并进“需求类型：直接处理（L0）”这类标签里，不要把内部调度码单独抬成标题。只有审查或调试真的受益时，才额外补“内部路由码：L1”这类信息，并保留上面的对照关系。
用户侧表达优先使用“面向个人消费者场景 / 面向企业服务场景 / 以 Agent 为主要使用场景”这类自然语言，不要把 consumer、b2b、agent 直接当展示词抛给用户。
界面、页面、视觉、样式或前端体验需求需要额外判断 UI 影响面。若会明显改变信息架构、核心布局、主视觉、关键路径、组件层级/密度，或用户需要先选择设计方向，即使属于“现有功能优化”，也要先走“大界面改动视觉方案评审”：已有界面时用 Computer Use 截取当前产品内功能截图，冷启动没有现有界面时基于已确认 PRD、用户群体、第一版切片和视觉目标生成设计 brief；再用 imagegen（Codex 原生 Image 2）生成至少 3 个方向，横向拼接带 1/2/3 序号的大图给用户确认。
如果同一句话同时包含“继续旧任务”和“新增范围”，先判断新增范围是否超出旧 PRD。超出时必须回到需求入口，更新 PRD/change/tasks，不能把“继续”当作实现授权。
工作流
- 读取
.openprd/状态和openprd run . --context，但把它当作建议。 - 用
references/routing-rubric.md判断 L0/L1/L2。 - 如果是 L2，读取
references/prd-template-lenses.md选择 PRD 场景视角。 - 输出一个短的需求类型判断：
- 先总后分，优先按下面结构在对话里给用户看：
- 需求判断：需求类型（默认写成
直接处理（L0）/现有功能优化（L1）/新功能/新流程方案（L2））/ 产品类型 / 推荐下一步 - 只有内部排障真的受益时，才额外补一行“内部路由码”
- 需求理解：主要服务对象 / 使用场景 / 第一版先做什么 / 这轮先不做什么 / 必须守住什么
需求判断和需求理解先用 1 到 2 句轻量主句说清“这次是什么 / 核心问题是什么 / 第一版先做到什么”；能一句话说清就不要写两句话。范围边界、风险边界、异常例子和技术细节下沉到后面的分项或表格，不要全塞进同一整段长话里。- 如果需求理解里同时出现多个角色、路径、状态、前后对比、风险传播或取舍关系，优先补一张解释型 SVG 图来承载结构；图后只保留必要结论、开放问题和下一步。
- 这里沉淀的是表达风格，不是固定示例文案；要根据本次内容自适应生成，不要机械套同一句模板。
- 功能范围：优先用 Markdown 表格写
功能模块 | 这次先做什么 | 这次先不做什么 - 技术方案：优先用 Markdown 表格写
技术部分 | 初步方案 | 主要负责什么；涉及前端、后端、Agent、数据或集成时，按用户能看懂的功能视角拆开 - L2 时补充 PRD 场景视角：通用场景 / 面向个人消费者场景 / 面向企业服务场景 / 以 Agent 为主要使用场景
- 把执行交回
$openprd-harness。
输出合同
L0
- 直接处理或问 1 个必要问题。
- 不生成 PRD。
- 完成后说明变更和验证。
L1
- 给 3-5 行 mini-plan。
- 明确范围内、范围外和验证方式。
- 默认先用业务/产品语言复述需求，再只追问 1 个最高价值问题；不要上来抛技术字段墙。
- 若是大界面改动，mini-plan 之后先做 3 方向效果图评审，用户确认方向后再实现。
- 用户已明确要求执行时可继续实现。
- 不生成正式 PRD，除非 mini-plan 暴露出新的决策缺口。
Show full SKILL.md (144 more words)Show less
L2
- 如果用户明确要梳理、先想清楚、进入脑暴模式，或这句话明显还需要先收敛业务方向，先运行或建议
openprd brainstorm . --topic <当前主题> --open，不要只在对话里先给一版 requirement 摘要代替脑暴模式。 - 进入脑暴模式后，Agent 默认先用“创业验证透镜”追问和收口：第一批可触达社区/种子用户、你为什么算这个社区里的自己人、当前替代方案和痛点强度、手工交付路径、手工作战卡、一件事 MVP、周末级验证、能否先用 spreadsheet / 表单 / no-code 跑起来、如果必须开始做产品也只自动化最重复的一步并先压成 forms / lists / CRUD 骨架、第一批客户路径、初始收费假设、客户 1 盈利路径、10 个样本和付费验证信号、达到什么条件才允许产品化、default alive 约束、增长纪律、可逆性、客户真问题判断和价值观一致性（是不是你愿意长期住进去的业务形态），再补核心诉求、推荐方向、关键角色和复用基础。
- 进入脑暴模式后，至少要形成
brainstorm.html这类可继续评审和推进的产物，再基于产物追问或收口。 - 其他 L2 默认先运行或建议
openprd clarify .。 - 先建立首轮项目画像：用户群体、产品形态、第一版切片、暂不处理、不能破坏和风险探针。
- 对话内 requirement 摘要除了常规的用户、范围、风险，还要主动抬出“第一批最容易先找谁验证、你为什么算这个社区里的自己人、用户现在怎么解决、这个 workaround 到底有多痛、先怎么手工交付、手工作战卡怎么写、第一版只做哪一件事、能不能压成周末级 MVP、能不能先用 spreadsheet / 表单 / no-code 跑起来、如果必须开始做产品也只自动化最重复的一步并先压成 forms / lists / CRUD 骨架、第一批客户路径、从第一个客户开始怎么收费、客户 1 如何打平成本、有没有 10 个样本和更强付费信号、达到什么条件才允许产品化、增长阶段守什么纪律、验证阶段怎样先活下来，以及这条路是否可逆、是否真在解决客户问题、是否符合团队价值观、是不是你愿意长期住进去的业务形态”。
- 再用对话内结构化摘要确认需求，默认按“需求判断 / 需求理解 / 功能范围 / 技术方案”的顺序来写，其中“功能范围”和“技术方案”优先用 Markdown 表格。
需求判断和需求理解先轻后重：先用轻量主句给用户一个一眼能懂的结论，再把边界、风险和技术细项下沉到后续表格或分项里；不要把它们揉成一大段说明。- 如果 L2 摘要正在解释新流程、新角色关系、状态机、前后方案差异、依赖边界或失败恢复路径，先用解释型 SVG 图降低理解成本，再用表格承接范围和技术分工。
- 优先由 Agent 先归纳，再请用户确认；默认先问 1 个最高价值问题，必要时再给 2 到 3 个方向和取舍供用户选，不要一次砸一整墙问题。
- 当前还是 L2 的首轮澄清或 requirement 摘要确认阶段时，只能承诺“我先整理需求摘要给你确认”；不要写成“你回我一句我就开始实现”，也不要把 requirement 摘要确认、review 和实现压成一句话。
- 单纯的“请帮我实现/继续实现”只表示用户希望最终落地，不表示可以跳过 requirement 摘要确认、
capture/classify/synthesize写入路径或 review；只有用户明确表示“不需要进行任何确认”时，才允许静默走完整 requirement write path。 - 用户侧表达优先使用业务和产品语言，强调谁在什么场景下解决什么问题、会获得什么收益、要承担什么业务风险；避免过早暴露前端/后端/数据库这类技术黑话。
- 使用
openprd capture . --field ...只写回已确认事实；agent-normalized仅用于无语义变化的内部措辞整理，不替代用户确认。 - 选择并记录产品类型：
openprd classify . <consumer|b2b|agent>；无法判断时保持base。 - requirement 摘要确认后，再进入
openprd classify .、openprd synthesize .、review artifact、change 和 tasks。
PRD 场景视角
base：通用产品或工程场景，强调问题、目标、首轮项目画像、范围、流程、需求矩阵、验收和风险。- 内部
consumer：面向个人消费者场景，强调用户旅程、首次成功、激活、留存、情绪价值和增长指标。 - 内部
b2b：面向企业服务场景，强调买方/使用者/管理员/运营者、权限矩阵、审批审计、集成依赖、SLA 和上线支持。 - 内部
agent：以 Agent 为主要使用场景，强调 Human-Agent contract、自主边界、工具边界、状态模型、失败恢复和评估计划。
模板视角应融入正文结构，不要作为 PRD 末尾的字段附录。比如企业服务场景的角色、权限和审批应该贯穿用户、流程、需求矩阵和验收标准；Agent 场景的自主边界应该贯穿范围、风险、任务和验证。
何时读取参考
- 分流有争议、用户输入很长、或涉及“继续旧任务 + 新范围”时，读
references/routing-rubric.md。 - 需要写 PRD、选择产品场景、或用户反馈 PRD 结构奇怪时，读
references/prd-template-lenses.md。 - 需要把 L2 或脑暴收口成更强的创业验证链时，读
references/startup-validation-lens.md。
© DavidLam-oss, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references) in .codex/skills/openprd-requirement-intake of DavidLam-oss/obsidian-wechat-converter.
- SKILL.md
- references/prd-template-lenses.md
- references/routing-rubric.md
- references/startup-validation-lens.md
Open the folder on GitHubat commit 3fef612
Compare with similar skills
Openprd Requirement Intake next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Openprd Requirement Intake this skillDavidLam-oss/obsidian-wechat-converter | 334 | — | ~1.5k | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Ralph Tui Create Beadssubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Trellis Brainstormanjiemo/SunnyBeach | 178 | 7 repos | ~4k | Automated safety check: Pass | Apache-2.0 | |
| Ralph Tui Create Beads Rustsubsy/ralph-tui | 2.5k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Ralph Tui Create JSONsubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT |
Similar skills
Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
Trellis Brainstorm
anjiemo/SunnyBeach
Guides collaborative requirements discovery before implementation.
Ralph Tui Create Beads Rust
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).
Ralph Tui Create JSON
subsy/ralph-tui
Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.
Prd Generator
jamesrochabrun/skills
Generate comprehensive Product Requirements Documents (PRDs) for product managers.
More from DavidLam-oss/obsidian-wechat-converter
All 14 skills in this repoOpenprd UI Context
DavidLam-oss/obsidian-wechat-converter
OpenPrd UI Context skill：区分 greenfield、brownfield 与局部修正，基于已确认 PRD、可选 CodeGraph 和本地证据提出专业 UI/UX 方向，并在用户确认后编译 PRODUCT.md、DESIGN.md 和 Impeccable handoff。
Wechat AI Layout
DavidLam-oss/obsidian-wechat-converter
为 Obsidian 微信公众号转换器生成受约束的 AI 编排结果。只在需要把文章内容映射为公众号安全 block JSON、诊断编排结果、优化 layout schema、分析 fallback 介入原因时使用。遇到教程、案例、产品介绍、截图型内容时应优先考虑这个 skill。
Openprd Test Strategy
DavidLam-oss/obsidian-wechat-converter
OpenPrd 测试策略分流 skill：按风险把任务分到单元、集成、端到端、人工、视觉、小程序、性能和安全验证，并要求 evidence-plan。
Project Release
DavidLam-oss/obsidian-wechat-converter
Release workflow for obsidian-wechat-converter (version bump, release notes, tag and publish).
Openprd Diagram Review
DavidLam-oss/obsidian-wechat-converter
生成并迭代 OpenPrd 图示产物，供用户确认或理解。适用于解释型 SVG、架构图、产品流程图、用户旅程、流程图、系统边界图、依赖图，以及 freeze 前的可视化评审场景。
Openprd Frontend Design
DavidLam-oss/obsidian-wechat-converter
OpenPrd 前端设计框架 skill：为界面、页面、视觉、样式和前端体验任务提供设计资产框架、审美立意、反 AI 味门禁和实现前方向评审规则。
Related
Categories
Questions about Openprd Requirement Intake
What does Openprd Requirement Intake do?
OpenPrd 需求入口与 PRD 分流 skill：判断用户可见需求类型和内部 L0/L1/L2 路由码，决定直接澄清、mini-plan 或正式 PRD，并选择通用 / 面向个人消费者场景 / 面向企业服务场景 / 以 Agent 为主要使用场景的 PRD 视角。对用户复述时不要直接把 consumer / b2b / agent 当展示词；这些枚举值只用于内部记录和命令。. Openprd Requirement Intake is an agent skill from DavidLam-oss/obsidian-wechat-converter.
When should I use Openprd Requirement Intake?
Openprd Requirement Intake fits situations like: tasks that involve PRD writing.
How do I install Openprd Requirement Intake in Claude Code?
Run `npx skills add DavidLam-oss/obsidian-wechat-converter --skill openprd-requirement-intake -a claude-code`. Or copy the skill folder (.codex/skills/openprd-requirement-intake in DavidLam-oss/obsidian-wechat-converter) into .claude/skills/openprd-requirement-intake in your project. Claude Code loads it when a task matches its description.
How do I install Openprd Requirement Intake in Codex?
Run `npx skills add DavidLam-oss/obsidian-wechat-converter --skill openprd-requirement-intake -a codex`. Or copy the skill folder (.codex/skills/openprd-requirement-intake in DavidLam-oss/obsidian-wechat-converter) into .agents/skills/openprd-requirement-intake in your project. Codex loads it when a task matches its description.
Can I use Openprd Requirement Intake in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add DavidLam-oss/obsidian-wechat-converter --skill openprd-requirement-intake -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/openprd-requirement-intake, .gemini/skills/openprd-requirement-intake, .github/skills/openprd-requirement-intake and .opencode/skills/openprd-requirement-intake in your project.
What does Openprd Requirement Intake need to run?
SKILL.md names no scripts, command-line tools or credentials: Openprd Requirement Intake is instructions for the agent only.
Does Openprd Requirement Intake access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Openprd Requirement Intake safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Openprd Requirement Intake use?
Openprd Requirement Intake is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Openprd Requirement Intake use?
About 1.5k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.3k tokens, read only when the agent opens those files.
What are the alternatives to Openprd Requirement Intake?
Skills that share tags, products or a category with Openprd Requirement Intake: CCPM Project Management (automazeio/ccpm, 8.4k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Trellis Brainstorm (anjiemo/SunnyBeach, 178 stars) and Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Openprd Requirement Intake?
DavidLam-oss (a GitHub user) maintains it in DavidLam-oss/obsidian-wechat-converter, which has 334 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 9, 2026.
Source: DavidLam-oss/obsidian-wechat-converter on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.