agentsclimarketplace

032 architecture adr non functional requirements

Skill jabrena/plinth/skills/032-architecture-adr-non-functional-requirements

Plinth is an AI-native engineering toolkit for modern Java enterprise SDLC, built around reusable Commands, Agents, Skills, and MCP Servers.

Install
npx -y skills add jabrena/plinth --skill 032-architecture-adr-non-functional-requirements

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

What its author says it does

Copied from the file, not written here

Facilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria. This should trigger for requests such as Create ADR for Non-functional requirements; Document Non-functional requirements; Capture Non-functional requirements; Generate Non-functional requirements in an ADR; Create ADR for performance scalability or security requirements. Part of Plinth Toolkit

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.8 KB, as published. Nobody here has run it

Create ADRs for Non-Functional Requirements

Guide stakeholders through a structured conversation to uncover and document architectural decisions for quality attributes using the ISO/IEC 25010:2023 quality model. This is an interactive SKILL. The ADR documents the outcome of the conversation, not the conversation itself. Act as an architecture consultant: challenge-first, consultative, adaptive. Use only the current conversation and repository files explicitly available in the current session.

What is covered in this Skill?

  • Challenge-first opening: ISO 25010:2023 quality characteristics (Functional Suitability, Performance Efficiency, Compatibility, Reliability, Security, Maintainability, Flexibility, Safety)
  • Understanding the challenge: drivers, constraints, system context
  • Quality-specific deep dive tailored to primary NFR category
  • Solution exploration and trade-off preferences
  • Decision synthesis and validation before ADR creation
  • ADR document generation with Quality Metrics & Success Criteria

Constraints

Use challenge-first, consultative discovery in small batches, build on answers, tailor to NFR category. Only create ADR after thorough conversation and user confirmation.

  • MANDATORY: Use the local shell date command before starting to get accurate timestamps for the ADR
  • MUST: Load the bundled reference template during the current session; ignore prior-session content unless the user provides it again
  • MUST: Start with challenge-first opening (ISO 25010:2023 quality characteristics)
  • MUST: Pose one or two discovery questions at a time; never all at once
  • MUST: Validate summary with user (Does this accurately capture your quality needs?) before proposing ADR creation
  • MUST: Wait for user to confirm proceed before generating the ADR

When to use this skill

  • Create ADR for Non-functional requirements
  • Document Non-functional requirements
  • Capture Non-functional requirements
  • Generate Non-functional requirements in an ADR
  • Create ADR for performance scalability or security requirements

Workflow

  1. Get current date

Use the local shell date command before discovery and use it for ADR timestamps.

  1. Load reference and open with quality challenge

Load references/032-architecture-adr-non-functional-requirements.md from this skill and begin with the challenge-first ISO 25010:2023 quality characteristics framing.

  1. Conduct consultative NFR discovery

Guide discovery in small batches to elicit drivers, constraints, quality priorities, options, and trade-off preferences tailored to the primary NFR category.

Step constraints:

  • Never ask all discovery questions at once
  • Validate summary with user before proposing ADR generation
  1. Generate ADR after explicit confirmation

Only after user confirms proceed, create the ADR including measurable Quality Metrics and Success Criteria.

Reference

For detailed guidance, examples, and constraints, see references/032-architecture-adr-non-functional-requirements.md.

Keep looking

Skills are one crate of 328,083. 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.