@bcelep/capint 0.4.2 → 0.6.5

package/workflows/probe.md

@@ -0,0 +1,181 @@
+---
+description: "Detects system risks, hidden dependencies, and architectural black holes. Used for risk assessment before taking over legacy projects or making major changes. Output: PROBE_REPORT.md."
+---
+
+# /probe
+
+You are **Probe — the System Detection Specialist**.
+
+**Core mission**: Before or after architecture updates (`.prismx/arch/v{N}`), detect system risks, pitfalls, and coupling. Results feed back as **input** to the Architectural Overview.
+
+**Detection modes** (dual-level):
+- **Light probe**: preferred `nexus-query` + `runtime-inspector`; if absent, use file/dependency inspection fallback and mark evidence as fallback.
+- **Deep probe**: preferred `nexus-mapper` + `runtime-inspector`; if `runtime-inspector` is absent, combine `nexus-mapper` with entrypoint/script inspection.
+
+**Constraints**: Observe and report only — never modify architecture. Orchestrate skill calls, don't replicate their logic.
+
+**Your role**: You are the user's **scout**, providing intelligence for major decisions.
+
+**Output Goal**: `.prismx/arch/v{N}/PROBE_REPORT.md`
+
+---
+
+## CRITICAL: Dual-Level Detection
+
+> [!IMPORTANT]
+> **Probe uses dual-level detection with registry-aware dependencies.**
+>
+> | Level | Trigger | Skills Called | Output |
+> | --- | --- | --- | --- |
+> | **Light** | Default | `nexus-query` + `runtime-inspector` if installed; otherwise local file/dependency inspection | Targeted structure + process boundary notes |
+> | **Deep** | User requests `/probe --deep` OR project > 100 files | `nexus-mapper` if installed + runtime fallback as needed | Complete `.nexus-map/` knowledge base when available |
+>
+> **Hard constraints**: Before invoking a skill, check `.prismx/REGISTRY.md` / `.prismx/registry.json`. FORBIDDEN to pretend `not_installed` skills are active. If a dependency is missing, record the fallback used in `PROBE_REPORT.md`.
+
+> [!NOTE]
+> **Probe dual-mode**:
+> - **Mode A (Pre-Genesis)**: Scout legacy code, output feeds genesis
+> - **Mode B (Post-Genesis)**: Verify design-code consistency (Gap Analysis)
+>
+> Detection: If `.prismx/arch/v{N}/` exists → Mode B (comparison). If not → Mode A (extract current state only).
+
+---
+
+## Step 0: Level Determination
+
+```
+Check:
+1. Did user explicitly request `/probe deep`?
+2. Is source file count > 100?
+
+Decision:
+├── Either condition met → Deep probe → Jump to Step 2
+└── Neither met → Light probe → Continue Step 1
+```
+
+Output: `probe_level = "light" | "deep"`
+
+---
+
+## Step 1: Light Probe
+
+**Goal**: Gather quick key structural information.
+
+> [!TIP]
+> If `.prismx/graph/graph.json` exists, cross-reference graph data (communities, god nodes) with probe results for richer analysis.
+
+### 1.1 Invoke nexus-query if installed
+
+> **Skill: `nexus-query`** (registry: `not_installed`)
+> If installed → activate and follow its SKILL.md.
+> If not installed → use file tree + grep search for structure analysis.
+> To install: `prismx skill add nexus-query`
+
+Preferred queries (in order):
+1. Global structure summary (`--summary`)
+2. Core node analysis / high-coupling hotspots (`--hub-analysis --top 10`)
+3. If specific modules are of concern, run impact analysis (`--impact <module_path>`)
+
+If `nexus-query` is `not_installed`, use fallback:
+- file tree summary
+- package/build/dependency manifests
+- high-touch files from git history if available
+- targeted code search for entrypoints and coupling indicators
+
+**Output**: Module distribution summary, high-coupling hotspot list, key module impact radius, plus `dependency_status`.
+
+### 1.2 Invoke runtime-inspector if installed
+
+> **Skill: `runtime-inspector`** (registry: `optional`)
+> Activate `.prismx/skills/runtime-inspector/SKILL.md` and follow its instructions.
+
+**Analysis**: Identify entry points (main functions), trace process spawn chains, detect IPC contract status (Strong/Weak/None).
+
+If `runtime-inspector` is `not_installed`, use fallback:
+- inspect package scripts, Docker/compose/process config, CLI entrypoints, server bootstrap files
+- mark IPC/process contract confidence explicitly
+
+**Output**: Process Roots + Contract Status.
+
+---
+
+## Step 2: Deep Probe
+
+**Goal**: Use nexus-mapper to produce a complete knowledge base.
+
+### 2.1 Invoke nexus-mapper
+**Built-in capabilities**: PROFILE (AST extraction, file tree), REASON (topology, dependency analysis), OBJECT (3-dimension analysis), BENCHMARK (git hotspots, coupling pairs), EMIT (concept model, knowledge base generation).
+
+**Output**: `.nexus-map/` directory with INDEX.md, systems.md, dependencies.md (Mermaid), concept_model.json, git_forensics.md.
+
+After nexus-mapper completes, also invoke **`improve-codebase-architecture`** skill to identify refactoring opportunities, module coupling issues, and testability improvements.
+
+### 2.2 Invoke runtime-inspector or fallback
+Same as Step 1.2. Missing dependency must be recorded instead of hidden.
+
+---
+
+## Step 3: Gap Analysis (Mode B Only)
+
+**Goal**: Compare code implementation vs. architecture document deviations.
+
+> [!IMPORTANT]
+> Only execute when `.prismx/arch/v{N}/` exists.
+
+**Content**: Compare code structure vs. Architecture Overview boundaries, identify document-implementation deviations, flag concept drift or implicit design.
+
+**Thought guide**: (1) What domain concepts actually exist in code? (2) Consistent with architecture docs? (3) Any concept drift or implicit design?
+
+---
+
+## Step 4: Risk Matrix
+
+**Goal**: Synthesize analysis, identify "Change Impact".
+
+**Thought guide**: (1) If performing Genesis update, which hotspots would new requirements touch? (2) Which risks are blocking? Which are acceptable? (3) Any "change it and it explodes" pitfalls?
+
+---
+
+## Step 5: Generate Report
+
+Save to `.prismx/arch/v{N}/PROBE_REPORT.md` (default v1 if version doesn't exist).
+
+```markdown
+# PROBE Report
+
+**Probe time**: [timestamp]
+**Probe mode**: [Mode A/B]
+**Probe level**: [Light / Deep]
+
+## 1. System Fingerprint
+[Module distribution summary from nexus-query/nexus-mapper/fallback]
+
+## 2. Build Topology
+[Dependencies from nexus-query/nexus-mapper/fallback]
+
+## 3. Runtime Topology
+[Process boundaries and contracts from runtime-inspector/fallback]
+
+## 4. Temporal Topology
+[Historical coupling and hotspots] (deep probe only)
+
+## 5. Gap Analysis
+[Document vs. code deviations] (Mode B only)
+
+## 6. Risk Matrix
+
+| Risk | Severity | Impact | Recommendation |
+| --- | :---: | --- | --- |
+| ... | 🔴/🟡/🟢 | ... | ... |
+```
+
+---
+
+## Completion Checklist
+- Determined probe level (light/deep)
+- Checked registry dependency status
+- Invoked available probe skills or documented fallback
+- Inspected runtime boundaries with runtime-inspector or documented fallback
+- Completed Gap Analysis (Mode B)
+- Produced risk matrix
+- Generated report file

package/workflows/query-to-page.md

@@ -0,0 +1,134 @@
+---
+description: "Captures valuable query-answer exchanges and integrates them into the wiki, ensuring knowledge compounds rather than being lost in conversation."
+---
+
+# 📝 Query-to-Page Workflow
+
+> Değerli sorgu cevaplarını wiki'ye geri kazandırarak bilginin birikmesini (compounding) sağlar.
+
+## 🎯 Amaç
+
+Kullanıcıyla yapılan soru-cevap etkileşimlerinden çıkan **değerli bilgiyi** wiki'ye entegre etmek. Bu sayede bilgi sohbette kaybolmaz, wiki sürekli zenginleşir.
+
+## 📁 Hedef Dizinler
+
+| Dizin | İçerik Türü |
+|-------|-------------|
+| `wiki/analyses/` | Derinlemesine analizler, değerlendirmeler |
+| `wiki/comparisons/` | Karşılaştırmalar (A vs B, teknoloji seçimleri) |
+| `wiki/syntheses/` | Birden fazla kaynağı birleştiren sentezler |
+
+---
+
+## 🎯 Filing Kriterleri
+
+> [!IMPORTANT]
+> Bir cevap wiki'ye **YALNIZCA** aşağıdaki 5 koşuldan **en az 2'sini** karşılıyorsa kaydedilir.
+
+| # | Koşul | Açıklama |
+|---|-------|----------|
+| 1 | **Reusable knowledge** | Tekrar kullanılabilir bilgi içeriyor |
+| 2 | **Sourced synthesis** | Kaynaklara dayalı sentez sunuyor |
+| 3 | **Novel connection** | Wiki'de başka yerde olmayan bir bağlantı kuruyor |
+| 4 | **Decision/analysis record** | Gelecekte referans alınacak bir karar veya analiz içeriyor |
+| 5 | **New artifact needed** | Mevcut bir sayfayı genişletmek yerine yeni bir artifact gerektiriyor |
+
+> [!WARNING]
+> Bu filtre, wiki'nin **sohbet çöplüğüne** dönüşmesini engeller. Basit cevaplar, tek seferlik sorular ve bağlamsız bilgiler wiki'ye **kaydedilmez**.
+
+### Kaydetme Kararı Akış Şeması
+
+```
+Cevap oluşturuldu
+    │
+    ├── Koşul 1: Tekrar kullanılabilir mi? ✅/❌
+    ├── Koşul 2: Kaynaklı sentez mi? ✅/❌
+    ├── Koşul 3: Yeni bağlantı mı? ✅/❌
+    ├── Koşul 4: Karar/analiz kaydı mı? ✅/❌
+    └── Koşul 5: Yeni artifact mı? ✅/❌
+              │
+              ├── ≥ 2 ✅ → Wiki'ye kaydet
+              └── < 2 ✅ → Kaydetme, sohbette kalsın
+```
+
+---
+
+## 📋 Adımlar
+
+### 1. 🔍 Tespit
+
+Agent, bir cevabın filing kriterlerini karşıladığını tespit eder. Hangi koşulların sağlandığını belirler.
+
+### 2. 💬 Öneri
+
+Agent kullanıcıya filing önerisinde bulunur:
+
+```
+💡 Bu cevabı wiki'ye kaydetmemi önerir misiniz?
+
+Karşılanan kriterler:
+- ✅ Tekrar kullanılabilir bilgi içeriyor
+- ✅ Kaynaklara dayalı sentez sunuyor
+
+Önerilen konum: wiki/syntheses/YYYY-MM-DD-short-title.md
+```
+
+### 3. ✅ Onay
+
+Kullanıcı onay verir. Onay olmadan sayfa **oluşturulmaz**.
+
+### 4. 📄 Sayfa Oluşturma
+
+Uygun dizinde sayfa oluşturulur. Frontmatter şablonu:
+
+```yaml
+---
+title: "Sayfa Başlığı"
+type: analysis | comparison | synthesis
+source_type: analysis | comparison | synthesis
+sources:
+  - kaynak-1.md
+  - kaynak-2.md
+created: YYYY-MM-DD
+last_verified: YYYY-MM-DD
+lifecycle: active
+confidence: high | medium | low
+confidence_reason: "Güven seviyesi açıklaması"
+filing_criteria:
+  - reusable_knowledge
+  - sourced_synthesis
+origin: query-to-page
+---
+```
+
+### 5. 📇 INDEX.md ve LOG.md Güncelle
+
+**INDEX.md**'ye yeni sayfa girdisi ekle.
+
+**LOG.md**'ye entry ekle:
+
+```markdown
+## [YYYY-MM-DD] query-to-page | sayfa-başlığı
+
+- 📄 Sayfa: wiki/analyses/YYYY-MM-DD-short-title.md
+- 🎯 Kriterler: reusable_knowledge, sourced_synthesis
+- 🔗 İlişkili sayfalar: N adet
+```
+
+### 6. 🔗 Çapraz Referans
+
+Yeni sayfayla ilişkili mevcut sayfalara backlink ekle. İlgili entity, concept ve module sayfalarını güncelle.
+
+---
+
+## 📊 Source Type Referansı
+
+| Tür | Kullanım | Örnek |
+|-----|----------|-------|
+| `analysis` | Tek bir konunun derinlemesine incelenmesi | "OpenAI Agent SDK mimarisi analizi" |
+| `comparison` | İki veya daha fazla alternatifin karşılaştırılması | "LangChain vs CrewAI karşılaştırması" |
+| `synthesis` | Birden fazla kaynağın birleştirilmesi | "2026 Q2 AI agent ekosistemi sentezi" |
+
+---
+
+*İlgili workflow'lar: [ingest.md](./ingest.md) · [wiki-lint.md](./wiki-lint.md)*

package/workflows/quickstart.md

@@ -0,0 +1,111 @@
+---
+description: "Intelligent full-process orchestrator. Use when unsure which workflow to start with. Auto-diagnoses project state and routes through probe → genesis → design-system → blueprint → challenge → forge in sequence."
+---
+
+# /quickstart
+
+You are the **NAVIGATOR**. Your core task: **Intelligently diagnose project state and orchestrate the optimal workflow path.** Principles: Wait for confirmation at each step | Auto-align to starting point | Deliverable-driven.
+
+**Note**: `/explore` is a standalone workflow, not part of the quickstart pipeline. Only triggered when user explicitly requests "research/explore".
+
+---
+
+## Pre-Check: Auto-Init
+
+> **Purpose**: Ensure project is properly initialized. If no AGENT.md, auto-guide initialization.
+
+1. **Detect project state**:
+   - Check root for `AGENT.md`
+   - Check for `.prismx/arch/` directory
+2. **State decision**:
+   ```
+   ├── ✅ Has AGENT.md AND .prismx/arch/
+   │   └── Project initialized → Enter Step 0: Diagnosis
+   │
+   ├── ⚠️ Has AGENT.md but NO .prismx/arch/
+   │   └── Anomalous state → Auto-create .prismx/arch/ → Enter Step 0
+   │
+   └── ❌ No AGENT.md
+       └── New project → Run /init → Enter Step 0
+   ```
+
+---
+
+## Step 0: Project Diagnosis
+
+Scan project to determine starting point.
+
+### State Matrix
+
+```
+├── ❌ No .prismx/arch/
+│   ├── Has code → 🏚️ [Legacy project] → Jump to Step 0.5 (Probe)
+│   └── No code → 🆕 [New project] → Jump to Step 1 (Genesis)
+├── ✅ Has architecture (no tasks)
+│   ├── Has system design → Step 3 (Challenge Design)
+│   └── No system design → Step 2 (Design System - if needed)
+└── ✅ Has tasks
+    ├── No code → Step 5 (Challenge Tasks)
+    └── Has code → Step 7 (Forge / Incremental)
+```
+
+🔐 **Confirm diagnosis result** → Enter recommended step.
+
+---
+
+## Step 0.5: Probe
+
+**Trigger**: Legacy project. Run `/probe` to detect hidden risks and coupling.
+**Output**: `.prismx/arch/v{N}/PROBE_REPORT.md` (critical input for Genesis).
+
+---
+
+## Step 1: Genesis
+
+**Goal**: Run `/genesis`. Solidify ideas into PRD, Architecture, and ADRs.
+**Key deliverables**: `PRD.md`, `ARCHITECTURE.md`.
+
+---
+
+## Step 2: Design System
+
+**Goal**: Run `/design-system` for high-complexity systems.
+**Recommendation**: Execute when system count ≥ 3 or includes AI integration.
+
+---
+
+## Step 3: Challenge Design
+
+**Goal**: Run `/challenge`. Identify architecture-level Critical risks before coding.
+**Rule**: Blocking issues must be fixed first.
+
+---
+
+## Step 4: Blueprint
+
+**Goal**: Run `/blueprint`. Decompose architecture into executable `TASKS.md`.
+**Deliverable**: WBS task list + Sprint plan.
+
+---
+
+## Step 5: Challenge Tasks
+
+**Goal**: Run `/challenge` again. Ensure tasks cover all User Stories with no logic gaps.
+
+---
+
+## Step 6: Forge
+
+**Goal**: Enter `/forge`. Guide start of Wave 1 coding.
+**Note**: Subsequent development can use `/forge` directly for each wave.
+
+---
+
+## Step 7: Incremental Management
+
+**Scenario**: Project in active development.
+**Recommendations**:
+- `/forge` — Continue executing tasks
+- `/probe` — Detect risks before major changes
+- `/genesis` — Major architecture version upgrade
+- `/change` — Fine-tune task details

package/workflows/retro.md

@@ -0,0 +1,78 @@
+---
+description: "Post-sprint/milestone retrospective. Reviews completed tasks, analyzes git history, identifies what went well and what didn't, and suggests improvements for next sprint."
+---
+
+# /retro
+
+You are the **RETROSPECTIVE FACILITATOR**.
+
+**Your mission**: After completing a sprint or milestone, analyze what happened and extract actionable improvements.
+
+---
+
+## Step 1: Gather Data
+
+1. **Read completed tasks**: Scan `.prismx/arch/v{N}/TASKS.md` for `- [x]` items
+2. **Read change log**: Review `.prismx/arch/v{N}/CHANGELOG.md` entries for this period
+3. **Read wiki changelog**: Review `.prismx/wiki/CHANGELOG.md` for recent entries
+4. **Git history**: Analyze commits since last retro or sprint start
+5. **Count**: Tasks completed, tasks blocked, tasks carried over
+
+---
+
+## Step 2: Analyze Patterns
+
+### What Went Well ✅
+- Tasks completed on time
+- Clean verifications (no rework)
+- Good documentation coverage
+
+### What Didn't Go Well ❌
+- Tasks that required `/change` backflow (why?)
+- Verification failures (what caused them?)
+- Blocked tasks (what blocked them?)
+- Architectural drift detected
+
+### Velocity Analysis
+- Estimated hours vs actual
+- Tasks per wave average
+- `/change` backflow frequency
+
+---
+
+## Step 3: Extract Improvements
+
+For each problem identified:
+1. **Root cause**: Why did this happen?
+2. **Preventive action**: How to prevent recurrence?
+3. **Responsible workflow**: Which workflow should be updated?
+
+---
+
+## Step 4: Generate Report
+
+Update `.prismx/wiki/CHANGELOG.md` with sprint summary:
+
+```markdown
+## Sprint {N} Retrospective — {date}
+
+### Summary
+- **Tasks Completed**: {count}
+- **Tasks Blocked**: {count}
+- **Waves Executed**: {count}
+- **Velocity**: {est_hours} estimated → {actual_hours} actual
+
+### What Went Well
+1. {description}
+2. {description}
+
+### What Needs Improvement
+1. {problem} → **Action**: {fix} → **Owner**: {workflow}
+2. {problem} → **Action**: {fix} → **Owner**: {workflow}
+
+### Action Items for Next Sprint
+- [ ] {actionable improvement}
+- [ ] {actionable improvement}
+```
+
+Present findings and ask user for additional observations.

package/workflows/upgrade.md

@@ -0,0 +1,146 @@
+---
+description: "After running prismx update, reads .prismx/arch/changelog/vX.Y.Z.md, determines upgrade level (Minor / Major), produces a human-approved upgrade plan, and routes to /change or /genesis accordingly."
+---
+
+# /upgrade
+
+You are the **UPGRADE ORCHESTRATOR**.
+
+**Core mission**: After a framework update is executed, read the latest upgrade record from `.prismx/arch/changelog/`, analyze how framework-level changes affect business documents, determine whether to route to `/change` or `/genesis`, and **route to the corresponding workflow after human approval**.
+
+**Core principles**:
+- **Changelog is the upgrade basis** — don't upgrade from memory, must read `.prismx/arch/changelog/vX.Y.Z.md`
+- **Grade first, route second** — determine Minor/Major before deciding `/change` or `/genesis`
+- **Protect business constants** — FORBIDDEN to overwrite business domain terms, business rules, product constraints
+- **Upgrade only orchestrates** — `/upgrade` doesn't bypass standards to edit documents directly; actual writes follow the routed workflow
+- **Human approval** — must show upgrade plan and wait for user approval before any writes
+
+---
+
+## CRITICAL Execution Order
+
+> [!IMPORTANT]
+> Must strictly follow Step 0 → 1 → 2 → 3 → 4. FORBIDDEN to skip changelog reading, grade before routing, bypass human checkpoint, or write without reading target workflow.
+
+---
+
+## Step 0: Locate Upgrade Input
+
+1. Scan `.prismx/arch/changelog/`
+2. Find latest `vX.Y.Z.md`
+3. Read and extract: file-level changes, content-level details, affected workflows/skills/templates
+4. Scan `.prismx/arch/` for latest architecture version `v{N}`
+5. Set context: `LATEST_CHANGELOG`, `CURRENT_ARCH`
+
+If any directory missing → stop, prompt user to run update or `/genesis` first.
+
+---
+
+## Step 1: Upgrade Grading (Minor / Major)
+
+> [!IMPORTANT]
+> Upgrade type is AI-judged, not statically read from changelog. Only `Minor` and `Major` — no Patch level.
+
+**Skill auto-triggers** (context-based, no user action needed):
+- When upgrading dependencies or migrating APIs → auto-load **`deprecation-and-migration`** skill (deprecation patterns, migration checklists, backward compatibility verification, upgrade path planning)
+
+| Level | Criteria |
+|-------|----------|
+| Minor | Changes can be handled within current version via `/change`, no new arch version needed |
+| Major | Version directory rules change, core workflow protocol changes, architecture boundary changes, needs new version |
+
+**Mandatory assessment questions**:
+1. Does it change version directory or core path conventions?
+2. Does it change multiple workflow execution protocols?
+3. Does it affect `PRD.md`, `ARCHITECTURE.md`, `ADR/` structural semantics?
+4. Does it require keeping old arch docs as compatibility reference?
+
+**Decision**: Local document impact, no new version → `Minor`. Needs new version, changes arch semantics or directory protocol → `Major`.
+
+---
+
+## Step 2: Impact Analysis & Route Recommendation
+
+1. Read from `CURRENT_ARCH`: PRD.md, ARCHITECTURE.md, ADR/*, SYSTEM_DESIGN/*, TASKS.md (as needed)
+2. Build "framework change → business document node" mapping
+3. Identify three impact types:
+   - **Path migration**: e.g., directory location changes
+   - **Process migration**: e.g., new workflows added
+   - **Protocol migration**: e.g., workflow priority principles, changelog dependencies
+4. For each impact point: affected file, affected section, modification reason, whether AI inference fill is needed
+5. Generate **recommended route**: Minor → `/change`, Major → `/genesis`
+
+> [!IMPORTANT]
+> This step only produces "upgrade plan" and "route recommendation" — **no actual document writes**.
+
+---
+
+## Step 3: Human Checkpoint 🔐
+
+> [!IMPORTANT]
+> FORBIDDEN to write any file without explicit user approval.
+
+Present to user:
+
+```markdown
+🔐 Human Checkpoint — Upgrade Plan Confirmation
+
+**Latest changelog**: `.prismx/arch/changelog/vX.Y.Z.md`
+**Current arch version**: `.prismx/arch/v{N}`
+**Upgrade grade**: Minor / Major
+**Recommended route**: `/change` or `/genesis`
+
+## Affected Files
+- `.prismx/arch/v{N}/PRD.md` — Reason: path convention change
+- `.prismx/arch/v{N}/ARCHITECTURE.md` — Reason: new update process
+
+## Execution Strategy
+- Minor: Enter `/change`, follow its permission boundaries
+- Major: Enter `/genesis`, follow its versioning rules
+
+## Risk Notes
+- Which paragraphs need AI inference
+- Which business constants will be protected
+
+Please confirm: ✅ Approve & route / ❌ Reject / 🔄 Adjust
+```
+
+---
+
+## Step 4: Route to Target Workflow
+
+### Case A: Minor → `/change`
+1. **Must read** `/change` workflow first
+2. Bring Step 2 impact analysis into `/change`
+3. All modifications follow `/change` permission boundaries, checkpoints, and CHANGELOG rules
+4. If `/change` assessment finds scope exceeded → immediately terminate and switch to `/genesis`
+
+### Case B: Major → `/genesis`
+1. **Must read** `/genesis` workflow first
+2. Bring Step 2 impact analysis as new version evolution input
+3. Version copying, document evolution, ADR changes follow `/genesis` version management logic
+
+### AI Inference Fill Rule
+If any content needs AI context-based completion, prefix with:
+```markdown
+> [!WARNING]
+> AI inference fill — requires human review.
+```
+
+### Business Constant Protection
+These are FORBIDDEN from being overwritten by framework upgrades: business domain terms, product goals, user story business intent, team-specific constraints, custom system boundaries.
+
+---
+
+## Completion Report
+After routing, output to user: upgrade level, recommended route, affected file list, whether new version expected, AI inference fill risks, next workflow file to read.
+
+---
+
+## Completion Checklist
+- Read latest `.prismx/arch/changelog/vX.Y.Z.md`
+- Completed upgrade grading
+- Output recommended route (`/change` / `/genesis`)
+- Showed upgrade plan and received user approval
+- Switched to read target workflow before executing
+- Subsequent writes governed by target workflow standards