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>

plugins/ultraplan-local/README.md

@@ -1,19 +1,20 @@
-# ultraplan-local — Brief, Research, Plan, Execute
+# ultraplan-local — Brief, Research, Architect, Plan, Execute
 
-![Version](https://img.shields.io/badge/version-2.0.0-blue)
+![Version](https://img.shields.io/badge/version-2.2.0-blue)
 ![License](https://img.shields.io/badge/license-MIT-green)
 ![Platform](https://img.shields.io/badge/platform-Claude%20Code-purple)
 
-A [Claude Code](https://docs.anthropic.com/en/docs/claude-code) plugin for deep implementation planning, multi-source research, and autonomous execution. Four commands, one pipeline:
+A [Claude Code](https://docs.anthropic.com/en/docs/claude-code) plugin for deep implementation planning, multi-source research, CC-feature architecture matching, and autonomous execution. Five commands, one pipeline:
 
 | Command | What it does |
 |---------|-------------|
 | **`/ultrabrief-local`** | Brief — interactive interview produces a task brief with explicit research plan |
 | **`/ultraresearch-local`** | Research — deep local + external research with triangulation |
+| **`/ultra-cc-architect-local`** | Architect (optional) — match brief+research against available CC features; produce architecture note with explicit gaps |
 | **`/ultraplan-local`** | Plan — agent swarm exploration, Opus planning, adversarial review |
 | **`/ultraexecute-local`** | Execute — disciplined step-by-step implementation with failure recovery |
 
-Every artifact lives in one project directory: `.claude/projects/{YYYY-MM-DD}-{slug}/` contains `brief.md`, `research/NN-*.md`, `plan.md`, `sessions/`, and `progress.json`.
+Every artifact lives in one project directory: `.claude/projects/{YYYY-MM-DD}-{slug}/` contains `brief.md`, `research/NN-*.md`, `architecture/overview.md` (+ `gaps.md`), `plan.md`, `sessions/`, and `progress.json`.
 
 ### Division of labor
 
@@ -21,7 +22,8 @@ Every artifact lives in one project directory: `.claude/projects/{YYYY-MM-DD}-{s
 |---|---|---|
 | `/ultrabrief-local` | **Capture intent** — intent, goal, non-goals, success criteria, and a research plan with explicit topics. Interactive only. | `brief.md` (task brief) |
 | `/ultraresearch-local` | **Gather context** — code state, external docs, community, risk. Makes NO build decisions. | `research/NN-slug.md` (research brief) |
-| `/ultraplan-local` | **Transform intent into an executable contract** — per-step YAML manifest, regex-validated checkpoints, verifiable paths. Plan-critic is a hard gate. | `plan.md` with Manifest blocks + `plan_version: 1.7` |
+| `/ultra-cc-architect-local` | **Match to CC features** (optional) — match brief+research against Claude Code feature catalog (Hooks, Subagents, Skills, MCP, …) with brief-anchored rationale and honest coverage gaps. | `architecture/overview.md` + `architecture/gaps.md` |
+| `/ultraplan-local` | **Transform intent into an executable contract** — per-step YAML manifest, regex-validated checkpoints, verifiable paths. Plan-critic is a hard gate. Auto-discovers `architecture/overview.md` as priors. | `plan.md` with Manifest blocks + `plan_version: 1.7` |
 | `/ultraexecute-local` | **Execute the contract disciplined** — fresh verification, independent manifest audit, honest reporting. Does NOT compensate for weak plans — escalates. | `progress.json` + structured report + manifest-audit status |
 
 **Principle:** Each step consumes the previous step's structured artifact. If execute has to guess, the plan is weak and must be revised upstream — not patched downstream.
@@ -55,7 +57,11 @@ claude plugin marketplace add https://git.fromaitochitta.com/open/ktg-plugin-mar
 # Research each topic identified in the brief (manual default)
 /ultraresearch-local --project .claude/projects/2026-04-18-jwt-auth --external "What are current JWT best practices?"
 
-# Plan from brief + research
+# Match task against available CC features (optional, v2.2)
+/ultra-cc-architect-local --project .claude/projects/2026-04-18-jwt-auth
+# → architecture/overview.md + architecture/gaps.md
+
+# Plan from brief + research + architecture (architecture auto-discovered)
 /ultraplan-local --project .claude/projects/2026-04-18-jwt-auth
 
 # Execute
@@ -176,6 +182,55 @@ Flags combine: `--project <dir> --external --fg`.
 
 ---
 
+## `/ultra-cc-architect-local` — Architect *(optional, v2.2)*
+
+Matches the task brief and any research against available Claude Code features (Hooks, Subagents, Skills, Output Styles, MCP, Plan Mode, Worktrees, Background Agents) and produces an **architecture note** with brief-anchored rationale per feature and an explicit coverage-gap section.
+
+This step is optional. You can go straight from research to planning. Use the architect step when:
+
+- The task touches orchestration, policy, or long-running work where CC-feature choice matters.
+- You want a reviewed, explicit feature selection before planning instead of letting the planner pick implicitly.
+- You want a backlog of coverage gaps (things the skill catalog does not yet know) in a shareable form.
+
+### How it works
+
+1. Read `{project_dir}/brief.md` + all `{project_dir}/research/*.md`.
+2. Read the CC-feature skill catalog from `skills/cc-architect-catalog/`.
+3. Run `feature-matcher` + `gap-identifier` in parallel.
+4. Write `architecture/overview.md` (six required sections, YAML frontmatter).
+5. Run `architecture-critic` + `scope-guardian` in parallel (unless `--quick`).
+6. Write `architecture/gaps.md` as issue-ready drafts (unless `--no-gaps`).
+
+Downstream: `/ultraplan-local` auto-discovers `architecture/overview.md` in project mode and treats its `cc_features_proposed` as *priors* — exploration agents may override with evidence.
+
+### Modes
+
+| Flag | Behavior |
+|------|----------|
+| `--project <dir>` | **Required.** Read `{dir}/brief.md` + `{dir}/research/*.md`; write to `{dir}/architecture/`. |
+| `--fg` | Foreground (inline) — default is background via `architect-orchestrator`. |
+| `--quick` | Skip adversarial review (no `architecture-critic` pass). |
+| `--no-gaps` | Do not write `gaps.md` (gap-section remains inside `overview.md`). |
+
+### What the architecture note contains
+
+- **Context** — 3 sentences paraphrasing brief Intent + Goal.
+- **Proposed CC features** — a table with rationale (brief-anchored), supporting skill, and confidence per feature.
+- **Feature composition** — sequence, conflicts, fallbacks.
+- **Coverage gaps identified** — always present, even if empty. Honest "what we don't know yet".
+- **Alternatives considered** — at least one rejected feature combination with rationale from the brief.
+- **Open questions** — forwarded to the plan phase.
+
+### CC-feature catalog
+
+The architect command reads from `skills/cc-architect-catalog/`, a plugin-internal catalog of hand-written skills covering each CC feature at one or more layers (`reference`, `pattern`, `decision`). v2.2 ships 10 seeds covering all 8 features at the reference layer (plus pattern layer for hooks and subagents). The catalog is designed for later expansion via a separate skill-factory process — gaps surfaced by the architect command are the backlog for that work.
+
+### Hallucination gate
+
+The `architecture-critic` agent blocks any feature proposal that is not in the catalog's `cc_feature` taxonomy or the `feature-matcher`'s documented fallback minimum list. This prevents the architect from inventing CC features that do not exist.
+
+---
+
 ## `/ultraplan-local` — Planning
 
 Produces an implementation plan detailed enough for autonomous execution. **v2.0 breaking change:** requires `--brief` or `--project`. There is no longer an interview inside `/ultraplan-local` — use `/ultrabrief-local` first.