swarm-to-plan_skill

Overview

This skill runs a structured swarm planning session using three specialist agents (Product Manager, UX Designer, Engineering Lead) to debate an idea, surface ambiguities, ask clarifying questions, and produce a detailed implementation plan saved to plans/<plan-name>.md. It automates team creation, role-driven analysis, cross-role debate, prioritized questions for the human, and compilation of a final spec that aligns with product principles from rules/product-principles.md.

How this skill works

The skill reads the idea from the input argument and scans the repo for tech stack and patterns (package.json, configs, key files) to build a short codebase context summary. It spawns three subagents with role-specific prompts, collects initial analyses, facilitates a structured debate, compiles prioritized clarifying questions for the user, ingests answers, gathers final refinements, synthesizes a single coherent plan, writes plans/<plan-name>.md, and shuts down the temporary team.

When to use it

• Turning an early idea or feature request into a concrete implementation plan
• Preparing a scoped MVP spec before engineering work begins
• Aligning product, UX, and engineering on trade-offs and unanswered questions
• Needing a reproducible, auditable planning output written to the repo
• When you want the team to follow established product design principles automatically

Best practices

• Provide a concise, specific idea description as the argument to reduce low-value clarifications
• Review rules/product-principles.md in the repo before running to ensure alignment
• Answer the prioritized user questions promptly to minimize follow-up rounds
• Use slug-friendly plan names (lowercase, hyphens) so the output file path is neat
• Keep human responses focused on scope, priority, and constraints for highest impact

Example use cases

• Plan an MVP for collaborative document editing across web and mobile
• Design and scope a settings page redesign with accessibility requirements
• Evaluate technical approach and rollout plan for adding real-time notifications
• Create a phased implementation plan for migration to a new auth system
• Generate a spec for adding analytics events and dashboard pages