agentleFS
Sign inStart free
jon-devlapazjon-devlapaz/agentic-se-skills/.agents/skills/conops-builder/SKILL.md

conops-builder

Skill7 starsChanged 6 months agoMITView on GitHub

Use when defining user operating scenarios, workflows, actors, nominal paths, off-nominal paths, or concept-of-operations artifacts before coding.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Use this skill to define intended use before requirements or design.

    line 8
  2. Distinctive:

    Write the nominal scenario as observable user/system behavior.

    line 14
  3. Distinctive:

    Write off-nominal and degraded scenarios, including trigger, system response, and recovery expectation.

    line 15
  4. Very specific:

    Start with references/source-grounding.md, then inspect extraction/pages/page_060.md and Appendix S pages extraction/pages/page_261.md …

    line 23

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

CONOPS Builder

Use this skill to define intended use before requirements or design.

Workflow

  1. State the operational objective in user-visible terms.
  2. Identify actors, environment, preconditions, external interfaces, and constraints.
  3. Write the nominal scenario as observable user/system behavior.
  4. Write off-nominal and degraded scenarios, including trigger, system response, and recovery expectation.
  5. Separate behavior from design: say what must happen, not how to implement it.
  6. List assumptions, open questions, and unresolved interfaces.
  7. Output a CONOPS brief with: objective, actors, context, nominal flow, off-nominal flows, end state, assumptions, interfaces, and candidate requirements.
  8. Hand off candidate requirements to requirements-distiller; hand off intended-use checks to validation-planner.

Source grounding

Start with references/source-grounding.md, then inspect extraction/pages/page_060.md and Appendix S pages extraction/pages/page_261.md through extraction/pages/page_263.md before making CONOPS-specific claims.

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