problem-decomposer

Identify and structure multi-subproblem tasks from mathematical modeling competition statements.

1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/Best6668/AMIS --skill problem-decomposer-best6668
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: problem-decomposer
Source: https://github.com/Best6668/AMIS/tree/main/skills/problem-decomposer
Command: npx skills add https://github.com/Best6668/AMIS --skill problem-decomposer-best6668

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to break down a complex competition problem into a set of explicit subproblems with clear goals, outputs, and required data, enabling parallel work and reliable planning.

Core Features & Use Cases

  • Phase-driven subproblem extraction and labeling with id, goal, deliverable, and required_data.
  • Dependency graph generation and topological ordering with indicators for independent, weak, and strong dependencies.
  • Artifact generation for downstream skills, including artifacts/problem_scope.json, artifacts/subproblem_candidates.json, and artifacts/problem_dependency_graph.json.

Quick Start

Run the Phase 1 script to extract and standardize problem scope from PROBLEM_BRIEF.md.

Frequently Asked Questions about problem-decomposer

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

FAQPage Schema
How do I decompose a complex mathematical modeling competition problem into solvable subproblems?

Decompose a complex mathematical modeling problem by extracting explicit and implicit subproblems, defining their dependencies, and generating a topologically ordered plan with modular outputs for parallel team execution.

What is topology-based problem decomposition for CUMCM and MCM competitions?

Topology-based problem decomposition for CUMCM and MCM analyzes subproblem dependencies to generate a topologically sound execution plan, categorizing relationships into independent, weak, and strong dependencies for reliable modeling workflows.

How do I generate a dependency graph for multi-subproblem modeling tasks?

Generate a dependency graph for multi-subproblem modeling tasks by identifying structural relationships between subproblems, ordering them topologically, and exporting the results into a structured problem_dependency_graph.json artifact.

Can I extract problem scope and subproblem candidates from a brief for mathematical modeling?

Extract problem scope and subproblem candidates from a brief by standardizing the input problem statement, labeling each subproblem with goals and deliverables, and outputting structured JSON artifacts for downstream stages.

What is the best way to structure multi-subproblem tasks for parallel modeling work?

Structure multi-subproblem tasks for parallel modeling by assigning unique IDs, required data, and deliverables to each subproblem, enforcing modular outputs and readiness constraints to support independent team workflows.

When should I not use an automated problem decomposition workflow for competition modeling?

Avoid automated problem decomposition workflows when a competition problem lacks clear structural dependencies or requires highly subjective interpretation, as topology-based ordering relies on definable relationships between explicit subproblems.