Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

mastra-planning

Étoiles3

Forks0

Mis à jour9 juillet 2026 à 19:24

Strategic planning and team orchestration for Mastra development - analyzes tasks, designs team compositions, creates execution plans, and coordinates agent splits

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

artsmc

artsmc/claude-dev-agents

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

3 fichiers

SKILL.md

readonly

name	mastra-planning
description	Strategic planning and team orchestration for Mastra development - analyzes tasks, designs team compositions, creates execution plans, and coordinates agent splits

Mastra Planning & Team Orchestration

Strategic planner that analyzes Mastra development tasks, classifies complexity, selects optimal team compositions, and creates structured execution plans with task dependencies. Routes to the right specialized Mastra skills and agents.

Usage

/mastra-planning

Provides context for:

Domain detection (agents, workflows, RAG, memory, evals, streaming, deploy, MCP, workspace)
Complexity classification (Level 1-3)
Team composition templates (7 pre-built templates)
Task breakdown with parallel execution groups
Skill injection into agent prompts
Decision framework for choosing patterns
Integration with all 10 Mastra skills

Plus depuis ce dépôt

même dépôt

start-phase-execute

artsmc/claude-dev-agents

Structured task execution with quality gates, parallel waves, and pm-db tracking — solo or with multi-agent teams (--team). Use this skill when the user wants to execute a task list, run implementation tasks, start building a feature from a plan, run tasks in parallel with a team of agents, or says things like 'execute these tasks', 'start building', 'run the implementation', 'execute the plan', 'execute with a team', or 'start phase execute'. Also triggers on '/start-phase execute' and '/start-phase-execute-team' commands.

2026-07-093

architecture-quality-assess

artsmc/claude-dev-agents

Assess and score codebase architecture health — layer separation, SOLID compliance, module coupling (FAN-IN/FAN-OUT), circular dependencies, drift from documented patterns. Use whenever the user asks to assess/review/grade architecture quality, wants an architecture score, or asks how healthy the codebase's architecture is. Analysis-only report + refactoring tasks; for docs-vs-code drift use document-hub-analyze.

2026-07-093

code-duplication

artsmc/claude-dev-agents

Deep analysis of codebase for code duplication. Detects exact, structural, and pattern-level duplicates, generates comprehensive reports with refactoring suggestions and metrics.

2026-07-093

diagnose-from-raw-symptom

artsmc/claude-dev-agents

Use when Mark reports a bug by pasting a raw artifact with little or no prose — a stack trace, an HTTP request/response trace (URL + method + status like 500/403/404/502), a console/React/Prisma error, a ChunkLoadError, a shell error, or a screenshot of a visual defect — or when he says things like 'still failing', 'clicking X does nothing', 'no inline editor on the rendered page', 'do we have local postgres/pgvector?', or 'identify the true error'. This is the front-to-back debugging procedure — extract the trigger and reproduction from terse input, probe whether the underlying plumbing even exists, localize by contrasting known-good vs broken, and drive to a durable root cause rather than a workaround. Reach for this BEFORE proposing any fix.

2026-07-093

document-hub-analyze

artsmc/claude-dev-agents

Deep analysis of codebase vs documentation alignment (cline-docs/). Detects drift, identifies undocumented code, extracts missing glossary terms, and provides actionable recommendations without making changes. Use this skill when the user asks "are the docs up to date", "check documentation quality", "what's missing from the docs", or wants a read-only audit before deciding what to update. For actually making changes, use document-hub-update instead.

2026-07-093

document-hub-initialize

artsmc/claude-dev-agents

Bootstrap a new project's documentation hub by creating the four core documentation files (systemArchitecture.md, keyPairResponsibility.md, glossary.md, techStack.md) with initial content based on codebase analysis.

2026-07-093

Exécutez n'importe quel Skill en un clic