agentleFS
Sign inStart free
grasscaograssgrasscaograss/AwesomeWeldoneSkills/opsx-search/SKILL.md

opsx-search

Skill2 starsChanged 6 months agoApache-2.0View on GitHub

Search and navigate OpenSpec documents in this project. Use when: (1) user asks about specs related to a topic, capability, or code file; (2) looking for which specs define a feature or requirement; (3) finding active or archived changes; (4) understanding the scope of a capability. Triggers: \"find spec\", \"which spec covers\", \"search openspec\", \"related specs\", \"spec for X\", \"what specs exist for\".

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Search and navigate the project's OpenSpec documentation.

    line 12
  2. Very specific:

    Read openspec/INDEX.md first.

    line 33

≈ “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

OpenSpec Search

Search and navigate the project's OpenSpec documentation.

Directory Structure

openspec/
├── INDEX.md              # Capability index (READ THIS FIRST)
├── specs/<capability>/   # 78 stable capability specs
│   └── spec.md
├── changes/<change>/     # 17 active changes
│   ├── .openspec.yaml
│   ├── proposal.md       # Why / What / Impact
│   ├── design.md         # Decisions / Risks
│   ├── tasks.md          # Implementation checklist
│   └── specs/<cap>/spec.md  # Delta specs
└── changes/archive/      # 107 completed changes

Search Patterns

1. Quick lookup by topic

Read openspec/INDEX.md first. It groups all 78 capabilities by domain with one-line summaries.

2. Find specs mentioning a code file/class

grep -r "WeldUnrecognized" openspec/*/proposal.md openspec/specs/*/spec.md

3. Find specs by keyword

grep -ri "粗定位" openspec/specs/*/spec.md

4. List active changes with status

openspec list --json

5. Read a specific capability's full spec

openspec/specs/<capability-name>/spec.md

6. Read a change's motivation and impact

openspec/changes/<change-name>/proposal.md

Workflow

  1. Start with INDEX.md — locate relevant capability names
  2. Read the spec.md for detailed requirements and scenarios (BDD: WHEN/THEN)
  3. Check proposal.md of related changes for motivation and code impact
  4. Cross-reference — use grep to find connections between specs and code

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