skills.rest
MaxGzLi
MaxGzLiCOMMUNITY
Explore all skills by this author →
GitHub

swarm-plan

Convert a product specification into a dated implementation plan with tasks.

4|1|Updated Mar 8, 2026
Search Tags:#acceptance-criteria#spec-to-plan#task-breakdown#codebase-analysis#implementation-plan#docs-plans#research-agents
One-click install
npx skills add https://github.com/MaxGzLi/claudeorc --skill swarm-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: swarm-plan
Source: https://github.com/MaxGzLi/claudeorc/tree/main/skills/swarm-plan
Command: npx skills add https://github.com/MaxGzLi/claudeorc --skill swarm-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a product specification into a concrete, actionable implementation plan so teams stop guessing scope, file targets, and dependencies and can begin work in isolated worktrees immediately.

Core Features & Use Cases

  • Parallel research agents: Dispatches three Explore agents (research, codebase, docs) in a single message to gather tech stack, integration points, and project constraints.
  • Synthesis into tasks: Merges findings and produces dated plan documents with task-by-task entries containing exact file paths, dependency ordering, and testable acceptance criteria.
  • Use Case: When a PM or engineer has a spec file, run this Skill to produce a ready-to-execute plan for worker agents or developer handoff.

Quick Start

Run the swarm-plan skill with a path to your spec file to generate a dated implementation plan in docs/plans/.

Frequently Asked Questions about swarm-plan

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

FAQPage Schema
How do I turn a product specification into an executable implementation plan?▼

To turn a product specification into an executable implementation plan, provide your spec file and codebase so parallel research agents can analyze integration points and generate a dated markdown document with exact file paths and execution order.

Does generating an implementation plan from a spec require manual codebase analysis?▼

Generating an implementation plan from a spec does not require manual codebase analysis because the process dispatches three parallel Explore agents to automatically gather tech stack details, integration points, and project constraints.

How are dependencies and acceptance criteria handled during task breakdown?▼

During task breakdown, dependencies and acceptance criteria are synthesized from agent research findings and embedded directly into the generated plan document to ensure testable execution order for worker agents or developer handoff.

What is the best way to prepare a repository for automated spec-to-plan conversion?▼

The best way to prepare a repository for automated spec-to-plan conversion is ensuring your product specification file resides within the codebase so research agents can accurately map architecture decisions and identify exact file paths.

Where does the generated implementation plan document get saved?▼

The generated implementation plan document gets saved as a dated markdown file at docs/plans/YYYY-MM-DD-<topic>.md, containing the synthesized task-by-task entries, dependency ordering, and testable acceptance criteria.

Related Skills

Explore More Product & Management Skills→
telum-aitelum-ai
2

project-import

Create a Speck project structure with a skeleton project.md file.

Official
Basic
Jurel89Jurel89

team

Coordinate N worker agents executing tasks in isolated git worktrees with back-pressure control.

Community
Advanced
oikon48oikon48
1

parallel-explore

Launch four Explore agents in parallel to investigate distinct codebase areas.

Community
Basic
royhenengelroyhenengel

plan

Generate spec-driven implementation plans for software development tasks.

Community
Intermediate