feat(ultraplan-local): v2.2.0 — /ultra-cc-architect-local

New optional command between /ultraresearch-local and /ultraplan-local that
matches brief+research against Claude Code features (hooks, subagents, skills,
output-styles, MCP, plan-mode, worktrees, background-agents) and produces an
architecture note with brief-anchored rationale plus explicit gaps.

Added:
- commands/ultra-cc-architect-local.md (--project, --fg, --quick, --no-gaps)
- agents/architect-orchestrator.md (opus) — 6-phase background orchestrator
- agents/feature-matcher.md (sonnet) — fallback-ranked feature proposals
- agents/gap-identifier.md (sonnet) — 4 gap classes with issue-ready drafts
- agents/architecture-critic.md (sonnet) — hallucination gate as BLOCKER
- skills/cc-architect-catalog/ — SKILL.md + 10 seed entries (reference/pattern)

Changed (non-breaking):
- commands/ultraplan-local.md — auto-discovers architecture/overview.md
- agents/planning-orchestrator.md — cross-references cc_features_proposed
- plugin.json — 2.1.0 → 2.2.0, description, cc-architecture keyword
- CHANGELOG, README, CLAUDE.md (plugin + marketplace root)

Pipeline becomes brief → research → architect → plan → execute. Architect is
optional; existing project dirs keep working unchanged.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

skills/cc-architect-catalog/output-styles-reference.md

@@ -0,0 +1,58 @@
+---
+name: output-styles-reference
+description: CC output styles — configurable response shape, tone, length, and formatting baselines.
+layer: reference
+cc_feature: output-styles
+source: https://docs.claude.com/en/docs/claude-code/output-styles
+concept: output-style-config
+last_verified: 2026-04-18
+ngram_overlap_score: null
+review_status: approved
+---
+
+# Output Styles — Reference
+
+Output styles let a user or plugin shape how Claude Code responds:
+length defaults, formatting preferences, tone, verbosity. They apply
+across the session rather than needing to be re-stated per prompt.
+
+## Where they live
+
+- **Built-in styles** — shipped with the CLI.
+- **Custom styles** — directory with a manifest describing the style.
+- **Selection** — the user sets an active style via settings or a
+  `/style` command. The style is injected into Claude's system context.
+
+## What a style can control
+
+- Default response length baseline ("keep responses ≤ 100 words
+  unless detail is required").
+- Formatting rules (markdown vs plain, code-block conventions).
+- Tone ("terse", "pedagogical", "adversarial").
+- Domain voice (Norwegian for dialog, English for code — a project
+  convention encoded as a style).
+
+## What a style cannot control
+
+- Tool permissions (that is `allowed-tools` / `settings.json`).
+- Hooks (those are harness-level).
+- Agent system prompts (those come from agent definitions).
+
+## When to use a custom style
+
+- The project has a persistent communication convention that should
+  hold across every session (e.g., "never use emojis").
+- Multiple users share the project and want consistent output.
+- A skill's prompts would otherwise have to restate formatting rules
+  each time.
+
+## When not to
+
+- For per-task formatting needs — use the prompt instead.
+- For rules that must hold against prompt injection — use hooks.
+
+## Practical shape
+
+A minimal custom style is a markdown or plain-text block listing the
+conventions. Claude treats it as top-of-system guidance. Keep it
+short: long styles crowd out the task.