agentleFS
Sign inStart free
aws-solutionsaws-solutions/konductor/skills/non-functional-requirements/SKILL.md

non-functional-requirements

Skill11 starsChanged 50 days agoApache-2.0View on GitHub

Extracts measurable non-functional requirements from system design documents. Use after system design to produce NFRs across performance, availability, security, scalability, and observability. Outputs are used as inputs for test planning and architecture validation.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When this skill is activated, apply the following directly:

    line 12
  2. Distinctive:

    All NFRs must be measurable — no vague terms ("fast", "reliable", "secure").

    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

Non-Functional Requirements

Execution

When this skill is activated, apply the following directly:

Extract NFRs from the provided system design document across these categories:

  • Performance: response time targets (p50, p99), throughput (requests/second)
  • Availability: uptime target (e.g., 99.9%), RTO, RPO
  • Security: authentication method, encryption standards, compliance requirements
  • Scalability: min/max instance counts, scale trigger thresholds
  • Observability: required metrics, log retention, trace sampling rate
  • Cost: monthly budget target, cost per transaction target

All NFRs must be measurable — no vague terms ("fast", "reliable", "secure").

Quality Gate

CRITICAL (must fix):

  • NFRs use vague terms instead of measurable targets
  • Performance targets not separated by operation type (read vs write)
  • Availability target not expressed as a percentage with RTO/RPO

IMPORTANT (should fix):

  • Scale thresholds not defined (when to scale out, when to scale in)
  • Compliance requirements not mapped to specific standards (SOC2, PCI, HIPAA)
  • Observability requirements missing trace sampling rate

SUGGESTION:

  • Could add NFRs for cold start latency if Lambda is used
  • Could define degraded mode behavior when targets cannot be met

Present findings as: CRITICAL → IMPORTANT → SUGGESTION. Ask: "Fix these issues? [y/n]" — unless scope_confirmed is true, in which case report all the findings and leave fixing to the caller, without asking.

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