skills.rest
Ascenseurs-Menetrey-SA
Ascenseurs-Menetrey-SAOFFICIAL
Explore all skills by this author →
GitHub

plan-with-team

Convert feature requests into multi-agent implementation plans with YAML frontmatter.

Updated Aug 23, 2026
Search Tags:#implementation planning#spec generation#task dependencies#multi-agent orchestration#team workflow#project blueprint#validation workflow
One-click install
npx skills add https://github.com/Ascenseurs-Menetrey-SA/amsa-claude-skills --skill plan-with-team
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-with-team
Source: https://github.com/Ascenseurs-Menetrey-SA/amsa-claude-skills/tree/main/plan-with-team
Command: npx skills add https://github.com/Ascenseurs-Menetrey-SA/amsa-claude-skills --skill plan-with-team

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the challenge of turning a user request into a structured, build-ready implementation roadmap by coordinating multiple agents while keeping the output strictly planning-focused.

Core Features & Use Cases

  • Detailed implementation blueprint: Produces a complete specification document saved as a markdown plan in specs/ for developers to follow.
  • Multi-agent task orchestration (Team + Tasks): Translates requirements into an execution-ready task list with dependencies, owners, and validation steps.
  • Input-driven planning: Uses PROMPT_UTILISATEUR (required) and optional PROMPT_ORCHESTRATION to set scope, granularity, and team strategy.

Quick Start

Ask the skill: "Plan the implementation for: <your feature/problem>, with orchestration guidance: <optional team strategy>."

Frequently Asked Questions about plan-with-team

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

FAQPage Schema
How do I generate a multi-agent implementation plan from a feature request?▼

A multi-agent implementation plan is generated by submitting a required user prompt detailing the feature request, alongside optional orchestration guidance for team strategy, which the skill translates into a structured execution blueprint.

How does task dependency ordering work for phased software engineering execution?▼

Task dependency ordering for phased execution works by translating project requirements into an execution-ready task list that sequences steps, assigns owners, and defines validation workflows across team members.

Can I use this to write code and deploy my project blueprint?▼

No, you cannot use this to write code or deploy. The workflow is strictly planning-focused, meaning it validates inputs and outputs a specification document into the specs directory without performing any coding.

What is the required input format for spec generation workflows?▼

Spec generation requires YAML frontmatter metadata and a mandatory user prompt describing the feature request. An optional orchestration prompt can also be included to define granularity and team workflow strategy.

Where are the generated project blueprints saved for developers?▼

Generated project blueprints are saved as markdown specification documents within the specs directory, using kebab-case plan filenames to ensure developers can easily locate and follow the build-ready plans.

Related Skills

Explore More Software Engineering Skills→
jshsakurajshsakura
22

qa-expert

Define risk-based test scope and acceptance criteria for software releases.

Community
Advanced
kngender5kngender5

kanban-orchestrator

Route Kanban tasks to agents based on profiles and dependencies.

Community
Advanced
artsmcartsmc

start-phase-execute-team

Coordinate parallel task execution for multi-agent teams across start-phase workflows.

Community
Advanced
cq112233cq112233
21

workflow-runner

Execute multi-agent YAML workflows by parsing task dependencies and role-based instructions.

Community
Advanced