request-decomposition-agent

Decompose natural language infrastructure requirements into structured CMP sub-requests.

15|6|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/CloudChef/atlasclaw-providers --skill request-decomposition-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: request-decomposition-agent
Source: https://github.com/CloudChef/atlasclaw-providers/tree/main/providers/SmartCMP-Provider/skills/request-decomposition-agent
Command: npx skills add https://github.com/CloudChef/atlasclaw-providers --skill request-decomposition-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Decomposes free-form infrastructure or application requirements into structured, reviewable CMP sub-requests for safer planning and human-in-the-loop fulfillment.

Core Features & Use Cases

  • Converts descriptive needs into a set of CMP catalog sub-requests mapped to available services.
  • Validates inputs, enforces orchestration rules, and returns draft or review-ready outputs.
  • Generates a decomposition plan with resolved and unresolved fields for operator review, enabling manual follow-up when needed.

Quick Start

Describe your infrastructure or application needs in natural language and let the agent decompose them into structured, reviewable CMP sub-requests.

Frequently Asked Questions about request-decomposition-agent

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

FAQPage Schema
How do I decompose natural language infrastructure requirements into CMP catalog requests?

Decomposing natural language infrastructure requirements into CMP catalog requests is achieved by parsing descriptive needs, validating inputs, and mapping them to available CMP services to generate structured sub-requests for human-in-the-loop review.

What is the best way to split free-form application requirements into reviewable sub-requests?

Splitting free-form application requirements into reviewable sub-requests is done by applying orchestration rules and validation to natural language descriptions, returning a structured decomposition plan with resolved and unresolved fields for operator follow-up.

Can I use natural language to automate CMP request orchestration?

Automating CMP request orchestration with natural language is supported by converting descriptive infrastructure needs into structured sub-requests, imposing validation, and discovering CMP catalog items to produce a review-ready decomposition plan.

Does the decomposition plan support manual follow-up for unresolved fields?

The decomposition plan supports manual follow-up by returning draft or review-ready outputs that explicitly separate resolved and unresolved fields, enabling operators to safely perform manual follow-up during human-in-the-loop fulfillment.

Why does request decomposition impose validation on infrastructure requirements?

Request decomposition imposes validation on infrastructure requirements to enforce orchestration rules, ensure inputs correctly map to discovered CMP catalog items, and generate safer, structured sub-requests suitable for operator review.