Start from a PRD, requirement, issue, bug report, or approved design. ProductDeveloper maps the repository, makes the smallest coherent change, and proves each accepted behavior with current tests, review, or measured results.Comece com PRD, requisito, issue, bug ou design aprovado. O ProductDeveloper mapeia o repositório, faz a menor mudança coerente e comprova cada comportamento com testes, revisão ou medições atuais. 从 PRD、需求、issue、bug 报告或确认过的设计出发。ProductDeveloper 会先建立仓库地图，完成最小但完整的改动，再用本次测试、审查或实测结果证明每项已确认行为。 PRD、要件、issue、バグ報告、承認済みデザインから開始。ProductDeveloper はリポジトリを把握し、最小で一貫した変更を行い、今回のテスト・レビュー・測定で各条件を検証します。
Key takeaways核心要点要点Pontos-chaveProductDeveloper maps the repository, keeps the change focused, and ties each accepted behavior to current engineering evidence.
Trace each requirement to the relevant code path, implement the smallest coherent change, and verify the accepted behavior.
Reproduce the failure, find the root cause, repair the code or test, and rerun the checks that prove the fix.
Improve structure without widening the patch, then review architecture, compatibility, migration, and rollback risk.
Profile the relevant path, test the proposed change, and report measured impact plus any remaining uncertainty.
You provide the PRD or issue. ProductDeveloper maps the code path, implements the focused change, and returns evidence for every accepted behavior.
Start from a PRD, issue, bug report, design, or explicit acceptance criteria.
Identify the relevant code paths, tests, constraints, and risk before editing.
Keep the patch coherent and avoid unrelated cleanup that makes review harder.
Return tests, review evidence, measured results, and clearly marked unverified items.
The repo, configs, and KB stay on disk by default; enabled model and connector services receive the data needed for their calls.
The task keeps explicit scope, acceptance criteria, compatibility concerns, and rollback risk visible.
A claim is marked verified only when supported by a current test, review, or measured result.
See security →Feature implementation, bug and CI repair, test repair, focused refactors, code review, and performance debugging from a PRD, requirement, issue, bug report, or design.Implementação de funcionalidades, correção de bugs, CI e testes, refatorações focadas, revisão de código e análise de desempenho a partir de PRD, requisito, issue, bug ou design. 从 PRD、需求、issue、bug 报告或设计稿出发，完成功能开发、bug 与 CI/测试修复、聚焦重构、代码评审和性能排查。 PRD、要件、issue、バグ報告、デザインから、機能実装、バグ・CI・テスト修正、焦点を絞ったリファクタ、レビュー、性能調査に対応します。
Each accepted behavior is mapped to a current targeted test, review result, or measured performance result. Anything not verified is explicitly marked instead of being presented as complete.Cada comportamento aceito é ligado a um teste atual, resultado de revisão ou medição. O que não foi validado fica marcado explicitamente. 每项已确认行为都会对应到本次针对性测试、审查结果或实测性能数据；仍未验证的内容会明确标注，不会包装成已完成。 各条件を今回のテスト、レビュー、性能測定に対応させ、未検証の項目は完了扱いせず明示します。
It maps the relevant repository paths before editing, keeps the patch focused, and reports architecture, compatibility, migration, and rollback concerns for review.Ele mapeia os caminhos relevantes antes de editar, mantém o patch focado e informa riscos de arquitetura, compatibilidade, migração e rollback. 动手前先建立相关仓库路径地图，保持补丁聚焦，并把架构、兼容性、迁移和回滚风险留给你审查。 編集前に関連経路を把握し、パッチを絞り、設計・互換性・移行・ロールバックの懸念を報告します。
Use optional Orkas-managed official models or connect OpenAI, Anthropic Claude, Google Gemini, and other providers through OAuth or an API key. Calls using your own provider go directly to it.Use modelos oficiais gerenciados pelo Orkas ou conecte OpenAI, Anthropic Claude, Google Gemini e outros por OAuth ou chave de API. Chamadas ao seu provedor vão direto para ele. 可使用 Orkas 托管的官方模型，或通过 OAuth/API Key 接入 OpenAI、Anthropic Claude、Google Gemini 等供应商；自有供应商调用会直接发给对应服务。 Orkas 管理の公式モデル、または OAuth/API キーで OpenAI、Anthropic Claude、Google Gemini などを利用できます。自分のプロバイダーへの呼び出しは直接送信されます。
Free, open source, runs on your machine.
