Skip to content

About

Reusable project context for OpenSpec. Openspec has no global context setting, so this ships one and applies it per project.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

1 Commit

Folders and files

Repository files navigation

openspec-context

OpenSpec injects context from openspec/config.yaml into every artifact's instructions. There is no global setting for it (Fission-AI/OpenSpec#835), so standing conventions have to be re-added to every new project.

This plugin ships a reusable context block and a skill that applies it, plus an optional shell wrapper that does it automatically after openspec init.

Default context

The shipped block is the rule text from two agent-behavior plugins, reproduced verbatim so artifacts follow the same conventions those plugins enforce in chat:

  • caveman — terse prose. Cuts articles, filler, hedging; keeps technical substance exact.
  • ponytail — minimal-solution engineering. YAGNI, stdlib before custom code, shortest diff that works.

Neither plugin is a dependency — the text is self-contained, so this works whether or not you run them. Installing them alongside is the point, though: they hold the same line during implementation, where openspec's context does not yet reach.

Sections that only govern chat behavior (mode switching, intensity levels, tool-call narration) are omitted, and one rule is added: never compress artifact structure, so openspec validate keeps passing. Swap the whole thing out if your conventions differ — see Customize.

Install

/plugin marketplace add phantom-signals/openspec-context

Then, in any project with an openspec/ directory:

/openspec-context

The skill appends the block to openspec/config.yaml if the file has no context: key, and offers to install the shell wrapper.

Customize

skills/openspec-context/context.yaml is the whole payload — one YAML context: block. Fork and replace it with your own conventions. Plugin updates overwrite the file, so keep local edits in a fork or copy it elsewhere and point the wrapper at the copy.

Keep the structure rule if you rewrite it: headings, SHALL statements, and WHEN/THEN scenario keywords must stay verbatim or openspec validate fails.

Scope

context reaches artifact generation (proposal, specs, design, tasks). The apply and verify phases get it once Fission-AI/OpenSpec#887 merges.

Credits

context.yaml reproduces text from caveman (© Julius Brussee) and ponytail (© DietrichGebert), both MIT. This plugin is MIT too — see LICENSE.

About

Reusable project context for OpenSpec. Openspec has no global context setting, so this ships one and applies it per project.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors