Agent skill
opence-compound
Document learnings, capture repeatable workflows as skills, and prepare to compound an opence change.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/development/opence-compound
Metadata
Additional technical details for this skill
- short description
- Document learnings, capture skills, and archive.
SKILL.md
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 theopence/directory—runls openceoropence updateif you don't see it) if you need additional opence conventions or clarifications.
Steps
- Determine the change ID:
- If this prompt already includes a specific change ID (for example inside a
<ChangeId>block populated by slash-command arguments), use that value after trimming whitespace. - If the conversation references a change loosely, run
opence listto surface likely IDs, share the relevant candidates, and confirm which one the user intends. - Otherwise, ask the user which change to compound and wait for a confirmed change ID before proceeding.
- If this prompt already includes a specific change ID (for example inside a
- Create a documentation entry under
docs/solutions/summarizing the problem, root cause, and fix. - Skill memory checkpoint:
- If the change revealed a repeatable workflow, recurring pitfalls, or manual checks, create or update a skill to encode it.
- Consult the
opence-skill-creatorskill for guidance on skill structure, naming, and best practices. - Use
opence skill add <skill-name> --description "..."to create new skills; the command automatically creates proper structure in all configured tool directories. - After creation, edit the SKILL.md file to add detailed instructions, examples, and guidelines.
- Move extensive documentation to
references/and reusable code toscripts/as described in skill-creator skill.
- After documentation and any skill updates are complete, consult the
opence-archiveskill to finalize the change. The skill provides guidance on pre-archive verification, runningopence archive <change-id>, and post-archive verification.
Reference
- Use
opence listto confirm change IDs before documenting. - Use
opence skill listto see existing skills and avoid duplicates. - Keep documentation concise and focused on future reuse.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?