Get the FREE Ultimate OpenClaw Setup Guide →

devteam-select

npx machina-cli add skill michael-harris/devteam/devteam-select --openclaw
Files (1)
SKILL.md
2.9 KB

DevTeam Select Command

Command: /devteam:select

Select a plan to work on. The selected plan becomes the active plan for /devteam:implement.

Usage

/devteam:select 2                    # Select by number (from /devteam:list)
/devteam:select notifications        # Select by name (partial match)
/devteam:select feature-dark-mode    # Select by full plan ID

Your Process

Step 1: Identify Plan

By number:

/devteam:select 2

Look up plan #2 from index

By partial name:

/devteam:select dark

Search plans for "dark" in name/ID, confirm if multiple matches

By full ID:

/devteam:select feature-dark-mode

Direct lookup

Step 2: Validate Plan

Check plan status:

  • planned -> Ready to start
  • in_progress -> Can resume
  • complete -> Warn user (can re-run but likely not needed)
  • archived -> Ask to unarchive first
  • failed -> Ask to reset circuit breaker

Step 3: Update Active Plan

# Update index.json
active_plan: feature-dark-mode

# Update pointer file
echo "feature-dark-mode" > .devteam/active-plan.txt

Step 4: Show Confirmation

Selected plan: Dark Mode Support (feature-dark-mode)

Type: feature
Parent: project-taskmanager
Status: planned
Sprints: 1 total, 0 completed

Tasks:
  TASK-001: Define dark mode color tokens       [pending]
  TASK-002: Create theme context                [pending]
  TASK-003: Update components for theme         [pending]
  TASK-004: Add theme toggle UI                 [pending]

Next steps:
  /devteam:implement         Execute this plan
  /devteam:plan         Modify the plan
  /devteam:list         See all plans

Disambiguation

If partial match finds multiple plans:

/devteam:select mode

Output:

Multiple plans match "mode":

  1. feature-dark-mode (Dark Mode Support)
  2. feature-offline-mode (Offline Mode)

Enter number to select, or use full ID:
>

Error Cases

Plan not found:

No plan found matching "xyz"

Available plans:
  1. Task Manager App (project)
  2. Push Notifications (feature)
  3. Dark Mode Support (feature)

Use /devteam:list to see all plans.

Selecting archived plan:

Plan "old-dashboard" is archived.

Would you like to:
  1. Unarchive and select it
  2. Cancel

>

Selecting failed plan:

Plan "feature-auth" has a triggered circuit breaker.

Last failure: TASK-003 - Build error in AuthService
Consecutive failures: 5

Would you like to:
  1. Reset circuit breaker and retry
  2. Review failure logs first
  3. Cancel

>

See Also

  • /devteam:list - List all plans
  • /devteam:implement - Execute the active plan
  • /devteam:plan - Create a new plan

Source

git clone https://github.com/michael-harris/devteam/blob/main/skills/devteam-select/SKILL.mdView on GitHub

Overview

DevTeam Select lets you pick a plan to work on and make it the active plan for /devteam:implement. It supports selecting by number, partial name, or full plan ID, and updates both index.json and the active-plan pointer. Clear validation and confirmation help ensure you switch plans safely.

How This Skill Works

Choose a plan with /devteam:select using a number, a partial name, or a full plan ID. The command checks the plan status (planned, in_progress, complete, archived, failed) and, if valid, updates the active_plan in index.json and writes the current plan to .devteam/active-plan.txt, then shows a confirmation with plan details.

When to Use It

  • You have the plan list from /devteam:list and want to pick by number.
  • You know a plan by name or want to match partially (e.g., 'dark').
  • You know the exact plan ID and want a direct lookup.
  • The chosen plan is archived or failed, and you need to handle unarchive or reset.
  • You want to see a detailed confirmation (status, sprints, tasks) after selecting.

Quick Start

  1. Step 1: Identify Plan using /devteam:list and choose by number, name, or ID.
  2. Step 2: Validate Plan Status (planned/in_progress vs archived/failed) and resolve issues.
  3. Step 3: Update the active plan and confirm the selection shows plan details.

Best Practices

  • Verify the plan status before activating (planned or in_progress).
  • Use the full plan ID when possible to avoid duplicates or ambiguity.
  • After selection, ensure index.json and .devteam/active-plan.txt reflect the new active plan.
  • Review related dependencies and tasks within the plan before switching.
  • Only run /devteam:implement after you have confirmed the active plan is correct.

Example Use Cases

  • Selecting by number from /devteam:list, e.g., /devteam:select 2 to activate Dark Mode Support (feature-dark-mode).
  • Selecting by partial name, e.g., /devteam:select dark, then resolve if multiple matches are found.
  • Selecting by full ID, e.g., /devteam:select feature-dark-mode.
  • Attempting to select an archived plan, then choosing to unarchive and select it.
  • Handling a failed plan by reviewing failures or resetting the circuit breaker before re-trying.

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers