plan

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Outline

1. Discover Feature Context:

   a. Find Repository Root and Initialize Features Directory:

   REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
   
   # Source features location helper
   SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
   PLUGIN_DIR="$(dirname "$SCRIPT_DIR")"
   source "$PLUGIN_DIR/lib/features-location.sh"
   
   # Initialize features directory (handles migration if needed)
   get_features_dir "$REPO_ROOT"
   

   b. Get Current Feature:

   BRANCH=$(git rev-parse --abbrev-ref HEAD 2>/dev/null)
   FEATURE_NUM=$(echo "$BRANCH" | grep -oE '^[0-9]{3}')
   
   # Fallback for non-git
   if [ -z "$FEATURE_NUM" ]; then
     FEATURE_NUM=$(list_features "$REPO_ROOT" | grep -oE '^[0-9]{3}' | sort -nr | head -1)
   fi
   

   c. Locate Feature Directory:

   find_feature_dir "$FEATURE_NUM" "$REPO_ROOT"
   # FEATURE_DIR is now set by find_feature_dir
   

   d. Set Path Variables:

   FEATURE_SPEC="${FEATURE_DIR}/spec.md"
   IMPL_PLAN="${FEATURE_DIR}/plan.md"
   RESEARCH_FILE="${FEATURE_DIR}/research.md"
   DATA_MODEL_FILE="${FEATURE_DIR}/data-model.md"
   CONTRACTS_DIR="${FEATURE_DIR}/contracts"
   

   e. Validate Prerequisites:

   • Check that spec.md exists
   • If missing: ERROR "No specification found. Run /specify first."

2. Load context:

   • Read FEATURE_SPEC (spec.md)
   • Read .specswarm/constitution.md if it exists
   • Check for .specswarm/tech-stack.md
   • Load plan template from templates/plan-template.md or use embedded template