[DEPRECATED] Use /planning:add-feature instead - adds spec with similarity checking and complete planning sync
Redirects to /planning:add-feature to prevent duplicate specs with similarity checking.
/plugin marketplace add vanman2024/dev-lifecycle-marketplace/plugin install planning@dev-lifecycle-marketplace<feature-description>šØ EXECUTION NOTICE FOR CLAUDE
When you invoke this command via SlashCommand, the system returns THESE INSTRUCTIONS below.
YOU are the executor. This is NOT an autonomous subprocess.
Immediately after SlashCommand returns, start executing Phase 0, then Phase 1, etc.
See @CLAUDE.md section "SlashCommand Execution - YOU Are The Executor" for detailed explanation.
Arguments: $ARGUMENTS
ā ļø DEPRECATED COMMAND
This command has been deprecated in favor of /planning:add-feature.
The Problem:
/planning:add-spec created specs without checking for duplicatesThe Solution:
Use /planning:add-feature instead, which:
Old way (DEPRECATED):
/planning:add-spec "email notifications"
ā Blindly creates spec 021
ā Might duplicate existing notification spec
New way (RECOMMENDED):
/planning:add-feature "email notifications"
ā Checks similarity with existing specs
ā Finds spec 003 "notification system" (87% match)
ā Asks: New feature or enhancement?
ā Routes correctly, no duplicates
This command will automatically redirect you to /planning:add-feature.
Phase 1: Deprecation Warning Goal: Inform user and redirect
Actions:
/planning:add-feature is betterPhase 2: Redirect Goal: Route to correct command
Actions:
Command Status: DEPRECATED as of 2025-11-05
Replacement: /planning:add-feature
Reason: Similarity checking required to prevent duplicate specs
Breaking Change: No - command still exists but redirects