← Software ArchitectCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Software Architect
Snapshot Sep 30, 2026 · 23:17 UTC · version 0.1.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"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"
}SHA-256: 0307e99d4f9e93048f27445d8ac21187ecd755844d567b93c9f97c6be7fb9e45