select

Plan swarm-ready tasks from source files into a canonical OrchPlan.

66|2|Updated Feb 18, 2015
One-click install
npx skills add https://github.com/tkersey/dotfiles --skill select
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: select
Source: https://github.com/tkersey/dotfiles/tree/main/codex/skills/select
Command: npx skills add https://github.com/tkersey/dotfiles --skill select

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill plans swarm-ready tasks from a chosen source and emits a structured OrchPlan that can be executed across multiple agents. It ensures tasks are atomic, dependencies are explicit, and work can be scheduled in parallel where safe.

Core Features & Use Cases

  • Atomic task decomposition: break down sources into independent tasks with explicit dependencies.
  • Dependency-aware planning: schedule tasks based on readiness and lock-based scope to avoid conflicts.
  • Source detection and normalization: read SLICES.md, beads lists, or plan-N.md, auto-remediate common issues, and produce a canonical OrchPlan.
  • Optional pipelines: emit planning pipelines to drive execution or review.

Quick Start

Run the select skill against a repository containing a SLICES.md or a plan-*.md to generate an OrchPlan. Review the decided waves and the decision trace to coordinate manual writeback.

Frequently Asked Questions about select

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan parallel tasks with explicit dependencies from a markdown source?

To plan parallel tasks with explicit dependencies, the skill reads sources like SLICES.md or plan-N.md, normalizes task metadata, and emits a canonical OrchPlan with dependency-aware, lock-safe waves for execution across multiple agents.

What is an OrchPlan and when do I need it for multi-agent task scheduling?

An OrchPlan is a structured output that schedules atomic tasks into lock-safe, parallel execution waves. You need it when decomposing sources like bead lists into independent tasks to avoid conflicts across multiple agents.

How do I generate a dependency-aware execution plan from a SLICES.md file?

You generate a dependency-aware execution plan by running the skill against a repository containing SLICES.md. It detects the source, applies safe auto-remediation to task metadata, and outputs scheduled waves with a decision trace.

Does this task planning approach support lock-based scope to prevent parallel conflicts?

Yes, this task planning approach uses lock-based scope to schedule tasks based on readiness, ensuring atomic tasks are scheduled in parallel only where safe and preventing execution conflicts.

Can I use bead lists as a source to produce a canonical task plan with pipelines?

Yes, you can use bd bead lists as a source. The skill reads and normalizes the bead list format, applies auto-remediation, and emits a canonical OrchPlan with optional planning pipelines to drive execution.

What are the limitations of auto-remediation when normalizing task metadata from plan files?

Auto-remediation applies safe corrections to normalize task metadata from sources like plan-N.md, but it is limited to safe fixes; you must review the emitted decision trace to coordinate manual writeback for complex issues.