team-create-plan

Orchestrate Architect, Risk Analyst, and Researcher roles to generate ADR-backed implementation plans.

17|1|Updated Dec 7, 2025
One-click install
npx skills add https://github.com/mhylle/claude-skills-collection --skill team-create-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-create-plan
Source: https://github.com/mhylle/claude-skills-collection/tree/main/skills/team-create-plan
Command: npx skills add https://github.com/mhylle/claude-skills-collection --skill team-create-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Team Create Plan skill orchestrates an expert planning team (Architect, Risk Analyst, and Researcher) to explore competing designs, challenge assumptions, and produce a coherent implementation plan for complex features or high-stakes changes.

Core Features & Use Cases

  • Team-based ideation: Three specialists work in parallel to surface trade-offs and synthesize a robust plan.
  • Adversarial review: The Risk Analyst actively challenges proposals to uncover risks and failure modes.
  • Structured plan output: Generates an ADR-backed plan with phase structure, exit conditions, risks, and dependencies.

Quick Start

Invoke the team-based planning workflow with the command that matches your topic, for example: /team-create-plan <topic-slug>.

Frequently Asked Questions about team-create-plan

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

FAQPage Schema
How do I create an implementation plan for complex features with multiple valid approaches?

To create an implementation plan for complex features, you can use a team-based planning workflow where an Architect, Risk Analyst, and Researcher collaborate to explore competing designs and challenge assumptions. This orchestrates parallel expert roles to synthesize a robust plan.

What is adversarial review in architecture design and when do I need it?

Adversarial review in architecture design is a process where a Risk Analyst actively challenges proposals to uncover risks and failure modes. You need it for high-stakes or ambiguous requirements where multiple valid approaches exist and adversarial review improves robustness.

How do I generate an ADR-backed plan for high-stakes codebase changes?

You generate an ADR-backed plan by orchestrating an expert planning team to research, challenge, and validate proposals. This produces a structured plan with phase structure, exit conditions, risks, and dependencies for your high-stakes codebase changes.

Does this team-based planning approach work for ambiguous requirements with no clear solution?

Yes, team-based planning is specifically designed for high-stakes or ambiguous requirements where multiple valid approaches exist. The three specialist roles work in parallel to surface trade-offs and synthesize a coherent implementation plan.

What's the best way to analyze risks and dependencies before starting a complex software feature?

The best way to analyze risks and dependencies is deploying a Risk Analyst role within an expert planning team to actively challenge proposals. This adversarial review uncovers failure modes and produces a structured plan with explicit risks and dependencies.

Why should I use a multi-role planning team instead of a single-pass architecture design?

You should use a multi-role planning team because adversarial review improves robustness for complex features. While single-pass architecture design may miss failure modes, parallel specialist roles surface trade-offs and validate proposals through active challenge.