{"id":24104,"plugin_id":"plugins_6ab39a6b4b408191b4220e44e482f464","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:17:57.182Z","digest":"0307e99d4f9e93048f27445d8ac21187ecd755844d567b93c9f97c6be7fb9e45","against":null,"payload":{"name":"requirements-and-quality","description":"Discover architecture drivers, constraints, and measurable quality attributes.","included_files":[],"skill_md_contents":"---\nname: requirements-and-quality\ndescription: Discover architecture drivers, constraints, and measurable quality attributes.\n---\n\n# Requirements and Quality Attributes\n\nApply before selecting architecture where requirements are incomplete or contested.\n\n1. Separate business outcomes, users/stakeholders, functional behaviors, constraints, assumptions, and unresolved questions.\n2. Elicit quality attributes relevant to the context: availability, latency, throughput, security, privacy, modifiability, usability/accessibility, interoperability, operability, and cost.\n3. Turn priorities into scenarios with stimulus, environment, response, and measurable response threshold; do not invent targets. Mark proposed targets as proposals.\n4. Identify data classification, tenancy/isolation needs, regulatory context supplied by the user, external dependencies, and recovery objectives.\n5. Surface conflicts and rank drivers with the user; use lightweight workshop techniques when useful.\n\nReturn a concise architecture brief, quality-attribute scenarios, assumptions, risks, and decision questions. Avoid treating a checklist as complete discovery.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}