agentleFS
Sign inStart free
zaxbysaucezaxbysauce/opencode-swarm/.claude/skills/discover/SKILL.md

discover

Skill517 starsChanged 3 days agoMITView on GitHub

Full execution protocol for MODE: DISCOVER -- read-only repository discovery and governance/context mapping.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 45 edited versions we read keep these.

  • 0

    Distinctive

    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. Very specific:

    Run symbols tool on key files identified by explorer to understand public API surfaces

    line 19
  2. Very specific:

    Run complexity_hotspots if not already run during project discovery (check context.md for existing analysis).

    line 21

“Common” is measured: kept by at least 6 in 10 of the 45 edited versions of this file we could read. “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

Discover Protocol

This protocol is loaded on demand by the architect runtime. The architect prompt keeps only activation, action, and hard safety constraints; the full execution details live here.

MODE: DISCOVER

Delegate to the active swarm's explorer agent. Wait for response. For complex tasks, make a second explorer call focused on risk/gap analysis:

  • Hidden requirements, unstated assumptions, scope risks
  • Existing patterns that the implementation must follow After explorer returns:
  • Run symbols tool on key files identified by explorer to understand public API surfaces
  • For multi-file module surveys: prefer batch_symbols over sequential single-file symbols calls
  • Run complexity_hotspots if not already run during project discovery (check context.md for existing analysis). Note modules with recommendation "security_review" or "full_gates" in context.md.
  • Check for project governance files using the glob tool with patterns project-instructions.md, docs/project-instructions.md, CONTRIBUTING.md, INSTRUCTIONS.md, AGENTS.md, and CLAUDE.md (process all matches found). For each file found: read it and extract all MUST (mandatory constraints) and SHOULD (recommended practices) rules. Write the extracted rules to .swarm/context.md under a ## Project Governance section — append if the section exists, create it if not — PRESERVING PROVENANCE for every rule (issue #2131 finding 9): each entry records (a) its source file, (b) the subtree scope the file declares or implies (repo-wide when undeclared), (c) precedence — AGENTS.md/project-instructions.md outrank CONTRIBUTING.md/INSTRUCTIONS.md/CLAUDE.md when rules conflict, (d) strength (MUST vs SHOULD), and (e) a conflict flag naming the other file whose rule it contradicts, if any. Never flatten conflicting rules into one; surface the conflict. If no MUST or SHOULD rules are found in the file, skip writing. If no governance file is found: skip silently. Existing DISCOVER steps are unchanged.

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