agentsclimarketplace
Sign in

Non functional requirements

Skill planifest/planifest-framework/planifest-framework/external-skills/non-functional-requirements

Quality attribute specification workflow after functional requirements are defined. Use when approved functional requirements need measurable performance/reliability/security/operability/compliance targets before implementation planning; do not use for initial requirement elicitation or sprint task breakdown.From its SKILL.md

Install
npx -y skills add planifest/planifest-framework --skill non-functional-requirements

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, 358 tokens by cl100k_base, as published. Nobody here has run it

Non Functional Requirements

Overview

Use this skill to define measurable quality constraints that are enforceable before release.

Scope Boundaries

  • Use this skill when the task matches the trigger condition described in description.
  • Do not use this skill when the primary task falls outside this skill's domain.

Shared References

  • NFR threshold definition rules:
    • references/nfr-threshold-definition-rules.md

Templates And Assets

  • NFR specification template:
    • assets/nfr-spec-template.csv
  • NFR observability mapping template:
    • assets/nfr-observability-mapping-template.md

Inputs To Gather

  • Approved functional requirement baseline.
  • Workload assumptions and operating context.
  • Security/legal/compliance obligations.
  • Existing telemetry and operational response capabilities.

Deliverables

  • Measurable NFR set with owners and linked requirements.
  • Signal/alert/runbook mapping for release-blocking NFRs.
  • Threshold rationale and escalation policy.

Workflow

  1. Define NFR set with assets/nfr-spec-template.csv.
  2. Apply threshold rules from references/nfr-threshold-definition-rules.md.
  3. Map each NFR to telemetry and runbooks via assets/nfr-observability-mapping-template.md.
  4. Mark release-blocking NFRs and owner accountability.
  5. Publish review-ready NFR baseline.

Quality Standard

  • Every NFR is measurable with unit, threshold, and owner.
  • Release-blocking NFRs are observable in production.
  • Threshold choices reflect user/business risk.

Failure Conditions

  • Stop when NFRs are qualitative and non-measurable.
  • Stop when required telemetry/runbook coverage is missing.
  • Escalate when legal/compliance constraints cannot be operationalized.

What ships with it: 1 file

11.3 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,758. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.