opence-plan — community opence-plan, opence, community, ide skills

v1.0.0
GitHub

About this Skill

Perfect for Developer Agents requiring streamlined development processes with minimal implementations Create an opence plan and scaffold change artifacts.

mufengbufeng mufengbufeng
[0]
[0]
Updated: 3/12/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
23
Canonical Locale
en
Detected Body Locale
en

Perfect for Developer Agents requiring streamlined development processes with minimal implementations Create an opence plan and scaffold change artifacts.

Core Value

Empowers agents to implement straightforward solutions first, adding complexity only when necessary, utilizing guardrails and referring to opence conventions for clarity, ensuring tightly scoped changes and minimal ambiguity

Ideal Agent Persona

Perfect for Developer Agents requiring streamlined development processes with minimal implementations

↓ Capabilities Granted for opence-plan

Implementing minimal viable products
Refining existing codebases for simplicity
Developing new features with tightly scoped changes

! Prerequisites & Limits

  • Requires adherence to opence conventions
  • Favors minimal implementations over complex solutions

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is opence-plan?

Perfect for Developer Agents requiring streamlined development processes with minimal implementations Create an opence plan and scaffold change artifacts.

How do I install opence-plan?

Run the command: npx killer-skills add mufengbufeng/opence/opence-plan. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for opence-plan?

Key use cases include: Implementing minimal viable products, Refining existing codebases for simplicity, Developing new features with tightly scoped changes.

Which IDEs are compatible with opence-plan?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for opence-plan?

Requires adherence to opence conventions. Favors minimal implementations over complex solutions.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add mufengbufeng/opence/opence-plan. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use opence-plan immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

opence-plan

Install opence-plan, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence
<!-- 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.
  • Identify any vague or ambiguous details and ask the necessary follow-up questions before editing files.
  • Do not write any code during the planning stage. Only create design documents (proposal.md, tasks.md, design.md, and spec deltas). Implementation happens in the work stage after approval.

Steps

  1. Review opence/project.md, run opence list and opence list --specs, and inspect related code or docs (e.g., via rg/ls) to ground the plan in current behaviour; note any gaps that require clarification.
  2. Choose a unique verb-led change-id and scaffold proposal.md, tasks.md, and design.md (when needed) under opence/changes/<id>/.
  3. Map the change into concrete capabilities or requirements, breaking multi-scope efforts into distinct spec deltas with clear relationships and sequencing.
  4. Capture architectural reasoning in design.md when the solution spans multiple systems, introduces new patterns, or demands trade-off discussion before committing to specs.
  5. Draft spec deltas in changes/<id>/specs/<capability>/spec.md (one folder per capability) using ## ADDED|MODIFIED|REMOVED Requirements with at least one #### Scenario: per requirement and cross-reference related capabilities when relevant.
  6. Draft tasks.md as an ordered list of small, verifiable work items that deliver user-visible progress, include validation (tests, tooling), and highlight dependencies or parallelizable work.
  7. Validate with opence validate <id> --strict and resolve every issue before sharing the plan.

Reference

  • Use opence show <id> --json --deltas-only or opence show <spec> --type spec to inspect details when validation fails.
  • Search existing requirements with rg -n "Requirement:|Scenario:" opence/specs before writing new ones.
  • Explore the codebase with rg <keyword>, ls, or direct file reads so plans align with current implementation realities.
<!-- OPENCE:END -->

Related Skills

Looking for an alternative to opence-plan or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

The React Framework

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Developer