skills.rest
myspecs
myspecsOFFICIAL
Explore all skills by this author →
Website𝕏@MySpecDevGitHub

plan

Builds factory wave plans by grouping MySpec tasks.md tasks into parallel worker groups.

Updated Sep 12, 2026
Search Tags:#pull requests#spec-driven development#brownfield#wave planning#parallel workers#task grouping#myspec
One-click install
npx skills add https://github.com/myspecs/claude-plugins --skill plan-myspecs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/myspecs/claude-plugins/tree/main/plugins/myspec-factory/skills/plan
Command: npx skills add https://github.com/myspecs/claude-plugins --skill plan-myspecs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating multiple coding workers on a spec bundle requires knowing which tasks are done, blocked, or ready, and which can safely run in parallel without file conflicts. This Skill derives that board from MySpec platform checkboxes and open pull requests, then groups related tasks into waves so a Software Factory Manager can dispatch workers without collisions. ## Core Features & Use Cases - Board derivation: Classifies every task as done, in flight, blocked, ready, or waiting using tasks.md checkboxes, open PRs, and factory branch names. - Wave planning: Groups tasks sharing dependency chains, modules, files, or requirements into one worker each, respecting the concurrency cap and milestone boundaries. - Lane planning for brownfield bundles: When a bundle lacks tasks.md, writes the task list itself, splits large changes into up to 3 parallel lanes with disjoint file ownership, and uploads only after user approval. - Use Case: Before running a factory on a MySpec bundle, ask for the wave plan to see a board table, Wave 1 worker assignments, waiting tasks, and spec gate blockers before any session is dispatched. ## Quick Start Ask the assistant to plan the factory run for your MySpec bundle and show which tasks can run in parallel.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I plan which spec tasks can run in parallel?▼

Ask to plan the factory run for your bundle. The Skill reads tasks.md from MySpec, checks open pull requests and factory branches, groups tasks sharing dependencies, modules, or files into one worker each, and outputs a wave table ordered by milestone.

What happens when a MySpec brownfield bundle has no tasks.md?▼

The Skill writes the task list itself, mapping the change from the proposal and requirements delta, then splits it into lanes: one worker, branch, and pull request per lane. Small changes stay one lane; large independent changes get up to 3, and nothing uploads until you approve.

Can the factory start while the spec session is still running?▼

No. The Skill first checks the bundle's generate session status with get_spec_session and stops immediately if it is not completed. You must finish the generate or edit session on the MySpec platform before any planning or dispatch.

How does the plan decide task status like ready or blocked?▼

Status comes from sources of truth: checked boxes in tasks.md mean done, open PRs or factory branches mean in flight, blocked labels or BLOCKED factory reports mean blocked, and unchecked tasks with all dependencies done are ready. The board is never stored as truth.

What are the limitations of parallel lane planning?▼

Lanes never exceed 3 or your concurrency cap, must own disjoint file paths, and cannot have cross-lane dependencies. Shared contracts must be written in full in both lanes' tasks; when work cannot be split this way, fewer lanes are used.

Related Skills

Explore More Software Engineering Skills→
cenconq25cenconq25
39

ux-review

Audit UX specs for completeness, accessibility, and platform conventions.

Community
Advanced
nebiusnebius
7

task-implementer

Coordinates brownfield implementation through dependency waves of isolated Git worktree workers.

Official
Advanced
jixoaijixoai
95

openspec-bulk-archive-change

Archive multiple completed changes and resolve spec conflicts by analyzing codebase implementations.

Official
Advanced
BryceRoberts13BryceRoberts13

subagent-driven-development

Dispatch subagents for isolated tasks with two-stage spec and code reviews.

Community
Advanced