---

name: using-polydev description: This skill should be used at conversation start when user mentions parallel, multiple tasks/features, worktrees, lists 2+ independent work items, or similar keywords - determines which polydev skill to use. version: 0.1.0

Using Polydev Skills

When to Use This Skill

Use polydev skills when the user mentions:

• "parallel" / "simultaneously" / "at the same time"
• "multiple features" / "multiple tasks"
• Lists 2+ independent work items
• "worktree" / "branch" (in context of parallel work)
• "background" / "long-running command"

Script Path (Main Agent Must Follow)

All scripts MUST be called via $POLYDEV_SCRIPTS variable. NEVER use ./scripts/

⚠️ Windows Compatibility - CRITICAL

On Windows (Git Bash/MINGW), scripts MUST be executed using bash -c "$(cat ...)" pattern:

CopyPOLYDEV_SCRIPTS="/path/to/polydev/plugins/polydev/scripts"

# Define helper function for Windows compatibility
run_polydev() {
    local script="$1"
    shift
    SCRIPT_DIR="$POLYDEV_SCRIPTS" bash -c "$(cat "$POLYDEV_SCRIPTS/$script")" -- "$@"
}

# ✅ CORRECT - Use run_polydev helper (works on all platforms)
run_polydev spawn-session.sh <workspace> <branch> <worktree-path> <plan-file>

# ❌ WRONG - Direct execution FAILS SILENTLY on Windows
"$POLYDEV_SCRIPTS/spawn-session.sh" args...  # Silent failure!

Why this pattern? Claude Code's Bash tool on Windows has an issue where direct script execution returns exit code 0 but produces no output and doesn't actually execute.

---

Skill Selection Flow

CopyUser message received
    |
Contains parallel/multiple keywords?
    | YES
Is it complex/unclear? --YES--> Run /polydev-brainstorm
    | NO
Ready to execute? --YES--> Use polydev:polydev skill
    |
Need detailed plans? --YES--> Use polydev:writing-plans skill
    |
Running background command? --YES--> Use polydev:terminal-task-runner skill

Available Skills

---

Script Quick Reference (For Main Agent)

Always use run_polydev helper function (see above) for script execution.

Example calls:

Copyrun_polydev spawn-session.sh myproject feature/auth .worktrees/feature-auth PLAN.md
run_polydev poll.sh .worktrees 10
run_polydev list-sessions.sh

---

Red Flags - STOP and Check Polydev

If the main agent thinks:

All of these mean: Check polydev skills first.

Quick Decision Guide

User says "implement X, Y, and Z":

1. Are X, Y, Z independent? -> polydev:polydev
2. Need clarification? -> /polydev-brainstorm
3. Need detailed plans? -> polydev:writing-plans first

User says "run this build/test":

1. Will it take > 30 seconds? -> polydev:terminal-task-runner
2. Need to monitor output? -> polydev:terminal-task-runner

User says "SSH to server and run commands":

1. Use polydev:terminal-task-runner
2. Use run-background.sh to start SSH
3. Use send-to-session.sh to send subsequent commands
4. Use capture-screen.sh to read output

User says "research X":

1. Read-only analysis? -> polydev:agent-investigator (via spawn-agent.sh)
2. Need parallel research? -> Multiple agent-investigators

Cost Control Reminder

Sub-agents MUST use model: "sonnet" unless user explicitly requests otherwise.

Copy// Correct
Task({ prompt: "...", subagent_type: "general-purpose", model: "sonnet" })

// Wrong - will bankrupt user
Task({ prompt: "...", subagent_type: "general-purpose" })

Integration

This skill is the entry point. After determining which skill to use:

Copyusing-polydev (this skill)
    |
/polydev-brainstorm (if complex)
    |
polydev:writing-plans (if need plans)
    |
polydev:polydev (execution)
    |
polydev:worktree-executor (per-branch, sub-agent)