nonfunctional-requirements

Identify and enforce non-functional requirements for KDA-CE smart contracts.

1|1|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/Pact-Community-Organization/github-marketplace --skill nonfunctional-requirements-pact-community-organization
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nonfunctional-requirements
Source: https://github.com/Pact-Community-Organization/github-marketplace/tree/main/skills/nonfunctional-requirements
Command: npx skills add https://github.com/Pact-Community-Organization/github-marketplace --skill nonfunctional-requirements-pact-community-organization

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Non-functional requirements ensure contract quality by outlining measurable performance, security, scalability, and compatibility criteria for KDA-CE smart contracts.

Core Features & Use Cases

  • Define measurable NFR categories for gas efficiency, security properties, scalability limits, and compatibility requirements.
  • Support governance-guided upgrades and schema evolution to keep contracts maintainable.
  • Integrate with deployment pipelines to audit and validate compliance against defined NFRs.

Quick Start

Analyze an existing contract module and apply the NFR template to establish gas budgets, verification requirements, and interface compatibility.

Frequently Asked Questions about nonfunctional-requirements

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are non-functional requirements for KDA-CE smart contracts?

Non-functional requirements for KDA-CE smart contracts are measurable criteria across performance, security, scalability, and compatibility that ensure contract quality and maintainability during design, development, deployment, and governance.

How do I establish a gas budget for my smart contract?

You can establish a gas budget by applying an NFR template to your contract module, specifying measurable performance criteria and validation methods to enforce gas efficiency limits across deployment pipelines.

Can I enforce formal verification and cross-chain compatibility rules during development?

Yes, you can enforce formal verification and cross-chain compatibility by defining specific NFR categories with measurable validation methods, integrating these checks directly into your deployment pipelines to audit compliance.

What is the best way to manage upgrade governance and schema evolution?

The best way to manage upgrade governance and schema evolution is through governance-guided NFR frameworks that define compatibility requirements, ensuring contracts remain maintainable and compliant across updates.

How do I validate my contract module against scalability limits and security properties?

You validate contract modules against scalability limits and security properties by defining measurable NFR categories, then integrating compliance audits into your deployment pipelines to verify enforcement.