shape

Evaluate project complexity and recommend multi-agent scoping tracks.

1|2|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/AesopScott/central --skill shape-aesopscott
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shape
Source: https://github.com/AesopScott/central/tree/main/local-client/app-content/mindshare/skills/archive/shape
Command: npx skills add https://github.com/AesopScott/central --skill shape-aesopscott

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

The Shape skill addresses the early complexity and confusion often faced at the beginning of MAPS (Multi-Agent Planning and Systems) projects, helping to decide between scope-first, single-agent, or multi-agent pathways.

Core Features & Use Cases

  • Workflow Scoping: Assist with initial scoping by understanding the complexity and needs of a system, ensuring it is approached correctly from the outset.
  • Research & Recommendations: Provides research and recommendations based on the project foundation, external sources, and guidelines, including role advice.
  • Technical Analysis: Includes the use of BPMN, team topology analysis, and multi-agent orchestration frameworks for comprehensive understanding and recommendation.

Quick Start

Use the shape command at M1 stage of a project to kick off scoping the project, starting by assessing if a track like 'Unknown/Scope First', 'Single-Agent/APS', or 'Multi-Agent/MAPS' is needed based on your current context.

Frequently Asked Questions about shape

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

FAQPage Schema
How do I scope a multi-agent planning system and decide between single-agent and multi-agent tracks?

Multi-agent planning system scoping evaluates project complexity, role assignments, and coordination requirements to recommend the correct track. It assesses your current context to determine if a scope-first, single-agent, or multi-agent pathway is needed for your project foundation.

What is the best way to use BPMN and team topology for multi-agent orchestration analysis?

Multi-agent orchestration analysis uses BPMN and team topology to evaluate project complexity and coordination requirements. This technical analysis provides comprehensive understanding and role recommendations based on structured research sources and multi-agent orchestration principles.

How do I start workflow scoping for a complex multi-agent system at the beginning of a project?

Workflow scoping for multi-agent systems starts at the M1 project stage by assessing complexity and system needs. You can execute the shape command to kick off scoping and evaluate whether an Unknown/Scope First, Single-Agent/APS, or Multi-Agent/MAPS track is required.

Do I need Python to run multi-agent project scoping and workflow analysis?

Python is required for multi-agent project scoping and workflow analysis. The skill uses Python for scripting and data handling to automate the evaluation of project complexity, role assignments, and coordination requirements.

When should I not use a multi-agent system architecture for my project?

A multi-agent system architecture is not recommended when initial scoping determines the project complexity does not require multi-agent coordination. The skill evaluates your context to redirect simpler projects to a single-agent or scope-first pathway instead of multi-agent orchestration.