@moreih29/nexus-core 0.2.0 → 0.4.0

package/manifest.json

@@ -1,6 +1,6 @@
 {
-  "nexus_core_version": "0.2.0",
-  "nexus_core_commit": "166a3b29f2b5795b9df037442ddc5d2ae7e36e5a",
+  "nexus_core_version": "0.4.0",
+  "nexus_core_commit": "2cc2402301c1f9b95ef0e9896c30e561357a7c35",
   "schema_contract_version": "2.0",
   "agents": [
     {
@@ -20,39 +20,55 @@
       "body_hash": "sha256:85f9a3de419f32cdae284436eb1d902bff19a2230c50fe3068ffc642949a63b7"
     },
     {
-      "name": "writer",
-      "description": "Technical writing — transforms research findings, code, and analysis into clear documents and presentations for the intended audience",
-      "task": "Technical writing, documentation, presentations",
-      "alias_ko": "라이터",
-      "category": "do",
-      "resume_tier": "bounded",
+      "name": "reviewer",
+      "description": "Content verification — validates accuracy, checks facts, confirms grammar and format of non-code deliverables",
+      "task": "Content verification, fact-checking, grammar review",
+      "alias_ko": "리뷰어",
+      "category": "check",
+      "resume_tier": "ephemeral",
       "model_tier": "standard",
       "capabilities": [
+        "no_file_edit",
         "no_task_create"
       ],
-      "id": "writer",
-      "body_hash": "sha256:2edd9bf52e537c446b5ebfaafab214ebaaad2491f019aa8534453bff3f1cd37b"
+      "id": "reviewer",
+      "body_hash": "sha256:f04d15249601b14046e7e40a4475defb289436c4474afbd89986964f8c3e7c2f"
     },
     {
-      "name": "tester",
-      "description": "Testing and verification — tests, verifies, validates stability and security of implementations",
-      "task": "Testing, verification, security review",
-      "alias_ko": "테스터",
-      "category": "check",
-      "resume_tier": "ephemeral",
-      "model_tier": "standard",
+      "name": "designer",
+      "description": "UX/UI design — evaluates user experience, interaction patterns, and how users will experience the product",
+      "task": "UI/UX design, interaction patterns, user experience",
+      "alias_ko": "디자이너",
+      "category": "how",
+      "resume_tier": "persistent",
+      "model_tier": "high",
       "capabilities": [
         "no_file_edit",
+        "no_task_create",
+        "no_task_update"
+      ],
+      "id": "designer",
+      "body_hash": "sha256:88ac56147d0e5bdf23fa591ce570a9c2d0eb1338df4ec2219f6238ddfcb65df4"
+    },
+    {
+      "name": "engineer",
+      "description": "Implementation — writes code, debugs issues, follows specifications from Lead and architect",
+      "task": "Code implementation, edits, debugging",
+      "alias_ko": "엔지니어",
+      "category": "do",
+      "resume_tier": "bounded",
+      "model_tier": "standard",
+      "capabilities": [
         "no_task_create"
       ],
-      "id": "tester",
-      "body_hash": "sha256:4dd04e1c93ff9c0c9fa6aebb60ece3f9719e82f9714b13feea01b6163633caec"
+      "id": "engineer",
+      "body_hash": "sha256:3d58b1b490c2f93cace2eedd0f04ec000f84514388eb086768cf53f8fa33db01"
     },
     {
-      "name": "postdoc",
-      "description": "Research methodology and synthesis — designs investigation approach, evaluates evidence quality, writes synthesis documents",
-      "task": "Research methodology, evidence synthesis",
-      "alias_ko": "포닥",
+      "name": "strategist",
+      "description": "Business strategy — evaluates market positioning, competitive landscape, and business viability of decisions",
+      "task": "Business strategy, market analysis, competitive positioning",
+      "alias_ko": "전략가",
       "category": "how",
       "resume_tier": "persistent",
       "model_tier": "high",
@@ -61,8 +77,8 @@
         "no_task_create",
         "no_task_update"
       ],
-      "id": "postdoc",
-      "body_hash": "sha256:da9b8c2568b8b5812abed6d6324139f814379d48dc63cdc5d0b5b263f5407814"
+      "id": "strategist",
+      "body_hash": "sha256:0254b4144a22c66209bd68119553d9057a4fb7f9b1ff7ebb9878687d99583465"
     },
     {
       "name": "researcher",
@@ -77,13 +93,13 @@
         "no_task_create"
       ],
       "id": "researcher",
-      "body_hash": "sha256:7f5db3b52ae76a3b3214cf73b076980e15ef85c80b9aa86a9704f737e4b13251"
+      "body_hash": "sha256:fc79bafec05503327bd51a0b84b6e642d304bd79c45b78db6448b112793c143e"
     },
     {
-      "name": "strategist",
-      "description": "Business strategy — evaluates market positioning, competitive landscape, and business viability of decisions",
-      "task": "Business strategy, market analysis, competitive positioning",
-      "alias_ko": "전략가",
+      "name": "postdoc",
+      "description": "Research methodology and synthesis — designs investigation approach, evaluates evidence quality, writes synthesis documents",
+      "task": "Research methodology, evidence synthesis",
+      "alias_ko": "포닥",
       "category": "how",
       "resume_tier": "persistent",
       "model_tier": "high",
@@ -92,14 +108,14 @@
         "no_task_create",
         "no_task_update"
       ],
-      "id": "strategist",
-      "body_hash": "sha256:0254b4144a22c66209bd68119553d9057a4fb7f9b1ff7ebb9878687d99583465"
+      "id": "postdoc",
+      "body_hash": "sha256:da9b8c2568b8b5812abed6d6324139f814379d48dc63cdc5d0b5b263f5407814"
     },
     {
-      "name": "reviewer",
-      "description": "Content verification — validates accuracy, checks facts, confirms grammar and format of non-code deliverables",
-      "task": "Content verification, fact-checking, grammar review",
-      "alias_ko": "리뷰어",
+      "name": "tester",
+      "description": "Testing and verification — tests, verifies, validates stability and security of implementations",
+      "task": "Testing, verification, security review",
+      "alias_ko": "테스터",
       "category": "check",
       "resume_tier": "ephemeral",
       "model_tier": "standard",
@@ -107,38 +123,22 @@
         "no_file_edit",
         "no_task_create"
       ],
-      "id": "reviewer",
-      "body_hash": "sha256:f04d15249601b14046e7e40a4475defb289436c4474afbd89986964f8c3e7c2f"
+      "id": "tester",
+      "body_hash": "sha256:4dd04e1c93ff9c0c9fa6aebb60ece3f9719e82f9714b13feea01b6163633caec"
     },
     {
-      "name": "engineer",
-      "description": "Implementation — writes code, debugs issues, follows specifications from Lead and architect",
-      "task": "Code implementation, edits, debugging",
-      "alias_ko": "엔지니어",
+      "name": "writer",
+      "description": "Technical writing — transforms research findings, code, and analysis into clear documents and presentations for the intended audience",
+      "task": "Technical writing, documentation, presentations",
+      "alias_ko": "라이터",
       "category": "do",
       "resume_tier": "bounded",
       "model_tier": "standard",
       "capabilities": [
         "no_task_create"
       ],
-      "id": "engineer",
-      "body_hash": "sha256:3d58b1b490c2f93cace2eedd0f04ec000f84514388eb086768cf53f8fa33db01"
-    },
-    {
-      "name": "designer",
-      "description": "UX/UI design — evaluates user experience, interaction patterns, and how users will experience the product",
-      "task": "UI/UX design, interaction patterns, user experience",
-      "alias_ko": "디자이너",
-      "category": "how",
-      "resume_tier": "persistent",
-      "model_tier": "high",
-      "capabilities": [
-        "no_file_edit",
-        "no_task_create",
-        "no_task_update"
-      ],
-      "id": "designer",
-      "body_hash": "sha256:88ac56147d0e5bdf23fa591ce570a9c2d0eb1338df4ec2219f6238ddfcb65df4"
+      "id": "writer",
+      "body_hash": "sha256:2edd9bf52e537c446b5ebfaafab214ebaaad2491f019aa8534453bff3f1cd37b"
     }
   ],
   "skills": [
@@ -156,17 +156,15 @@
       "body_hash": "sha256:6c8d1a36626d4034209ff83780dec6238297ec4710612441b2ef09daac714ca8"
     },
     {
-      "name": "nx-plan",
-      "description": "Structured multi-perspective analysis to decompose issues, align on decisions, and produce an enriched plan before execution. Plan only — does not execute.",
-      "summary": "Structured planning — subagent-based analysis, deliberate decisions, produce execution plan",
-      "triggers": [
-        "plan"
-      ],
+      "name": "nx-init",
+      "description": "Project onboarding — scan, mission, essentials, context generation",
+      "summary": "Project onboarding — scan, mission, essentials, context generation",
+      "manual_only": true,
       "harness_docs_refs": [
-        "resume_invocation"
+        "instruction_file"
       ],
-      "id": "nx-plan",
-      "body_hash": "sha256:2e3f4fabb2961c052c4449f19ec16ed940394be037a63d4af90a3d12df8e4895"
+      "id": "nx-init",
+      "body_hash": "sha256:3c8230ecc0f87c541ec0ff80492a28f28bf173d0b9781901adadfae69a54b8ed"
     },
     {
       "name": "nx-sync",
@@ -176,23 +174,20 @@
         "sync"
       ],
       "id": "nx-sync",
-      "body_hash": "sha256:dbd3933c0474b2831a857308d9dd6ccd2c072f089327c22ce8d2842894fc3216"
+      "body_hash": "sha256:a7b0ae8f13ebcd10e52361d0ada1570ff0c47933f731deec07e95539c63e6946"
     },
     {
-      "name": "nx-init",
-      "description": "Project onboarding — scan, mission, essentials, context generation",
-      "summary": "Project onboarding — scan, mission, essentials, context generation",
-      "manual_only": true,
-      "id": "nx-init",
-      "body_hash": "sha256:11761d37bad2fb30ef1d562d22d9a395e27e0c3ce58ea42ad3b1799f47bf8950"
-    },
-    {
-      "name": "nx-setup",
-      "description": "Interactive project setup wizard for Nexus configuration.",
-      "summary": "Interactive Nexus configuration wizard",
-      "manual_only": true,
-      "id": "nx-setup",
-      "body_hash": "sha256:e66b0116d5da403c6480876a5b0a575110bcd26ecaa30079ce17de64fc112e65"
+      "name": "nx-plan",
+      "description": "Structured multi-perspective analysis to decompose issues, align on decisions, and produce an enriched plan before execution. Plan only — does not execute.",
+      "summary": "Structured planning — subagent-based analysis, deliberate decisions, produce execution plan",
+      "triggers": [
+        "plan"
+      ],
+      "harness_docs_refs": [
+        "resume_invocation"
+      ],
+      "id": "nx-plan",
+      "body_hash": "sha256:85b858089bd3dc276be61baa3f5265bc107a85470f169983e710fecb404bb4b1"
     }
   ],
   "vocabulary": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@moreih29/nexus-core",
-  "version": "0.2.0",
+  "version": "0.4.0",
   "description": "Nexus ecosystem Authoring layer — canonical prompts, neutral metadata, and vocabulary shared by Nexus harnesses",
   "license": "MIT",
   "repository": {
@@ -39,6 +39,7 @@
   "packageManager": "bun@1.3.12",
   "scripts": {
     "validate": "bun run scripts/validate.ts",
+    "validate:conformance": "bun run scripts/conformance-coverage.ts",
     "typecheck": "tsc --noEmit",
     "prepublishOnly": "bun run validate"
   },

package/skills/nx-init/body.md

@@ -4,11 +4,11 @@ Scans the project and builds Nexus knowledge in the flat .nexus/ structure. On f
 
 ## Constraints
 
-- NEVER modify source code. Slimming down CLAUDE.md beyond the project section is not this skill's responsibility.
+- NEVER modify source code. Slimming down the instruction file beyond the project section is not this skill's responsibility.
 - NEVER infer or guess information that cannot be confirmed from code — do not write it to context/.
 - NEVER store secrets (API keys, credentials, etc.) in knowledge files.
 - NEVER overwrite existing files without `--reset`. On resume, preserve existing files intact.
-- Project section in CLAUDE.md MUST go through user confirmation before writing.
+- Project section in the instruction file MUST go through user confirmation before writing.
 - NEVER reference or create identity/, codebase/, reference/, or core/ paths.
 - Essentials section MUST NOT exceed 10 lines. If more items are needed, move lower-priority ones to .nexus/context/.
 
@@ -116,7 +116,7 @@ Do not include items that are standard defaults for the detected tech stack. Do
 Present the full draft to the user in this format:
 
 ```
-The following will be added to CLAUDE.md (existing content will not be changed):
+The following will be added to the instruction file (see harness docs: instruction_file) (existing content will not be changed):
 
 <!-- PROJECT:START -->
 ## {project-name}
@@ -133,7 +133,7 @@ Any changes?
 
 Wait for the user to confirm or provide edits. Apply all changes in one pass — do not ask about Mission and Essentials separately.
 
-After confirmation, write the section into CLAUDE.md inside markers using the Edit tool. If CLAUDE.md already contains `<!-- PROJECT:START -->` markers, replace the content between them. If CLAUDE.md does not exist, create it with the markers.
+After confirmation, write the section into the instruction file inside markers using the harness's file-editing primitive. If the instruction file already contains `<!-- PROJECT:START -->` markers, replace the content between them. If the instruction file does not exist, create it with the markers.
 
 ### Step 3: Context Knowledge Auto-Generation
 
@@ -149,9 +149,9 @@ Principles:
 Generation targets (select and name based on what the project actually needs):
 - Development stack (languages, frameworks, runtimes, key dependencies, build/test/deploy workflow)
 - Design and architecture (module relationships, data flow, core entry points, conventions)
-- Implementation specifics (pipeline details, configuration patterns, file structure conventions, tool restrictions — anything too specific for CLAUDE.md but not readable from code alone)
+- Implementation specifics (pipeline details, configuration patterns, file structure conventions, tool restrictions — anything too specific for the instruction file but not readable from code alone)
 
-Use the Write tool to create files at `.nexus/context/{chosen-name}.md`.
+Use the harness's file-creation primitive to create files at `.nexus/context/{chosen-name}.md`.
 
 For large projects, spawn Writer subagents per topic to generate context knowledge in parallel. Lead coordinates and reviews outputs.
 
@@ -173,7 +173,7 @@ prompt_user({
 })
 ```
 
-If "Set up": present a draft based on scan results → user confirms → save via Write tool to `.nexus/rules/{topic}.md`.
+If "Set up": present a draft based on scan results → user confirms → save via the harness's file-creation primitive to `.nexus/rules/{topic}.md`.
 
 If "Skip": inform and proceed to Step 5.
 
@@ -185,7 +185,7 @@ Output a summary of the onboarding results.
 ## Nexus Initialization Complete
 
 ### Generated Files
-- CLAUDE.md: project section — mission and essentials (<!-- PROJECT:START/END -->)
+- instruction file: project section — mission and essentials (<!-- PROJECT:START/END -->)
 - .nexus/context/: {list of generated files}
 - .nexus/rules/: {generated files or "none (skipped)"}
 

package/skills/nx-init/meta.yml

@@ -2,4 +2,6 @@ name: nx-init
 description: Project onboarding — scan, mission, essentials, context generation
 summary: "Project onboarding — scan, mission, essentials, context generation"
 manual_only: true
+harness_docs_refs:
+  - instruction_file
 id: nx-init

package/skills/nx-plan/body.md

@@ -28,7 +28,7 @@ Facilitate structured multi-perspective analysis using subagents to decompose is
 ## Trigger
 
 - Explicit tag: `[plan]` — continue existing session if plan.json exists, otherwise start new
-- Additional analysis needed mid-session: spawn HOW subagents independently via Agent tool
+- Additional analysis needed mid-session: spawn HOW subagents independently via the harness's subagent spawn primitive
 - Continuing conversation without a tag → continue existing session
 
 ---
@@ -99,7 +99,7 @@ Understand code, core knowledge, and prior decisions before forming a planning a
 
 - NEVER call `nx_plan_start` before research is complete.
 - `research_summary` parameter in `nx_plan_start` is required — forces research completion before session creation.
-- Researcher subagents are spawned via the Agent tool and return findings to Lead. They do not join the plan session.
+- Researcher subagents are spawned via the harness's subagent spawn primitive and return findings to Lead. They do not join the plan session.
 
 **Existing session (plan.json present):**
 - Check current state with `nx_plan_status`.
@@ -120,7 +120,7 @@ Register the planning session.
 For each issue:
 
 1. **Current State Analysis** — Lead summarizes the current state and problems, drawing on research.
-2. **Subagent Analysis** — for complex issues, spawn HOW subagents (architect, strategist, etc.) in parallel via Agent tool. Each subagent independently analyzes the issue and returns findings.
+2. **Subagent Analysis** — for complex issues, spawn HOW subagents (architect, strategist, etc.) in parallel via the harness's subagent spawn primitive. Each subagent independently analyzes the issue and returns findings.
    - **Domain-Agent mapping** — match issue keywords to recommended HOW subagents:
 
    | Domain keywords | Recommended HOW |

package/skills/nx-sync/body.md

@@ -8,7 +8,7 @@ Scans the current project state and synchronizes .nexus/context/ design document
 - NEVER modify source code — this skill updates documentation only
 - NEVER guess information that cannot be confirmed from sources — mark as "needs verification" instead
 - MUST preserve existing content structure — update sections, don't rewrite entire files unnecessarily
-- NEVER use deprecated MCP knowledge tools — use Read and Write native tools only
+- NEVER use deprecated MCP knowledge tools — use the harness's file-reading and file-creation primitives only
 
 ## Guidelines
 
@@ -31,7 +31,7 @@ Collect information from all available sources:
 
 ### Step 2: Read Current Context
 
-Read all files in `.nexus/context/` using the Read tool:
+Read all files in `.nexus/context/` using the harness's file-reading primitive:
 
 - List files: `ls .nexus/context/`
 - Read each file to understand current documented state
@@ -45,13 +45,13 @@ Spawn Writer agent to update affected context documents:
 
 ```
 Agent({ subagent_type: "claude-nexus:writer", name: "writer-sync-context",
-  prompt: "Update .nexus/context/ documents based on the following changes. Read current files with the Read tool, then write updates with the Write tool. Changes: {change_manifest}" })
+  prompt: "Update .nexus/context/ documents based on the following changes. Read current files with the harness's file-reading primitive, then write updates with the harness's file-creation primitive. Changes: {change_manifest}" })
 ```
 
 The Writer agent:
-- Reads each relevant context file with the Read tool
+- Reads each relevant context file with the harness's file-reading primitive
 - Applies targeted updates — changes only the sections that are stale
-- Writes the updated file back with the Write tool
+- Writes the updated file back with the harness's file-creation primitive
 - Does not rewrite files that are already accurate
 
 ### Step 4: Report

package/skills/nx-setup/body.md

@@ -1,196 +0,0 @@
-## Role
-
-Interactive project setup wizard — configure Nexus for a new project with minimal token cost. Every step is a concrete choice via `prompt_user`, with no open-ended exploration.
-
-## Constraints
-
-- NEVER accept free-text input — every step must use `prompt_user` with explicit options.
-- NEVER skip the "Skip" option — all steps are optional.
-- NEVER modify files outside the selected scope without explicit user confirmation.
-- NEVER overwrite an existing `statusLine` field in settings.json without explicit user confirmation.
-
-## Guidelines
-
-## Trigger
-- Direct invocation: `/claude-nexus:nx-setup`
-
----
-
-## Steps
-
-### Step 1: Scope Selection
-
-```
-prompt_user({
-  questions: [{
-    question: "Where should the Nexus configuration be applied?",
-    header: "Scope",
-    multiSelect: false,
-    options: [
-      { label: "User (Global)", description: "Apply to all projects (~/.claude/CLAUDE.md, ~/.claude/settings.json statusline)" },
-      { label: "Project", description: "Apply to this project only (CLAUDE.md, .claude/settings.local.json)" }
-    ]
-  }]
-})
-```
-
-All file write paths for subsequent steps are determined by this selection:
-- User: `~/.claude/CLAUDE.md`, `~/.claude/settings.json` (statusline wrapper)
-- Project: `./CLAUDE.md`, `./.claude/settings.local.json`
-
-### Step 2: Statusline
-
-```
-prompt_user({
-  questions: [{
-    question: "Enable the Nexus statusline? (model, branch, context usage, rate limits)",
-    header: "Statusline",
-    multiSelect: false,
-    options: [
-      { label: "Enable (Recommended)", description: "2 lines: model+branch+git, context+usage meters" },
-      { label: "Skip", description: "Skip statusline configuration" }
-    ]
-  }]
-})
-```
-
-**Create wrapper script** (for Enable, run via Bash tool):
-```bash
-mkdir -p ~/.claude/hooks
-cat > ~/.claude/hooks/nexus-statusline.sh << 'EOF'
-#!/bin/bash
-SCRIPT=$(ls -1d "$HOME/.claude/plugins/cache/nexus/claude-nexus"/*/scripts/statusline.cjs 2>/dev/null | sort -V | tail -1)
-[ -n "$SCRIPT" ] && exec node "$SCRIPT"
-EOF
-chmod +x ~/.claude/hooks/nexus-statusline.sh
-```
-
-**On selection, depending on scope:**
-
-**(1) User scope:**
-- Create wrapper script (run step above)
-- If `statusLine` field is **absent** in `~/.claude/settings.json`: add statusLine setting directly:
-  ```json
-  { "statusLine": { "type": "command", "command": "bash $HOME/.claude/hooks/nexus-statusline.sh" } }
-  ```
-- If `statusLine` field **already exists** in `~/.claude/settings.json`: create wrapper only, do not modify settings.json — ask user to confirm replacement (see "Statusline coexistence handling" below)
-
-**(2) Project scope:**
-- Create wrapper script (run step above)
-- If `statusLine` field is **absent** in `.claude/settings.local.json`: add statusLine setting directly:
-  ```json
-  { "statusLine": { "type": "command", "command": "bash $HOME/.claude/hooks/nexus-statusline.sh" } }
-  ```
-- If `statusLine` field **already exists** in `.claude/settings.local.json`: create wrapper only, do not modify settings.local.json — ask user to confirm replacement (see "Statusline coexistence handling" below)
-**(3) Skip:**
-- Do not create wrapper or modify settings.json.
-
-**Statusline coexistence handling:**
-
-Run only if settings.json modification was deferred above (i.e., wrapper was created but existing statusLine was detected).
-If statusLine settings were already applied above, skip this sub-step.
-
-Specifically, treat an existing statusline setting as detected if any of the following are true:
-- `~/.claude/hooks/statusline.sh` file exists
-- Or the scope-appropriate settings.json (`~/.claude/settings.json` or `.claude/settings.local.json`) already has a `statusLine` field
-
-If detected:
-
-```
-prompt_user({
-  questions: [{
-    question: "An existing statusline configuration was detected. Replace it with the Nexus statusline?",
-    header: "Statusline",
-    multiSelect: false,
-    options: [
-      { label: "Replace (Recommended)", description: "Replace with Nexus statusline (wrapper script configuration)" },
-      { label: "Keep Existing", description: "Keep existing statusline. Nexus wrapper is created but settings.json is not modified." }
-    ]
-  }]
-})
-```
-
-- "Replace (Recommended)": replace the `statusLine` in the scope-appropriate settings.json with the Nexus wrapper (wrapper script already created above)
-- "Keep Existing": keep the existing `statusLine` in settings.json (wrapper script already created above — user can switch manually later)
-
-If no existing statusline configuration is detected, skip this sub-step.
-
-### Step 3: Recommended Plugin
-
-Check if `context7@claude-plugins-official` is in `enabledPlugins` (global or project settings.json).
-
-**Already installed:**
-
-Notify and skip:
-```
-"Recommended plugin already installed: context7 ✓"
-```
-
-**Not installed:**
-
-```
-prompt_user({
-  questions: [{
-    question: "Install the context7 plugin? It enables agents to look up library docs in real time.",
-    header: "Plugin",
-    multiSelect: false,
-    options: [
-      { label: "Install (Recommended)", description: "context7 — real-time library documentation lookup (Upstash Context7)" },
-      { label: "Skip", description: "Skip recommended plugin installation" }
-    ]
-  }]
-})
-```
-
-**If "Install":**
-Add to `enabledPlugins` in the scope-appropriate settings.json (`~/.claude/settings.json` or `.claude/settings.local.json`):
-```json
-{
-  "context7@claude-plugins-official": true
-}
-```
-Claude Code will automatically install the plugin at the start of the next session.
-
-**If "Skip":** proceed to the next step.
-
-Note: Once added to `enabledPlugins`, Claude Code automatically installs the plugin at the start of the next session.
-
-### Step 4: Knowledge Init
-
-```
-prompt_user({
-  questions: [{
-    question: "Auto-generate project core knowledge?",
-    header: "Init",
-    multiSelect: false,
-    options: [
-      { label: "Yes (Recommended)", description: "Analyze existing docs (README, CLAUDE.md, etc.) to generate knowledge files in .nexus/memory/ and .nexus/context/" },
-      { label: "Skip", description: "Run manually later with /claude-nexus:nx-init" }
-    ]
-  }]
-})
-```
-
-If "Yes": invoke `Skill({ skill: "claude-nexus:nx-init" })`.
-If "Skip": proceed to next step.
-
-### Step 5: Complete
-
-Output a setup completion message:
-- Summary of applied settings
-- Brief introduction to available skills/agents
-- "To get started, describe a task, or use [plan] for planning, [run] for execution, [rule] for saving rules"
-
----
-
-## Key Principles
-
-1. **Every step uses prompt_user** — no free-text input
-2. **Minimize tokens** — limit each step to concrete choices to prevent unnecessary exploration
-3. **Always provide a Skip option** — nothing is forced
-4. **Extensible structure** — includes recommended plugin step, expandable to additional categories in the future
-
-## State Management
-
-Setup operates via sequential prompt_user calls with no state file.
-Configuration results are written to the scope-appropriate settings file at each step.

package/skills/nx-setup/meta.yml

@@ -1,5 +0,0 @@
-name: nx-setup
-description: Interactive project setup wizard for Nexus configuration.
-summary: "Interactive Nexus configuration wizard"
-manual_only: true
-id: nx-setup