diff --git a/.agents/skills/unidesk-oa/SKILL.md b/.agents/skills/unidesk-oa/SKILL.md index 2b7312d3..061a151d 100644 --- a/.agents/skills/unidesk-oa/SKILL.md +++ b/.agents/skills/unidesk-oa/SKILL.md @@ -24,10 +24,11 @@ Use this skill to keep HWLAB Cloud M1 project management centered on a stable ma ## Canonical HWLAB Issue Anchors -- L0 master specification: `pikasTech/HWLAB#1194` (`HWLAB 总项目规格（L0）：云端硬件研发平台总控`). +- L0 master specification: `PJ2026-01`, `pikasTech/HWLAB#1194` (`HWLAB 总项目规格（L0）：云端硬件研发平台总控`). - Long-term navigation board: `pikasTech/HWLAB#645` (`HWLAB 长期总面板`). This is a board, not the specification. - Current Cloud M1 phase specification: `pikasTech/HWLAB#644` (`HWLAB Cloud SPEC / 云平台开发目标 20260601`). This is a phase spec, not an L1 direction. - When creating or updating HWLAB project-management issues, link nontrivial L1/L2/L3/L4 work back to `#1194` and keep `#645` as a navigation index only. +- Use the HWLAB hierarchy code on all management issues and specs: project codes use `PJ-`: `PJ` means project, `2026` is the establishment year, HWLAB L0 is `PJ2026-01`; L1 codes are `PJ2026-0101`, `PJ2026-0102`, ...; L2 codes append two digits, e.g. `PJ2026-010102` means HWLAB L1 #01, L2 #02. Continue appending two digits per deeper level. ## Workflow diff --git a/.agents/skills/unidesk-oa/references/project-planning.md b/.agents/skills/unidesk-oa/references/project-planning.md index 450fe896..662ed995 100644 --- a/.agents/skills/unidesk-oa/references/project-planning.md +++ b/.agents/skills/unidesk-oa/references/project-planning.md @@ -4,11 +4,11 @@ HWLAB Cloud M1 needs a project control structure that prevents local issue/PR work from drifting away from the center. Use a research-project style hierarchy: -- Major project: overall mission, product goal, delivery boundary. -- Direction: stable capability domain under the major project that directly serves the L0 mission. -- Topic: concrete program of work inside a direction. -- Subtopic: bounded validation slice with explicit acceptance criteria. -- Execution task: issue, PR, CaseRun, smoke, deployment, or document closeout. +- Major project: overall mission, product goal, delivery boundary (`PJ2026-01` for HWLAB). +- Direction: stable capability domain under the major project that directly serves the L0 mission (`PJ2026-0101`, `PJ2026-0102`, ...). +- Topic: concrete program of work inside a direction (`PJ2026-010102` means HWLAB L1 #01 / L2 #02). +- Subtopic: bounded validation slice with explicit acceptance criteria, appending another two digits. +- Execution task: issue, PR, CaseRun, smoke, deployment, or document closeout, appending another two digits when it needs a persistent management code. ## Document And Issue Split @@ -33,11 +33,20 @@ Do not store the only copy of a stable requirement in an issue comment. If the r ## Current HWLAB Issue Anchors -- L0 master specification: `pikasTech/HWLAB#1194` (`HWLAB 总项目规格（L0）：云端硬件研发平台总控`). +- L0 master specification: `PJ2026-01`, `pikasTech/HWLAB#1194` (`HWLAB 总项目规格（L0）：云端硬件研发平台总控`). - Long-term board/navigation: `pikasTech/HWLAB#645` (`HWLAB 长期总面板`). Do not treat this as the specification. - Cloud M1 phase specification: `pikasTech/HWLAB#644` (`HWLAB Cloud SPEC / 云平台开发目标 20260601`). This is a phase spec, not an L1 direction. - New or updated direction/topic/execution issues should include `上级总项目: #1194` unless the user explicitly scopes the task outside HWLAB Cloud M1. +## Numbering Rule + +- HWLAB L0 project code is `PJ2026-01`: `PJ` means project, `2026` is the establishment year, and `01` is the HWLAB L0 sequence. +- L1 direction codes are `PJ2026-0101`, `PJ2026-0102`, `PJ2026-0103`, ... +- L2 topic codes append the L2 two-digit sequence after the L1 code payload: `PJ2026-010101`, `PJ2026-010102`, `PJ2026-010201`, ... +- L3/L4 persistent management codes continue appending two digits per level, e.g. `PJ2026-01010203` = HWLAB L1 #01 / L2 #02 / L3 #03. +- Do not renumber existing codes just because priorities change. Add new suffixes for new durable nodes; execution-only PRs or one-off smokes may reference the nearest persistent code instead of receiving their own code. +- Issue titles should start with the code when the issue is a durable L0/L1/L2/L3 management node, e.g. `PJ2026-010102 PLC 71-FREQ AO ioProbe 造模`. + ## Suggested HWLabOA Structure For HWLAB Cloud M1, keep the durable docs under: @@ -72,7 +81,7 @@ The L0 item defines: - Issue hierarchy index. - Drift indicators. -There should normally be one L0 GitHub issue and one L0 master spec document. For HWLAB, the canonical L0 issue is `pikasTech/HWLAB#1194`; `#645` remains only the long-term board/navigation entry. +There should normally be one L0 GitHub issue and one L0 master spec document. For HWLAB, the canonical L0 code is `PJ2026-01` and the canonical L0 issue is `pikasTech/HWLAB#1194`; `#645` remains only the long-term board/navigation entry. ### L1 Direction @@ -95,12 +104,12 @@ Do not use any of these as L1 directions: Typical HWLAB Cloud M1 directions: -- Cloud AI hardware-development workflow: user request, workspace, Code Agent implementation, review, collaboration, delivery. -- Real hardware access and auditable validation loop: target device, debug probe, io probe, CaseRun, low-noise evidence. -- Multi-user cloud service and commercial metering: auth, API keys, credit, usage ledger, billing, admin operations. -- Execution substrate and resource orchestration: AgentRun/HWPOD/Code Agent runtime assembly, sessions, provider profiles, bundles, recovery. -- Capability accumulation, training feedback, and quality control: harness cases, failure taxonomy, review, reusable templates, model/tool improvement. -- User product surface and collaboration experience: Web/CLI/API workflows that expose the above capabilities to users. +- `PJ2026-0101` Cloud AI hardware-development workflow: user request, workspace, Code Agent implementation, review, collaboration, delivery. +- `PJ2026-0102` Real hardware access and auditable validation loop: target device, debug probe, io probe, CaseRun, low-noise evidence. +- `PJ2026-0103` Multi-user cloud service and commercial metering: auth, API keys, credit, usage ledger, billing, admin operations. +- `PJ2026-0104` Execution substrate and resource orchestration: AgentRun/HWPOD/Code Agent runtime assembly, sessions, provider profiles, bundles, recovery. +- `PJ2026-0105` Capability accumulation, training feedback, and quality control: harness cases, failure taxonomy, review, reusable templates, model/tool improvement. +- `PJ2026-0106` User product surface and collaboration experience: Web/CLI/API workflows that expose the above capabilities to users. ### L2 Topic diff --git a/.agents/skills/unidesk-oa/references/templates.md b/.agents/skills/unidesk-oa/references/templates.md index bc0aba97..cd297402 100644 --- a/.agents/skills/unidesk-oa/references/templates.md +++ b/.agents/skills/unidesk-oa/references/templates.md @@ -5,6 +5,8 @@ ```markdown # HWLAB Cloud M1 Master Specification +编号: PJ2026-01 + ## 1. Mission One paragraph describing the product and research objective. @@ -23,12 +25,12 @@ One paragraph describing the product and research objective. | Level | Title | GitHub issue | Spec section | Current status | | --- | --- | --- | --- | --- | -| L1 | Cloud AI hardware-development workflow | TBD | ... | ... | -| L1 | Real hardware access and auditable validation loop | TBD | ... | ... | -| L1 | Multi-user cloud service and commercial metering | TBD | ... | ... | -| L1 | Execution substrate and resource orchestration | TBD | ... | ... | -| L1 | Capability accumulation, training feedback, and quality control | TBD | ... | ... | -| L1 | User product surface and collaboration experience | TBD | ... | ... | +| L1 | PJ2026-0101 Cloud AI hardware-development workflow | TBD | ... | ... | +| L1 | PJ2026-0102 Real hardware access and auditable validation loop | TBD | ... | ... | +| L1 | PJ2026-0103 Multi-user cloud service and commercial metering | TBD | ... | ... | +| L1 | PJ2026-0104 Execution substrate and resource orchestration | TBD | ... | ... | +| L1 | PJ2026-0105 Capability accumulation, training feedback, and quality control | TBD | ... | ... | +| L1 | PJ2026-0106 User product surface and collaboration experience | TBD | ... | ... | ## 5. Global Acceptance Criteria @@ -67,6 +69,7 @@ One paragraph describing the product and research objective. 目标合并分支: 不适用 原因: 本 issue 是 HWLAB Cloud M1 总项目管理锚点，代码变更由下级 issue/PR 承载。 +编号: PJ2026-01 上级面板: #645 当前 L0 总规格: #1194 总规格文档: @@ -79,12 +82,14 @@ One paragraph describing the product and research objective. ## L1 方向 -- [ ] #... 方向A: -- [ ] #... 方向B: -- [ ] #... 方向C: +- [ ] PJ2026-0101 #... 方向A: +- [ ] PJ2026-0102 #... 方向B: +- [ ] PJ2026-0103 #... 方向C: 方向判定: L1 必须是直接服务 L0 的能力域；文档整理、项目管理、看板维护、skill 维护、仓库名、工具名和临时执行路径不得作为 L1。 +编号规则: 项目编号格式为 PJ<立项年份>-<层级路径>；PJ 表示项目，HWLAB L0 为 PJ2026-01；L1 为 PJ2026-0101；L2 继续追加两位，例如 PJ2026-010102 表示 HWLAB L1 第 1 个方向下的第 2 个 L2 课题；更深层级继续每级追加两位。 + ## 全局验收 - ... @@ -107,6 +112,7 @@ One paragraph describing the product and research objective. 目标合并分支: 不适用 原因: 本 issue 是方向级项目管理锚点，代码变更由下级 topic/subtopic issue 承载。 +编号: PJ2026-010N 上级总项目: #1194 总规格文档: @@ -144,6 +150,7 @@ One paragraph describing the product and research objective. ```markdown 目标合并分支: +编号: PJ2026-010N0M 上级总项目: #1194 所属方向: #... 所属课题: #...