agentleFS
Sign inStart free
FuDesign2008FuDesign2008/open-skills/skills/opsx-workspace-gate/SKILL.md

opsx-workspace-gate

Skill6 starsChanged 6 days agoMITView on GitHub

Shared OpenSpec workspace gate for OPSX workflows: locate project root, verify openspec/, and require exact native OPSX skills before delegation. Triggers — 「OpenSpec 工程门禁」「OPSX 工程定位」「OpenSpec 原生技能检查」 / OPSX workspace gate, OpenSpec project root, native skill gate. Do NOT use for Jira, Git, retry binding, or implementation orchestration.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this priority order and stop at the first unique result:

    line 14
  2. Very specific:

    No match: stop and ask the user to enter an initialized OpenSpec project or run openspec init.

    line 21
  3. Distinctive:

    Search installed skill directories under the project root and require these exact names:

    line 31
  4. Very specific:

    Before delegating to any native OPSX skill, read that skill's current SKILL.md.

    line 44

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

OPSX Workspace Gate

Internal shared skill for OPSX workflows. It establishes an OpenSpec project root and verifies native-skill prerequisites before the host starts its workflow-specific orchestration.

1. Locate the project root

Use this priority order and stop at the first unique result:

  1. The current working directory contains openspec/.
  2. Walk upward from the current edit file and use the first ancestor containing openspec/.
  3. Scan direct children of the current working directory for openspec/.
    • One match: use it.
    • Multiple matches: list candidates and wait for the user to select one.
  4. No match: stop and ask the user to enter an initialized OpenSpec project or run openspec init.

Output 【工程定位结果】目标工程根：<absolute path>. Run subsequent OpenSpec paths, CLI commands, and native-skill delegation from that root; if changing the working directory is unavailable, use absolute paths.

2. Verify the OpenSpec directory

Confirm <project-root>/openspec/ exists. If it does not, stop and instruct the user to run openspec init; do not silently initialize it.

3. Verify native OPSX skills

Search installed skill directories under the project root and require these exact names:

Required skillWorkflow purpose
openspec-new-changeCreate a change
openspec-continue-changeCreate or continue artifacts
openspec-apply-changeImplement checked tasks
openspec-archive-changeArchive a completed change

openspec-verify-change is optional. Legacy or alternate names do not satisfy this gate. If a required skill is missing, stop and direct the user to run openspec init (first setup) or openspec update (refresh skills).

Delegation discipline

  • Before delegating to any native OPSX skill, read that skill's current SKILL.md.
  • CLI commands such as openspec status and openspec validate are allowed tools; they do not replace native skill delegation.
  • Hosts retain stage ordering, Jira/Git operations, retry/change binding, artifact sinks, and all workflow-specific decisions.

Integration guide

An OPSX host declares opsx-workspace-gate as a dependency, loads it for location plus gates, then continues with host-only setup. Do not copy this location algorithm, exact-name table, or delegation rules into the host.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free