docs(readme): /agents head-start para + knowledge-bases phrasing (#1206)

- New 'A head start on /agents, too.' paragraph: Claude Code owns the
  /agents mechanism; attune-ai ships ready-made plugin subagents
  (security-reviewer, spec-author, refactor-planner, release-prep-auditor,
  + more) that appear on install — use as-is or fork.
- Reword the attune-gui pointer: 'help content and docs' ->
  'help-content, docs, or knowledge-bases'.

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

Author: silversurfer562

README.md

@@ -62,7 +62,7 @@ templates, and 380+ engineering lessons at
 [attune-ai.dev](https://attune-ai.dev) are authored, grounded, and
 maintained entirely by Attune's own stack.
 
-**Managing and creating help content and docs?**
+**Managing and creating help-content, docs, or knowledge-bases?**
 That's [`attune-gui`](https://github.com/Smart-AI-Memory/attune-gui)
 — a dedicated Living Docs dashboard wrapping `attune-rag`,
 `attune-help`, and `attune-author` in a single UI. `attune-ai` is the
@@ -149,6 +149,14 @@ Subagents are assigned models by task complexity — Opus for deep
 reasoning, Sonnet for analysis, Haiku for fast scanning — keeping
 cost proportional to value.
 
+**A head start on `/agents`, too.** Beyond the workflow teams above,
+attune-ai ships a curated set of Claude Code subagents —
+`security-reviewer`, `spec-author`, `refactor-planner`,
+`release-prep-auditor`, and more — that appear in your `/agents` list the
+moment the plugin installs. Claude Code gives you the *mechanism* to build
+subagents; attune-ai gives you a *running start* — use them as-is, or fork
+one as the scaffold for your own.
+
 ### 3. Socratic before execution
 
 Workflows ask questions before executing, not after. The `spec`