From e0225cbf5dcc440c88d6a90db7465b4b263878dd Mon Sep 17 00:00:00 2001 From: JeremyDev87 Date: Sat, 4 Apr 2026 09:29:37 +0900 Subject: [PATCH] fix(plugin): align /plan and /act docs with actual standalone defaults (#1248) plan.md referenced "Frontend Developer Agent" as the standalone default, but mode_engine.py uses "Technical Planner". Same mismatch in act.md where it said "Frontend Developer Agent" but the actual default is "Software Engineer". Updated both docs to match the implementation. --- packages/claude-code-plugin/commands/act.md | 4 ++-- packages/claude-code-plugin/commands/plan.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/packages/claude-code-plugin/commands/act.md b/packages/claude-code-plugin/commands/act.md index 0d98ab68..8cfda795 100644 --- a/packages/claude-code-plugin/commands/act.md +++ b/packages/claude-code-plugin/commands/act.md @@ -35,9 +35,9 @@ This command activates ACT mode for the CodingBuddy workflow. - Execute implementation steps defined in PLAN **🔴 Agent Activation (STRICT):** -- When ACT is triggered, **Frontend Developer Agent** (loaded via parse_mode in MCP mode; defaults in standalone mode) **MUST** be automatically activated +- When ACT is triggered, the **default ACT agent** (loaded via parse_mode in MCP mode; Software Engineer in standalone mode) **MUST** be automatically activated - The Agent's development philosophy and code quality checklist MUST be followed -- See agent documentation for complete development framework +- In MCP mode, the agent framework is loaded via parse_mode. In standalone mode, basic workflow guidance is provided by the mode detection hook. **Purpose:** Execute implementation following TDD cycle, augmented coding principles, and quality standards diff --git a/packages/claude-code-plugin/commands/plan.md b/packages/claude-code-plugin/commands/plan.md index 5ee8beed..1f166ed4 100644 --- a/packages/claude-code-plugin/commands/plan.md +++ b/packages/claude-code-plugin/commands/plan.md @@ -31,9 +31,9 @@ This command activates PLAN mode for the CodingBuddy workflow. - After creating plan, user can type `ACT` to execute **🔴 Agent Activation (STRICT):** -- When in PLAN mode, **Frontend Developer Agent** (loaded via parse_mode in MCP mode; defaults in standalone mode) **MUST** be automatically activated +- When in PLAN mode, the **default PLAN agent** (loaded via parse_mode in MCP mode; Technical Planner in standalone mode) **MUST** be automatically activated - The Agent's workflow framework and all mandatory requirements MUST be followed -- See agent documentation for complete development framework +- In MCP mode, the agent framework is loaded via parse_mode. In standalone mode, basic workflow guidance is provided by the mode detection hook. **Purpose:** Create actionable implementation plans following TDD and augmented coding principles