codingbuddy-rules 0.0.0-canary.20260106072742.5537605 → 0.0.0-canary.20260106105956.dda0e31

package/.ai-rules/CHANGELOG.md

@@ -5,6 +5,55 @@ All notable changes to the Multi-AI Coding Assistant Common Rules System will be
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [2.0.0] - 2026-01-06
+
+### Added
+
+- **PLAN Mode Primary Agents** with intent-based resolution
+  - `solution-architect.json`: High-level system design and architecture planning
+  - `technical-planner.json`: Low-level implementation planning with TDD and bite-sized tasks
+  - Intent-based automatic selection between architects based on prompt analysis
+  - Support for Korean and English intent patterns
+
+- **AI Model Selection and Resolution**
+  - CLI init prompt for model selection (Sonnet/Opus/Haiku)
+  - `ai.defaultModel` configuration field in `codingbuddy.config.js`
+  - Agent-level model preferences with priority resolution (agent > mode > system)
+  - `resolvedModel` field in MCP tool responses
+
+- **Parallel Agent Execution Support**
+  - `get_agent_system_prompt` MCP tool for generating subagent prompts
+  - `prepare_parallel_agents` MCP tool for batch agent preparation
+  - `parallelAgentsRecommendation` in `parse_mode` response
+  - Default specialist lists per mode (PLAN/ACT/EVAL)
+
+- **Dynamic Language Configuration**
+  - `LanguageService` supporting 10 languages (ko, en, ja, zh, es, de, fr, pt, ru, hi)
+  - `languageInstruction` field in `parse_mode` response
+  - Automatic language detection from project config
+
+- **Agent Activation Transparency**
+  - `ActivationMessageBuilder` for clear agent activation reporting
+  - `activation_message` field showing active agents with tiers
+
+### Changed
+
+- **Primary Agent Resolution**
+  - Extended `PrimaryAgentSource` type to include `intent`
+  - Priority order: explicit > config > intent > context > default
+  - Centralized Primary Agent constants with `_LIST` variants
+
+- **Token Usage Optimization**
+  - Mode-based `core.md` filtering to reduce token consumption
+  - Shared `ResponseUtils` for consolidated response generation
+
+### Fixed
+
+- Canary deployment timestamp mismatch bug
+- Type assertions replaced with proper typing in keyword service
+
+---
+
 ## [1.0.0] - 2025-11-20
 
 ### Added
@@ -48,18 +97,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
-### Added
-- **Clarification Phase** for PLAN mode (`rules/clarification-guide.md`)
-  - Optional phase triggered when AI detects ambiguous requirements
-  - Sequential Q&A with progress indicator (Question N/M format)
-  - Multiple-choice questions preferred for easy response
-  - Ambiguity assessment checklist (6 categories, triggers on 2+ unclear)
-  - Question count guidelines (2-7 questions based on complexity)
-  - Korean/English output format support
-  - Updated `rules/core.md` with Clarification Phase section
-
 ### Planned
-- Real-world usage testing across all 6 AI tools
+- Real-world usage testing across all 7 AI tools (including OpenCode)
 - Performance metrics collection
 - User feedback integration
 - Advanced examples and use cases

package/.ai-rules/agents/README.md

@@ -24,6 +24,8 @@ AI Agent definitions for specialized development roles.
 
 | Task Type | Recommended Agent | File |
 |-----------|-------------------|------|
+| **High-level Architecture Design** | Solution Architect | `solution-architect.json` |
+| **Implementation Planning** | Technical Planner | `technical-planner.json` |
 | **React/Next.js Development** | Frontend Developer | `frontend-developer.json` |
 | **Backend API Development** | Backend Developer | `backend-developer.json` |
 | **Code Review (EVAL)** | Code Reviewer | `code-reviewer.json` |
@@ -43,6 +45,8 @@ AI Agent definitions for specialized development roles.
 
 | Agent | Description |
 |-------|-------------|
+| Solution Architect | High-level system design and architecture planning |
+| Technical Planner | Low-level implementation planning with TDD and bite-sized tasks |
 | Frontend Developer | TDD-based frontend development with React/Next.js |
 | Backend Developer | Multi-stack backend API development (Node, Python, Go, Java, Rust) |
 | Code Reviewer | Auto-activated in EVAL mode, multi-dimensional code quality assessment |
@@ -93,9 +97,18 @@ as agent-architect, design new agent
 
 ### Available Primary Agents
 
+**PLAN Mode Primary Agents:**
+
+| Agent | role.type | Activation Condition |
+|-------|-----------|---------------------|
+| Solution Architect | `primary` | Architecture design, system design, technology selection |
+| Technical Planner | `primary` | Implementation planning, task breakdown, TDD planning |
+
+**ACT Mode Primary Agents:**
+
 | Agent | role.type | Activation Condition |
 |-------|-----------|---------------------|
-| Frontend Developer | `primary` | Default for PLAN/ACT modes, React/Next.js projects |
+| Frontend Developer | `primary` | Default for ACT mode, React/Next.js projects |
 | Backend Developer | `primary` | Backend file context (.go, .py, .java, .rs) |
 | Agent Architect | `primary` | Agent-related work requests |
 | DevOps Engineer | `primary` | Dockerfile, docker-compose context |
@@ -104,6 +117,15 @@ as agent-architect, design new agent
 
 EVAL mode always uses `code-reviewer` (regardless of Primary Agent settings).
 
+### Intent-Based Resolution (PLAN Mode)
+
+PLAN mode uses intent-based resolution to automatically select between Solution Architect and Technical Planner:
+
+| Intent Pattern | Selected Agent |
+|----------------|----------------|
+| Architecture, system design, technology selection | Solution Architect |
+| Implementation plan, task breakdown, TDD | Technical Planner |
+
 ---
 
 ## Mode Agents
@@ -253,6 +275,89 @@ Unified specialist agents organized by domain:
 
 ## Agent Details
 
+### Solution Architect (`solution-architect.json`)
+
+> **Note**: This is a **Primary Agent** for PLAN mode, specializing in high-level system design.
+
+**Expertise:**
+
+- System Architecture Design
+- Technology Selection
+- Integration Patterns
+- Scalability Planning
+- Trade-off Analysis
+
+**Development Philosophy:**
+
+- **Brainstorm-First**: Always start with `superpowers:brainstorming` skill
+- **Multiple Options**: Present 2-3 design approaches with trade-offs
+- **Incremental Validation**: Present design in sections (200-300 words) and validate with user
+- **Document-Driven**: Save validated designs to `docs/plans/YYYY-MM-DD-<topic>-design.md`
+
+**Responsibilities:**
+
+- Analyze requirements and constraints
+- Design high-level system architecture
+- Evaluate technology options
+- Define component boundaries
+- Delegate to domain specialists (Frontend/Backend/DevOps)
+
+**Workflow:**
+
+1. Invoke `superpowers:brainstorming` skill
+2. Understand project context (files, docs, commits)
+3. Ask clarifying questions one at a time
+4. Propose 2-3 approaches with trade-offs
+5. Present design in sections with user validation
+6. Document to `docs/plans/`
+7. Offer handoff to Technical Planner
+
+---
+
+### Technical Planner (`technical-planner.json`)
+
+> **Note**: This is a **Primary Agent** for PLAN mode, specializing in detailed implementation planning.
+
+**Expertise:**
+
+- Implementation Planning
+- TDD Strategy
+- Task Decomposition
+- Code Structure Design
+- Test Design
+
+**Development Philosophy:**
+
+- **Bite-Sized Tasks**: Each task is 2-5 minutes of work
+- **TDD-First**: Red-Green-Refactor-Commit structure per task
+- **Complete Code**: Plans include full code, no placeholders
+- **Exact Paths**: Specify exact file paths for all changes
+
+**Responsibilities:**
+
+- Break down designs into bite-sized tasks (2-5 minutes each)
+- Define exact file paths and code changes
+- Design test cases with TDD approach
+- Create executable implementation plans
+- Ensure plans are context-complete for engineers
+
+**Workflow:**
+
+1. Invoke `superpowers:writing-plans` skill
+2. Read design document or requirements
+3. Identify all components and dependencies
+4. Break into bite-sized tasks (2-5 minutes each)
+5. For each task: exact files, complete code, test commands
+6. Save to `docs/plans/YYYY-MM-DD-<feature>.md`
+7. Offer execution choice (subagent vs parallel session)
+
+**Execution Options:**
+
+- **Subagent-Driven**: Execute in current session with `superpowers:subagent-driven-development`
+- **Parallel Session**: Execute in separate session with `superpowers:executing-plans`
+
+---
+
 ### Primary Developer Agent Example: Frontend Developer (`frontend-developer.json`)
 
 > **Note**: This is an example Primary Developer Agent for React/Next.js projects. Create your own agent (e.g., `backend-developer.json`, `mobile-developer.json`) following this pattern for other tech stacks.
@@ -746,8 +851,10 @@ All agent files are located directly in `.ai-rules/agents/` directory without su
 
 ```
 .ai-rules/agents/
-├── frontend-developer.json          # Primary Agent (auto-activated, default)
-├── backend-developer.json           # Primary Agent for backend
+├── solution-architect.json          # Primary Agent for PLAN mode (architecture)
+├── technical-planner.json           # Primary Agent for PLAN mode (implementation)
+├── frontend-developer.json          # Primary Agent for ACT mode (default)
+├── backend-developer.json           # Primary Agent for ACT mode (backend)
 ├── agent-architect.json             # Primary Agent for agent management
 ├── devops-engineer.json             # Primary Agent for infrastructure
 ├── code-reviewer.json               # Core agent (EVAL mode, fixed)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codingbuddy-rules",
-  "version": "0.0.0-canary.20260106072742.5537605",
+  "version": "0.0.0-canary.20260106105956.dda0e31",
   "description": "AI coding rules for consistent practices across AI assistants",
   "main": "index.js",
   "types": "index.d.ts",