mirrors/pikasTech-unidesk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: allow eight-character oa short names

Browse Source
This commit is contained in:
Codex
2026-06-14 04:43:25 +00:00
parent 23daca5a24
commit f208e3afcf
3 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.agents/skills/unidesk-oa/SKILL.md
+1 -1
View File
@@ -28,7 +28,7 @@ Use this skill to keep HWLAB Cloud M1 project management centered on a stable ma
- 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<YYYY>-<path>`: `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. Durable node short names should usually be no more than 5 Chinese characters; put explanations in descriptions, not names.
- Use the HWLAB hierarchy code on all management issues and specs: project codes use `PJ<YYYY>-<path>`: `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. Durable node short names should usually be no more than 8 Chinese characters; put explanations in descriptions, not names.
## Workflow
.agents/skills/unidesk-oa/references/project-planning.md
+1 -1
View File
@@ -45,7 +45,7 @@ Do not store the only copy of a stable requirement in an issue comment. If the r
- 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.
- Durable node short names should usually be no more than 5 Chinese characters. Issue titles should start with the code and short name, e.g. `PJ2026-010102 频源造模`; put detailed explanations in the body.
- Durable node short names should usually be no more than 8 Chinese characters. Issue titles should start with the code and short name, e.g. `PJ2026-010102 频源造模`; put detailed explanations in the body.
## Suggested HWLabOA Structure
.agents/skills/unidesk-oa/references/templates.md
+3 -3
View File
@@ -90,7 +90,7 @@ One paragraph describing the product and research objective.
方向判定: L1 必须是直接服务 L0 的能力域；文档整理、项目管理、看板维护、skill 维护、仓库名、工具名和临时执行路径不得作为 L1。
编号规则: 项目编号格式为 PJ<立项年份>-<层级路径>；PJ 表示项目，HWLAB L0 为 PJ2026-01；L1 为 PJ2026-0101；L2 继续追加两位，例如 PJ2026-010102 表示 HWLAB L1 第 1 个方向下的第 2 个 L2 课题；更深层级继续每级追加两位。短名一般控制在 5 个中文汉字以内，解释写入正文说明。
编号规则: 项目编号格式为 PJ<立项年份>-<层级路径>；PJ 表示项目，HWLAB L0 为 PJ2026-01；L1 为 PJ2026-0101；L2 继续追加两位，例如 PJ2026-010102 表示 HWLAB L1 第 1 个方向下的第 2 个 L2 课题；更深层级继续每级追加两位。短名一般控制在 8 个中文汉字以内，解释写入正文说明。
## 全局验收
@@ -115,7 +115,7 @@ One paragraph describing the product and research objective.
原因: 本 issue 是方向级项目管理锚点，代码变更由下级 topic/subtopic issue 承载。
编号: PJ2026-010N
短名: <5字以内>
短名: <8字以内>
上级总项目: #1194
总规格文档: <HWLabOA path or GitHub URL>
@@ -154,7 +154,7 @@ One paragraph describing the product and research objective.
目标合并分支: <repo branch/lane>
编号: PJ2026-010N0M
短名: <5字以内>
短名: <8字以内>
上级总项目: #1194
所属方向: #...
所属课题: #...