claude-nexus 0.17.0 → 0.19.0

package/.claude-plugin/marketplace.json

@@ -7,7 +7,7 @@
     {
       "name": "claude-nexus",
       "description": "Agent orchestration plugin for Claude Code. Injects optimized context per agent role with minimal overhead.",
-      "version": "0.17.0",
+      "version": "0.19.0",
       "author": {
         "name": "kih"
       },

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-nexus",
-  "version": "0.17.0",
+  "version": "0.19.0",
   "description": "Agent orchestration plugin for Claude Code — optimized context injection per role",
   "author": {
     "name": "kih"

package/README.en.md

@@ -26,7 +26,7 @@ Run `/claude-nexus:nx-init` — scans your project and auto-generates structured
 
 **3. Start using**
 
-- **Consult**: `[consult] How should we design the auth system?` — clarify intent and align before executing
+- **Meet**: `[meet] How should we design the auth system?` — clarify intent and align before executing
 - **Run**: `[run] Implement login API` — agent team handles analysis through implementation
 
 ## Usage
@@ -35,12 +35,12 @@ Tag your message to route it to the right workflow:
 
 | Tag | Action | Example |
 |-----|--------|---------|
-| `[consult]` | Pre-execution consultation | `[consult] Discuss DB migration strategy` |
+| `[meet]` | Pre-execution meeting | `[meet] Discuss DB migration strategy` |
 | `[run]` | Execution (agent team) | `[run] Refactor payment module` |
 | `[d]` | Record a decision | `[d] Use PostgreSQL for primary storage` |
 | `[rule]` | Save a rule | `[rule] Always use bun instead of npm` |
 
-Typical flow: use `[consult]` to discuss and align → decide → use `[run]` to execute.
+Typical flow: use `[meet]` to discuss and align → decide → use `[run]` to execute.
 
 ## Agents
 
@@ -72,10 +72,11 @@ Typical flow: use `[consult]` to discuss and align → decide → use `[run]` to
 
 | Skill | Trigger | Description |
 |-------|---------|-------------|
-| **nx-consult** | `[consult]` | Structured consultation. Clarify requirements → record decisions (`[d]`) → recommend execution tag |
+| **nx-meet** | `[meet]` | Structured meeting. Clarify requirements → record decisions (`[d]`) → recommend execution tag |
 | **nx-run** | `[run]` | Execution. User-directed agent composition for development, research, and more |
 | **nx-init** | `/claude-nexus:nx-init` | Full project onboarding: scan codebase, establish identity, generate core knowledge |
 | **nx-setup** | `/claude-nexus:nx-setup` | Interactive setup. Injects agent/skill/tag configuration into CLAUDE.md |
+| **nx-sync** | `/claude-nexus:nx-sync` | Core knowledge sync. Reflects source changes into .nexus/core/ docs |
 
 ## Advanced
 
@@ -84,21 +85,22 @@ Typical flow: use `[consult]` to discuss and align → decide → use `[run]` to
 
 Claude-callable tools exposed by the Nexus MCP server.
 
-### Core (14 tools)
+### Core (17 tools)
 
 | Tool | Purpose |
 |------|---------|
+| `nx_briefing` | Assemble role-specific briefing (core knowledge + rules) |
 | `nx_core_read/write` | Project knowledge management (git-tracked) |
 | `nx_rules_read/write` | Team custom rules management (git-tracked) |
-| `nx_context` | Current session state lookup (branch, tasks, decisions) |
+| `nx_context` | Current session state lookup (branch, tasks, meet) |
 | `nx_task_list/add/update/close` | Task management + history.json archiving |
-| `nx_decision_add` | Record architecture decisions |
 | `nx_artifact_write` | Save team artifacts (branch-isolated) |
-| `nx_consult_start` | Start consultation session (topic + issues) |
-| `nx_consult_status` | Query consultation state (with decisions join) |
-| `nx_consult_decide` | Record issue decision (consult.json + decisions.json) |
-| `nx_consult_update` | Modify consultation issues (add/remove/edit/reopen) |
-| `nx_branch_migrate` | Migrate state files (consult/decisions) across branches |
+| `nx_meet_start` | Start meeting session (topic + issues, team verification) |
+| `nx_meet_status` | Query meeting state |
+| `nx_meet_update` | Modify meeting issues (add/remove/edit/reopen) |
+| `nx_meet_discuss` | Record issue discussion (speaker validation: registered attendees only) |
+| `nx_meet_decide` | Record issue decision (meet.json) |
+| `nx_meet_join` | Join an ongoing meeting |
 
 ### Code Intelligence (10 tools)
 
@@ -128,7 +130,7 @@ Nexus registers a single Gate module as a Claude Code hook.
 | Event | Role |
 |-------|------|
 | `UserPromptSubmit` | Tag detection → mode activation + TASK_PIPELINE injection + additionalContext guidance |
-| `PreToolUse` | Edit/Write: blocks when tasks.json missing. Nexus internal paths exempted |
+| `PreToolUse` | Edit/Write: blocks when tasks.json missing. nx_meet_start: attendee team verification. Agent: team_name tracking |
 | `Stop` | Blocks exit with pending tasks. Forces nx_task_close when all completed |
 
 </details>
@@ -161,8 +163,7 @@ Runtime state is stored under `.nexus/` and is excluded from git.
 ├── branches/               ← Per-branch isolation
 │   └── {branch}/
 │       ├── tasks.json      ← Task list
-│       ├── decisions.json  ← Architecture decision list
-│       ├── consult.json    ← Consultation issue tracker
+│       ├── meet.json       ← Meeting issue tracker
 │       ├── history.json    ← Cycle archive (created by nx_task_close)
 │       └── artifacts/      ← Team artifacts
 └── sync-state.json         ← Last sync commit

package/README.md

@@ -28,14 +28,14 @@ claude plugin install claude-nexus@nexus
 
 **첫 사용**
 
-- **상담**: `[consult] 인증 시스템 어떻게 설계하면 좋을까?`
+- **미팅**: `[meet] 인증 시스템 어떻게 설계하면 좋을까?`
 - **결정 기록**: `응 그 방향으로 [d]`
 
 ## 사용법
 
 | 태그 | 동작 | 예시 |
 |------|------|------|
-| `[consult]` | 상담 모드 활성화 | `[consult] DB 마이그레이션 전략 논의` |
+| `[meet]` | 미팅 모드 활성화 | `[meet] DB 마이그레이션 전략 논의` |
 | `[d]` | 결정 기록 | `응 그 방향으로 [d]` |
 
 ## 에이전트
@@ -56,10 +56,11 @@ claude plugin install claude-nexus@nexus
 
 | 스킬 | 트리거 | 설명 |
 |------|--------|------|
-| **nx-consult** | `[consult]` | 구조화된 상담. 요구사항 정리 → 결정 기록 |
+| **nx-meet** | `[meet]` | 구조화된 미팅. 요구사항 정리 → 결정 기록 |
 | **nx-run** | (기본 동작) | 동적 에이전트 구성 실행 |
 | **nx-init** | `/claude-nexus:nx-init` | 프로젝트 온보딩. 코드 스캔 → 지식 생성 |
 | **nx-setup** | `/claude-nexus:nx-setup` | 대화형 설정 |
+| **nx-sync** | `/claude-nexus:nx-sync` | 코어 지식 동기화. 소스 변경사항을 .nexus/core/ 문서에 반영 |
 
 ## 고급 기능
 
@@ -68,20 +69,22 @@ claude plugin install claude-nexus@nexus
 
 Claude가 직접 호출하는 도구입니다.
 
-### Core (13개)
+### Core (17개)
 
 | 도구 | 용도 |
 |------|------|
+| `nx_briefing` | 에이전트 역할별 브리핑 조립 (core knowledge + rules 기반) |
 | `nx_core_read/write` | 프로젝트 지식 관리 (`.nexus/core/`, git 추적) |
 | `nx_rules_read/write` | 팀 커스텀 규칙 관리 (`.nexus/rules/`, git 추적) |
-| `nx_context` | 현재 세션 상태 조회 (브랜치, 태스크, 결정) |
+| `nx_context` | 현재 세션 상태 조회 (브랜치, 태스크, 미팅) |
 | `nx_task_list/add/update/close` | `.nexus/state/tasks.json` 기반 태스크 관리 + `.nexus/history.json` 아카이브 |
-| `nx_decision_add` | 아키텍처 결정 기록 (`.nexus/state/decisions.json`) |
 | `nx_artifact_write` | 팀 산출물 저장 (`.nexus/state/artifacts/`) |
-| `nx_consult_start` | 상담 세션 시작 (토픽 + 논점 등록) |
-| `nx_consult_status` | 상담 상태 조회 (decisions.json join) |
-| `nx_consult_decide` | 논점 결정 처리 (consult.json + decisions.json) |
-| `nx_consult_update` | 상담 논점 수정 (add/remove/edit/reopen) |
+| `nx_meet_start` | 미팅 세션 시작 (토픽 + 논점 등록, 참석자 팀 검증) |
+| `nx_meet_status` | 미팅 상태 조회 |
+| `nx_meet_update` | 미팅 논점 수정 (add/remove/edit/reopen) |
+| `nx_meet_discuss` | 논점 토론 기록 (speaker 검증: 등록된 참석자만 허용) |
+| `nx_meet_decide` | 논점 결정 처리 (meet.json) |
+| `nx_meet_join` | 진행 중인 미팅 참여 |
 
 ### Code Intelligence (10개)
 
@@ -111,7 +114,7 @@ Gate 단일 모듈로 동작합니다.
 | 이벤트 | 역할 |
 |--------|------|
 | `UserPromptSubmit` | 태그 감지 → 모드 활성화 + TASK_PIPELINE 주입 + additionalContext 안내 |
-| `PreToolUse` | Edit/Write: tasks.json 없으면 차단. Nexus 내부 경로는 예외 허용 |
+| `PreToolUse` | Edit/Write: tasks.json 없으면 차단. nx_meet_start: 참석자 팀 검증. Agent: team_name 트래킹 |
 | `Stop` | pending 태스크 있으면 종료 차단. all completed면 nx_task_close 강제 |
 
 </details>
@@ -125,7 +128,7 @@ Gate 단일 모듈로 동작합니다.
 - `rules/` — 팀 커스텀 규칙. git 추적.
 - `config.json` — Nexus 설정. git 추적.
 - `history.json` — 사이클 아카이브. git 추적.
-- `state/` — 런타임 상태 (tasks, decisions, consult 등). git 무시.
+- `state/` — 런타임 상태 (tasks, meet 등). git 무시.
 
 </details>
 
@@ -137,8 +140,7 @@ Gate 단일 모듈로 동작합니다.
 ```
 .nexus/state/
 ├── tasks.json
-├── decisions.json
-├── consult.json
+├── meet.json
 ├── edit-tracker.json
 ├── reopen-tracker.json
 ├── agent-tracker.json

package/VERSION

@@ -1 +1 @@
-0.17.0
+0.19.0

package/agents/engineer.md

@@ -81,6 +81,11 @@ When stuck on a technical issue or unclear on design direction:
 - Notify Lead as well to maintain shared context
 - Do not guess at implementations — ask when uncertain
 
+When work scope exceeds initial expectations:
+- If the task requires changes to 3+ files or touches multiple modules, report to Lead via SendMessage
+- Include: affected file list, reason for scope expansion, whether design review (How agent) is needed
+- Do not proceed with expanded scope without Lead acknowledgment
+
 ## Codebase Documentation
 Focus on code changes. Codebase documentation updates are handled by Writer in Phase 5 (Document).