akili-specs 2.8.0 → 2.10.0

package/docs/skills/software-architect.md

@@ -0,0 +1,32 @@
+# `software-architect`
+
+**Author:** Juan Carlos Cadavid — [jcadavid.com](https://jcadavid.com)
+
+## Purpose
+
+Makes the agent operate as a **senior software architect** during TRD and design work. Its differentiator is the **Decision Spine** — Scenario → Tactic → Tier & Style → Pattern → View & Record: non-functional requirements are captured as six-part, measurable quality-attribute scenarios (SEI format); tactics answer each scenario; a **robust-vs-lite gate** sizes the architecture (and therefore the infrastructure) with evidence; design patterns enter only bound to named problems; everything lands as C4 views and compact ADRs. Inspired by SEI's *Software Architecture in Practice* and *Documenting Software Architectures*, the C4 model (Simon Brown), the Refactoring.Guru pattern catalog, Clean/Hexagonal architecture, and Google Cloud's agentic AI guides.
+
+## Use When
+
+- `/akili-constitution` reaches **Step 5 (TRD)** — automatic, required; Step 6 (Infrastructure) derives its shape from the tier decision.
+- `/akili-specify` Phase 2 designs an architecturally significant feature (new module/service, integration, data-flow, or NFR impact).
+- The user asks for architecture review, NFR identification, stack sizing, or design-pattern guidance.
+
+## Core Rules
+
+- **No NFR without a measure** — every scenario ends in a testable response measure; "fast/secure/scalable" without numbers is banned output.
+- **Minimum NFR sweep** — security, performance, scalability, availability always evaluated explicitly; "not architecturally significant" is valid, silence is not.
+- **Start lite, escalate with evidence** — robust choices (microservices, polyglot data, multi-agent AI) require a scenario whose measure the lite option cannot meet, recorded as an ADR.
+- **No pattern without a named problem** — each pattern cites the tactic it implements and the simpler alternative it beat.
+- **Every diagram has a legend**; C4 Context + Container are the default view set.
+- **Token frugality** — progressive disclosure via `references/` (NFR scenarios & tactics, architecture styles, design patterns, views & ADRs, agentic AI); conceptual designs only, no implementation code in documents.
+
+## Best Paired Commands
+
+- `/akili-constitution` — runs the full spine in Step 5; hands the tier decision to Step 6.
+- `/akili-specify` — feature-scale spine in Phase 2 `design.md`; its scenario→tactic→pattern traceability is what `judgment-day` audits.
+- `/akili-test` — scenario response measures become non-functional test candidates.
+
+## Source
+
+- `../../.claude/skills/software-architect/SKILL.md`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "akili-specs",
-  "version": "2.8.0",
+  "version": "2.10.0",
   "description": "Portable AKILI-SPECS methodology commands and skills for AI-assisted development.",
   "homepage": "https://github.com/JuankCadavid/akili-specs#readme",
   "repository": {