---
title: "ops-requirements-guidelines"
description: "Turn ambiguous operational briefs into grounded, testable workflow requirements."
canonical: https://agentpluginsdirectory.com/plugins/ops-requirements-guidelines
last-updated: 2026-09-21
---

# ops-requirements-guidelines
Turn ambiguous operational briefs into grounded, testable workflow requirements.
- Slug: ops-requirements-guidelines
- Publisher: Surajit Das
- Repository: https://github.com/surajit003/agent-skills
- Manifest: plugins/ops-requirements-guidelines/plugin.json
- Version: 0.1.1
- License: MIT
- Category (editorial): other
- Skills: 1 (ops-requirements-guidelines)
- MCP servers: 0
- Stars: 0
- Repository created: 2026-09-18
- Repository last pushed: 2026-09-21
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/ops-requirements-guidelines
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What ops-requirements-guidelines does, in the publisher's words

A reusable Agent Skill for turning an ambiguous customer brief into grounded, testable operational workflow requirements.

It is useful when an AI or automation idea depends on information from physical work, people, messages, transactions, machines, or existing software, and the hard question is not just what to build, but how the system can reliably know what happened.

The skill prompts an agent to:

- separate customer facts from inferences, assumptions, and unknowns;
- restate feature requests as operational decisions;
- map the idea-to-outcome chain with editable Mermaid diagrams;
- trace every required fact to a credible real-world source;
- represent missing, stale, disputed, and corrected information explicitly;
- keep authoritative state and deterministic rules outside the LLM conversation;

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/surajit003/agent-skills/HEAD/plugins/ops-requirements-guidelines/README.md

## Skills

- ops-requirements-guidelines: Turn a customer brief, operational problem, workflow description, or desired business outcome into grounded, testable, and visually mapped requirements. Use for discovery, solution challenges, operational state design, AI or automation feasibility, architecture options, minimum-prototype planning,…

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.