What problem does it solve? When an ERP implementation request involves multiple steps or cross-layer combinations (e.g., enabling a standard module plus BOS configuration plus a Python plugin), jumping straight into execution causes missed steps, unclear ownership, and no rollback path. This Skill teaches the agent how to decompose requirements, write a plan markdown file that both consultants and clients can review, and execute it step by step with checkpoints. ## Core Features & Use Cases - Plan Template & Conventions: Provides a full markdown template with goals, acceptance criteria, layered step tags ([标准启用] / [BOS 配置] / [Python] / [交付]), owner fields limited to 你/我, risk register, and rollback path. - Persistent Plan Files: Plans are stored per project under ~/.opendeploy/projects/<projectId>/plans/ via write_plan / read_plan / list_plans tools, enabling cross-day resumption by reading unchecked steps. - Execution Cadence: Enforces per-step checkpoints, checkbox synchronization, verification after every action, and user sign-off before continuing. - Use Case: A client asks for credit management upgrade (enable standard module + add blacklist field + write BeforeSave plugin + training). The Skill produces a 4-step plan with owners, verification methods, and rollback steps, then executes it one confirmed step at a time. ## Quick Start Ask the agent to break this multi-part requirement into a step-by-step implementation plan with owners, verification, and rollback before executing anything.
