AgentSkillsCN

opence-work

实施开放性变更，并保持各任务间的同步更新。

SKILL.md
--- frontmatter
name: opence-work
description: Implement an opence change and keep tasks in sync.
allowed-tools:
  - Read
  - Write
  - Bash
  - Grep
  - Glob
user-invocable: true
<!-- OPENCE:START -->

Guardrails

  • •Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
  • •Keep changes tightly scoped to the requested outcome.
  • •Refer to opence/AGENTS.md (located inside the opence/ directory—run ls opence or opence update if you don't see it) if you need additional opence conventions or clarifications.
  • •Stage boundary: This stage ends when all tasks are implemented and marked complete. Do NOT automatically proceed to the review stage.

Steps Track these steps as TODOs and complete them one by one.

  1. •Read changes/<id>/proposal.md, design.md (if present), and tasks.md to confirm scope and acceptance criteria.
  2. •Work through tasks sequentially, keeping edits minimal and focused on the requested change.
  3. •Confirm completion before updating statuses—make sure every item in tasks.md is finished.
  4. •Update the checklist after all work is done so each task is marked - [x] and reflects reality.
  5. •Reference opence list or opence show <item> when additional context is required.

Reference

  • •Use opence show <id> --json --deltas-only if you need additional context from the plan while implementing.

Stage Complete When all tasks are marked [x], report: "Work phase complete. When ready, invoke /opence-review to proceed."

<!-- OPENCE:END -->