Loading...
Loading...
Found 24 Skills
Plan technical execution for software systems by organizing phases, dependencies, sequencing, infrastructure foundations, MVP scope, coordination points, and incremental architecture delivery.
Processes for routing community insights/actions and communicating outcomes back to members.
Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.
Guides technical program management—multi-team initiatives with dependencies, milestones, RAID tracking, launch readiness, stakeholder status, and cross-functional coordination across engineering, product, and infrastructure (not application code or BRDs). Use when running a technical program, dependency maps, milestones, exec status, or unblocking cross-team delivery—not for requirements (business-analyst), rollout (deployment-strategist), CI/CD (devops), data roadmaps (data-manager), or single-team delivery (fullstack-software-engineer). Incidents: incident-management-engineer. Architecture: senior-system-architecture. Strategy: business-consultant. Comms: communication-lead. DC site build: data-center-design-execution-lead. DC portfolio: data-center-portfolio-planning-execution-lead. M&A/financing deal execution and closing matrix: transaction-manager. Exec/VIP and community customer escalations: community-executive-escalations-program-manager. CVD/disclosure: technical-program-manager-security-cvd.
Coordinate Claude Code Agent Teams through filesystem-based protocol. Use when orchestrating multiple Claude agents on parallel tasks, need task dependency management, multi-agent code review or implementation. Do not use when single-agent work suffices, task is not parallelizable.
Orchestrate the release team: coordinates release-manager, qa-lead, devops-engineer, and producer to execute a release from candidate to deployment.
Spawning Plan. Use when user wants to spawn agents, create a team, or coordinate multiple agents. Automatically gathers context, asks team topology questions, outputs clean TEAM PLAN markdown, and gets user approval. 3 steps: context gathering → questions → present plan. **CRITICAL**: MUST NOT SPAWN AGENTS SKIPPING THIS SKILL, USE ALWAYS.
Use when the user says "vm", "voice mode", "team", "coordinate", or needs to orchestrate multiple agents working on related tasks in parallel
Template for documenting co-built solutions, integrations, and GTM motions with partners.
A comprehensive development team tailored for beginners, consisting of product managers, architects, designers, developers, and testers, guiding you through the entire process from concept to launch.
Direct research projects by gathering team feedback and delegating implementation tasks. Writes publication-quality scientific text and coordinates bioinformaticians, software developers, and biologist commentators via technical-pm.
Autonomous project gardening by a coordinated team of agents. Spawns a team of gardeners that each run the `garden` skill in parallel, coordinating via a shared task list to avoid duplicate work. Use when the user wants to tend multiple small issues in one pass. Invoke with /gardeners.