openprd-router
An entry point for routing OpenPrd tasks to the correct harness, design, or testing workflows.
Install
mkdir -p .claude/skills/openprd-router && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17260" && unzip -o skill.zip -d .claude/skills/openprd-router && rm skill.zipInstalls to .claude/skills/openprd-router
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
OpenPrd 入口路由 skill：先判断当前任务该读哪个 skill、哪个命令面和哪个门禁。Key capabilities
- →Determine execution mode for tasks
- →Route tasks to appropriate OpenPrd skills
- →Prioritize user intent for brainstorming or direct implementation
- →Read command catalogs for specific commands
- →Apply shared constraints and main workflow rules
How it works
The skill acts as an entry router for OpenPrd, determining the execution mode, selecting the relevant skill, and prioritizing user intent. It reads command catalogs and applies shared constraints and main workflow rules.
Inputs & outputs
When to use openprd-router
- →Starting an OpenPrd maintenance task
- →Routing UI tasks to frontend-design
- →Determining execution modes for automation
About this skill
OpenPrd Router
把这份 skill 当成 OpenPrd 的入口路由，而不是长文规则仓库。
先做什么
- 先判断 executionMode。Codex automation、Claude Code headless、cron、scheduled、unattended task 这类无人值守自动化默认进入 automation-safe mode：不要运行
openprd run . --context，不要注入 OpenPrd context，不要求openprd dev-check/quality/doctor，按该自动化自己的 runbook、日志、测试和通知合同收口。 - 只有 automation prompt 或环境明确写明“这是 OpenPrd 维护任务”“显式启用 OpenPrd / enable OpenPrd / openprd-maintenance”时，才在自动化里恢复 OpenPrd 工作流。
- 如果用户当前明确在说“帮我梳理下”“先想清楚”“进入脑暴模式”，先读
$openprd-requirement-intake，并优先运行openprd run . --context --message <用户原话>；需要时直接进入openprd brainstorm . --open，不要只跑不带 message 的openprd run . --context。 - 其他互动场景再读
.openprd/当前状态，并把openprd run . --context当作纯读取的建议上下文，而不是自动执行指令；只有 hook/调用方确实要记录本次上下文使用时，才显式加--record-context。 - 如果当前是空白工作区的前端/页面冷启动，而且用户已经给了明确的页面主题、模块范围或“直接实现”的意图，优先改用
openprd run . --context --message <用户原话>；不要先跑不带 message 的openprd run . --context，再被空白工作区自己的clarify-user带偏。 - 需要具体命令时，优先读取
.openprd/harness/command-catalog.md，不要把命令清单继续塞回AGENTS.md。 - 需要共用约束时，读
$openprd-shared；需要主工作流时，读$openprd-harness。 - 任务涉及界面、页面、视觉、样式、信息架构、内容型页面或前端体验时，先读取
$openprd-frontend-design；新界面、结构性 UI 改造、设计系统或 Impeccable handoff 再读取$openprd-ui-context。局部低风险修正使用 UI Context 的local-fix路径。 - 如果这类空白前端任务在带 message 的前提下仍短暂返回
clarify-user，但用户原话已经明确要求直接实现单页/首页/原型，就把它当成摘要级提醒；先用 3 到 5 行 mini-plan 收口，再按 frontend design 的design-starter -> Patch Mode路径继续，不要回到长澄清或模板源码漫游。
路由表
- 需求入口分流、用户可见需求类型与内部 L0/L1/L2 路由码对照、PRD 场景视角选择：
$openprd-requirement-intake - 主工作流、review/change/tasks、
run/loop：$openprd-harness - 前端设计框架、审美资产库、主题/骨架/组件/配方/模板、事实与素材前置门：
$openprd-frontend-design - 项目双路径理解、专业 UI/UX 方向、PRODUCT.md/DESIGN.md 与 Impeccable 交接：
$openprd-ui-context - 测试策略分流、分层验证和任务级 evidence-plan：
$openprd-test-strategy - 最佳实践、benchmark、公开 GitHub 仓库、第三方技术事实、prompt/context engineering：
$openprd-benchmark-router docs/basic/、文件说明书、文件夹 README、文档标准：$openprd-standards- 就绪验证、EVO 门禁、HTML 质量评估报告、项目经验沉淀：
$openprd-quality - 架构图、产品流程图、解释型 SVG、可视化评审、大界面改动效果图方案评审：
$openprd-diagram-review与$openprd-harness - 长时间只读挖掘、参考项目持续调研、requirements/specs/tasks 补全：
$openprd-discovery-loop - 学习包、归档阅读器、知识整理：
$openprd-learning-review
路由原则
AGENTS.md只保留轻量入口合同；详细规则放进 repo-local skills、.openprd/harness/command-catalog.md和 hooks。- 公开 GitHub 仓库架构/对标先 DeepWiki；第三方库、API、SDK、MCP、CLI 用法先查本地证据，本地不足时再按
resolve_library_id -> query_docs使用 Context7。 - hooks 已经强制处理 requirement / research / secrets / skill-visualization / weapp / browser / copy 这些门禁；不要再把它们膨胀回
AGENTS.md静态长文。 - 用户原话里已经明确要求“先梳理/脑暴”时，用户意图优先于不带 message 的默认 run context；先把原话带进
openprd run . --context --message ...，或直接进入脑暴模式。 - 不要用固定关键词决定是否写 PRD，也不要用词表决定工具；先让
$openprd-requirement-intake按影响面、未知数、决策成本和验证成本做语义分流，再按用户目标、期望产物、交付阶段和证据缺口选择学习器、视觉评审或质量收口工具。 - 当用户需要理解状态跳转、因果链、方案差异、边界分工或风险传播时，先读
$openprd-diagram-review，优先用轻量解释型 SVG 辅助说明；不要把它误升级成正式评审图或视觉验收图。 - 不要用“需求大小”机械决定测试层级；先让
$openprd-test-strategy按风险、触达面、失败后果和证据成本分流。
When not to use it
- →When automation prompt or environment does not explicitly enable OpenPrd maintenance
- →When the user expects a long rule repository instead of a router
Limitations
- →The skill only restores OpenPrd workflow in automation when explicitly enabled.
- →The skill prioritizes user intent for brainstorming or direct implementation.
- →The skill reads `.openprd/harness/command-catalog.md` for specific commands.
How it compares
This skill functions as a dynamic entry point, routing tasks based on context and user intent, which is more adaptive than a static rule repository for determining task execution.
Compared to similar skills
openprd-router side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| openprd-router (this skill) | 0 | 20d | No flags | Intermediate |
| agent-migration-plan | 1 | 5mo | No flags | Advanced |
| oh-my-ccg-plan | 0 | 5mo | No flags | Advanced |
| value-stream-mapping | 0 | 6mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
agent-migration-plan
ruvnet
Agent skill for migration-plan - invoke with $agent-migration-plan
oh-my-ccg-plan
1molchuan
RPI 计划阶段 — 约束集转化为零决策可执行计划
value-stream-mapping
Prorise-cool
Lean value stream mapping for identifying waste and optimization opportunities. Creates current/future state maps with cycle time analysis and improvement recommendations.
trello
openclaw
Manage Trello boards, lists, and cards via the Trello REST API.
create-plan
antinomyhq
Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.
project-planner
adrianpuiu
Comprehensive project planning and documentation generator for software projects. Creates structured requirements documents, system design documents, and task breakdown plans with implementation tracking. Use when starting a new project, defining specifications, creating technical designs, or breaking down complex systems into implementable tasks. Supports user story format, acceptance criteria, component design, API specifications, and hierarchical task decomposition with requirement traceability.