configure-trackerlisted

# Configure Tracker Select an issue tracker template and write it to the project-level config path. ## Step 1 — List available templates Run the shared script to find templates and auto-apply if only one exists: ```bash bash "<skill-dir>/scripts/configure-tracker-auto.sh" ``` If the script exits 0, the tracker is configured — skip to Step 4. If it exits 1, stop with the error message it printed. If multiple templates exist (script didn't auto-apply), list them for the user: ```bash REPO_TRACKERS="$(git rev-parse --show-toplevel)/.coding-crew/docs/templates/trackers" USER_TRACKERS="$HOME/.coding-crew/docs/templates/trackers" if [ -d "$REPO_TRACKERS" ] && [ -n "$(find "$REPO_TRACKERS" -name "*.md" -print -quit 2>/dev/null)" ]; then TRACKERS_DIR="$REPO_TRACKERS" elif [ -d "$USER_TRACKERS" ] && [ -n "$(find "$USER_TRACKERS" -name "*.md" -print -quit 2>/dev/null)" ]; then TRACKERS_DIR="$USER_TRACKERS" fi [ -n "$TRACKERS_DIR" ] && find "$TRACKERS_DIR" -name "*.md" | sort ``` For each file, derive a short name (filename without `.md`) and a one-line description from the first `#` heading inside the file if present; otherwise use the filename. Present a numbered menu, for example: ``` Available tracker templates: (1) local — Local markdown files in .scratch/ (2) linear — Linear.app integration ``` ## Step 2 — Choose a template Ask: "Which template? Enter a number." Wait for the user to enter a valid number. If the input is invalid, re-prompt once; then stop. ## Step