From 371ab30eeaa011615d0bd482812492aa0aa30517 Mon Sep 17 00:00:00 2001 From: SepComet <202308010230@stu.csust.edu.cn> Date: Sat, 28 Mar 2026 09:48:53 +0800 Subject: [PATCH] =?UTF-8?q?=E5=B0=86=20openspec=20skills=20=E8=BF=81?= =?UTF-8?q?=E7=A7=BB=E5=88=B0=E5=85=A8=E5=B1=80=20+=20=E5=AE=9A=E4=B9=89?= =?UTF-8?q?=E5=90=8E=E7=BB=AD=20proto=20=E7=B1=BB=E5=9E=8B?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .codex/skills/openspec-apply-change/SKILL.md | 156 --- .../skills/openspec-archive-change/SKILL.md | 114 -- .../openspec-bulk-archive-change/SKILL.md | 246 ---- .../skills/openspec-continue-change/SKILL.md | 118 -- .codex/skills/openspec-explore/SKILL.md | 288 ----- .codex/skills/openspec-ff-change/SKILL.md | 101 -- .codex/skills/openspec-new-change/SKILL.md | 74 -- .codex/skills/openspec-onboard/SKILL.md | 554 --------- .codex/skills/openspec-propose/SKILL.md | 110 -- .codex/skills/openspec-sync-specs/SKILL.md | 138 --- .codex/skills/openspec-verify-change/SKILL.md | 168 --- Assets/Scripts/MovementComponent.cs | 39 +- Assets/Scripts/Network/Defines/Message.cs | 1087 +++++++++++++++-- Assets/Scripts/Network/Defines/MessageType.cs | 23 +- Assets/Scripts/Network/Defines/message.proto | 85 ++ .../Network/Defines/message.proto.meta | 7 + .../ClientPredictionBuffer.cs | 12 +- .../DefaultMessageDeliveryPolicyResolver.cs | 4 +- .../NetworkApplication/SyncSequenceTracker.cs | 7 +- Assets/Scripts/NetworkManager.cs | 19 +- .../EditMode/Network/MessageManagerTests.cs | 126 +- .../Network/SharedNetworkFoundationTests.cs | 16 +- .../EditMode/Network/SyncStrategyTests.cs | 24 +- MobaSyncMVP.md | 14 +- TODO.md | 92 +- .../.openspec.yaml | 2 + .../design.md | 66 + .../proposal.md | 26 + .../specs/kcp-transport/spec.md | 14 + .../network-gameplay-message-types/spec.md | 17 + .../specs/network-sync-strategy/spec.md | 45 + .../specs/shared-network-foundation/spec.md | 19 + .../tasks.md | 19 + openspec/specs/kcp-transport/spec.md | 12 +- .../network-gameplay-message-types/spec.md | 17 + openspec/specs/network-sync-strategy/spec.md | 36 +- .../specs/shared-network-foundation/spec.md | 7 +- 37 files changed, 1560 insertions(+), 2342 deletions(-) delete mode 100644 .codex/skills/openspec-apply-change/SKILL.md delete mode 100644 .codex/skills/openspec-archive-change/SKILL.md delete mode 100644 .codex/skills/openspec-bulk-archive-change/SKILL.md delete mode 100644 .codex/skills/openspec-continue-change/SKILL.md delete mode 100644 .codex/skills/openspec-explore/SKILL.md delete mode 100644 .codex/skills/openspec-ff-change/SKILL.md delete mode 100644 .codex/skills/openspec-new-change/SKILL.md delete mode 100644 .codex/skills/openspec-onboard/SKILL.md delete mode 100644 .codex/skills/openspec-propose/SKILL.md delete mode 100644 .codex/skills/openspec-sync-specs/SKILL.md delete mode 100644 .codex/skills/openspec-verify-change/SKILL.md create mode 100644 Assets/Scripts/Network/Defines/message.proto create mode 100644 Assets/Scripts/Network/Defines/message.proto.meta create mode 100644 openspec/changes/archive/2026-03-28-split-network-message-types/.openspec.yaml create mode 100644 openspec/changes/archive/2026-03-28-split-network-message-types/design.md create mode 100644 openspec/changes/archive/2026-03-28-split-network-message-types/proposal.md create mode 100644 openspec/changes/archive/2026-03-28-split-network-message-types/specs/kcp-transport/spec.md create mode 100644 openspec/changes/archive/2026-03-28-split-network-message-types/specs/network-gameplay-message-types/spec.md create mode 100644 openspec/changes/archive/2026-03-28-split-network-message-types/specs/network-sync-strategy/spec.md create mode 100644 openspec/changes/archive/2026-03-28-split-network-message-types/specs/shared-network-foundation/spec.md create mode 100644 openspec/changes/archive/2026-03-28-split-network-message-types/tasks.md create mode 100644 openspec/specs/network-gameplay-message-types/spec.md diff --git a/.codex/skills/openspec-apply-change/SKILL.md b/.codex/skills/openspec-apply-change/SKILL.md deleted file mode 100644 index d474dc1..0000000 --- a/.codex/skills/openspec-apply-change/SKILL.md +++ /dev/null @@ -1,156 +0,0 @@ ---- -name: openspec-apply-change -description: Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks. -license: MIT -compatibility: Requires openspec CLI. -metadata: - author: openspec - version: "1.0" - generatedBy: "1.2.0" ---- - -Implement tasks from an OpenSpec change. - -**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes. - -**Steps** - -1. **Select the change** - - If a name is provided, use it. Otherwise: - - Infer from conversation context if the user mentioned a change - - Auto-select if only one active change exists - - If ambiguous, run `openspec list --json` to get available changes and use the **AskUserQuestion tool** to let the user select - - Always announce: "Using change: " and how to override (e.g., `/opsx:apply `). - -2. **Check status to understand the schema** - ```bash - openspec status --change "" --json - ``` - Parse the JSON to understand: - - `schemaName`: The workflow being used (e.g., "spec-driven") - - Which artifact contains the tasks (typically "tasks" for spec-driven, check status for others) - -3. **Get apply instructions** - - ```bash - openspec instructions apply --change "" --json - ``` - - This returns: - - Context file paths (varies by schema - could be proposal/specs/design/tasks or spec/tests/implementation/docs) - - Progress (total, complete, remaining) - - Task list with status - - Dynamic instruction based on current state - - **Handle states:** - - If `state: "blocked"` (missing artifacts): show message, suggest using openspec-continue-change - - If `state: "all_done"`: congratulate, suggest archive - - Otherwise: proceed to implementation - -4. **Read context files** - - Read the files listed in `contextFiles` from the apply instructions output. - The files depend on the schema being used: - - **spec-driven**: proposal, specs, design, tasks - - Other schemas: follow the contextFiles from CLI output - -5. **Show current progress** - - Display: - - Schema being used - - Progress: "N/M tasks complete" - - Remaining tasks overview - - Dynamic instruction from CLI - -6. **Implement tasks (loop until done or blocked)** - - For each pending task: - - Show which task is being worked on - - Make the code changes required - - Keep changes minimal and focused - - Mark task complete in the tasks file: `- [ ]` → `- [x]` - - Continue to next task - - **Pause if:** - - Task is unclear → ask for clarification - - Implementation reveals a design issue → suggest updating artifacts - - Error or blocker encountered → report and wait for guidance - - User interrupts - -7. **On completion or pause, show status** - - Display: - - Tasks completed this session - - Overall progress: "N/M tasks complete" - - If all done: suggest archive - - If paused: explain why and wait for guidance - -**Output During Implementation** - -``` -## Implementing: (schema: ) - -Working on task 3/7: -[...implementation happening...] -✓ Task complete - -Working on task 4/7: -[...implementation happening...] -✓ Task complete -``` - -**Output On Completion** - -``` -## Implementation Complete - -**Change:** -**Schema:** -**Progress:** 7/7 tasks complete ✓ - -### Completed This Session -- [x] Task 1 -- [x] Task 2 -... - -All tasks complete! Ready to archive this change. -``` - -**Output On Pause (Issue Encountered)** - -``` -## Implementation Paused - -**Change:** -**Schema:** -**Progress:** 4/7 tasks complete - -### Issue Encountered - - -**Options:** -1.