Orkas Orkas
Repository-aware product engineering 理解仓库的产品研发

ProductDeveloper Turn a clear requirement into a focused, verified code change. 把明确需求落成聚焦且可验证的代码改动。

ProductDeveloper reads supplied PRDs, issues, bug reports, designs, and repository rules; builds a compact map of the real code path; plans the smallest safe change; implements, tests, debugs, and reviews it; then delivers an auditable handoff with exact evidence and remaining risk. ProductDeveloper 会读取 PRD、issue、bug 报告、设计稿和仓库规则,建立真实代码路径的紧凑地图,规划最小安全改动,完成实现、测试、调试和复审,并交付包含确切证据与剩余风险的可审计说明。

  • Repository rules first 先读仓库规则
  • Acceptance mapped to evidence 验收逐项映射证据
  • Final diff reviewed again 最终 Diff 再审一遍
PD Feature delivery 功能交付

Implement the onboarding checklist from PRD.md. Preserve existing users, add the analytics contract, and cover the first-use and resume journeys. 根据 PRD.md 实现新手引导清单,保持现有用户行为,补充分析契约,并覆盖首次使用和恢复流程。

Focused diff 聚焦改动 3 files
src/onboarding/checklist.ts
18 const progress = loadProgress(userId);
19 + const next = resumeVisibleStep(progress);
20 + emitOnboardingResult(next);
21 return renderChecklist(next);
Acceptance evidence 验收证据 review complete
First-use journey 首次使用流程 Focused product test passed 聚焦产品测试通过 pass
Resume without duplication 恢复时不重复 State and event checks passed 状态与事件检查通过 pass
Contract classification 识别工程契约 Distinguishes feature, bug, refactor, review, performance, technical decision, CI repair, and finite input work. 区分功能、bug、重构、评审、性能、技术决策、CI 修复和有限输入任务。
Compact repository map 紧凑仓库地图 Reads instructions, symbols, callers, boundaries, tests, and CI without broad speculative scanning. 读取指令、符号、调用者、边界、测试和 CI,不做无边界扫描。
Smallest safe change 最小安全改动 Connects every accepted behavior to a concrete file and evidence path before implementation. 实现前把每项验收行为映射到具体文件和证据路径。
Auditable handoff 可审计交付 Reports scope, decisions, changed files, checks, pre-existing failures, unverified paths, and remaining risk. 报告范围、决策、变更文件、检查、既有失败、未验证路径和剩余风险。
Usage example 使用示例

From an Orkas landing-page requirement to a verified repository change. 从 Orkas 落地页需求到经验证的仓库改动。

YOU Development request 研发需求
“Add crawlable pages for Commander and nine official Agents. Reuse the public chrome, keep one download CTA, support bilingual raw HTML and 320 px mobile, register both sitemaps, and add deterministic regression coverage.” “为指挥官和 9 个官方 Agent 增加可抓取页面。复用公共顶部栏,保留单一下载 CTA,支持中英文原始 HTML 与 320px 移动端,注册两份 sitemap,并增加确定性回归测试。”
Web/ agent-specs/ public chrome contract acceptance matrix
Repository change · Web official Agents仓库改动 · Web 官方 Agentsverified已验证
11public routes公开路由1 hub + 10 detail pages
1shared system共享系统agents.css
0competing CTAs竞争 CTAhero + final
CHANGED FILESWeb/agents/agents.cssWeb/agents/*/index.htmlWeb/home.htmlWeb/seo/{global,cn}/Server/test/...PC/test/e2e/...
Web/agents/agents.css
+ .agent-subnav { /* shared */ }+ [data-case-artifact] { ... }+ @media (max-width: 620px) { ... } /* one implementation, ten consumers */
Acceptance验收项Evidence证据State状态
Every Agent is discoverable每个 Agent 都可被发现hub + 2 sitemapsPASS
One download path单一下载路径static inventoryPASS
Chinese at 320 px320px 中文页面Electron browserPASS
✓ 8 static checks✓ 2 E2E journeys✓ 0 page errors✓ final diff reviewed
focused diffacceptance matrixtest logsrisk notes
Engineering work 工程工作

Implement, repair, refactor, review, and investigate. 实现、修复、重构、评审和排查。

01

Feature delivery 功能开发

Turn accepted product behavior into focused changes, engineering tests, compatibility checks, and evidence-backed completion. 把已接受的产品行为落成聚焦改动、工程测试、兼容性检查和证据型完成。

  • PRD implementation
  • architecture decision
  • migration and rollback
02

Bug and CI repair Bug 与 CI 修复

Reproduce the first failure, state one falsifiable hypothesis, run the smallest disproof check, and fix the root cause. 复现首个失败,提出一个可证伪假设,用最小检查验证,并修复根因。

  • bug reproduction
  • test repair
  • CI/build repair
03

Refactor and review 重构与代码评审

Preserve invariants, inspect callers and consumers, identify risks, and return prioritized evidence or a safe focused change. 保持不变量,检查调用者和消费者,识别风险,交付优先级清晰的证据或安全聚焦改动。

  • code review
  • performance investigation
  • technical spike
How it works 工作方式

Map the real path, change narrowly, verify independently. 梳理真实路径、缩小改动范围、独立验证结果。

01

Read the contract 读取工程契约

Read every supplied requirement, issue, design, bug report, and relevant attachment. 读取所有需求、issue、设计、bug 报告和相关附件。

02

Map the repository 梳理仓库

Locate instructions, modules, callers, data boundaries, tests, and verification commands. 定位规则、模块、调用者、数据边界、测试和验证命令。

03

Implement the smallest change 实施最小改动

Baseline, edit coherently, inspect impacted callers, and run cheap focused checks first. 建立基线、完成一致改动、复查受影响调用者,并先运行低成本聚焦检查。

04

Verify and review again 验证并再次复审

Expand verification by risk, inspect every log, review the final diff, and report residual gaps. 按风险扩展验证、检查全部日志、复审最终 Diff,并报告残余缺口。

Engineering boundaries 工程边界

Clear product behavior is the starting point; vague discovery is not silently converted into code. 明确产品行为才进入研发;模糊探索不会被悄悄变成代码。

Product decisions stay with the product owner 产品决策仍由产品负责人决定

If a missing choice materially changes the experience and cannot be discovered from code, ProductDeveloper asks the smallest question instead of inventing an MVP. 缺失选择会实质改变体验且无法从代码发现时,只询问最小必要问题,不擅自发明 MVP。

User changes are preserved 保护用户已有改动

Modified paths are treated as user-owned; no reset, discard, stage, commit, push, or publish occurs without matching authority. 已修改路径视为用户所有;没有对应授权不会重置、丢弃、暂存、提交、推送或发布。

Verification limits remain explicit 验证限制保持明确

Unavailable services, blocked checks, flaky results, and unverified paths are reported rather than presented as production-ready. 不可用服务、受阻检查、波动结果和未验证路径会明确报告,不包装成生产就绪。

Works with the team 团队协作

Move from research and UI direction to verified engineering delivery. 从研究和 UI 方向继续推进到经验证的工程交付。

Commander can coordinate the product path 指挥官可以协调产品落地路径

UIDesigner can produce the interface artifact, DeepResearcher can ground technical or market facts, and ProductDeveloper can implement the accepted behavior in the real repository. UIDesigner 产出界面设计,DeepResearcher 夯实技术或市场事实,ProductDeveloper 在真实仓库实现已接受行为。

Start directly with a clear engineering request 需求明确时可直接开始研发

Provide the development task and optional project path. Repository instructions and relevant attachments are discovered before editing. 提供研发任务和可选项目路径;编辑前会发现仓库规则和相关附件。

Turn the next accepted requirement into verified code. 把下一个已明确需求落成经验证的代码。

Download Orkas and give ProductDeveloper a PRD, issue, bug report, design, refactor, review, or CI failure. 下载 Orkas,把 PRD、issue、bug 报告、设计、重构、评审或 CI 失败交给 ProductDeveloper。

Repository-aware · Focused changes · Evidence-backed handoff 理解仓库 · 聚焦改动 · 证据型交付