Skip to content
Back to skills

Propose Subgoal Decomposition Plans

ASecurity

Propose multiple subgoal decomposition plans for the current theorem using the information already gathered. Use when enough information has been collected from examples, counterexamples, search results, and previous failures to break the problem into several materially different plans.

  • 389 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 5, 2026
ai-agentsgo

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 5, 2026

npx -y skills add frenzymath/Danus --skill propose-subgoal-decomposition-plans --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Propose Subgoal Decomposition Plans?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Propose Subgoal Decomposition Plans
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/frenzymath-propose-subgoal-decomposition-plans/badge)](https://www.skillsdirectory.com/skills/frenzymath-propose-subgoal-decomposition-plans)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: propose-subgoal-decomposition-plans
description: Propose multiple subgoal decomposition plans for the current theorem using the information already gathered. Use when enough information has been collected from examples, counterexamples, search results, and previous failures to break the problem into several materially different plans.
---

# Propose Subgoal Decomposition Plans

Use this skill when the agent has enough context to propose several viable decomposition plans.

## Input Contract

Read:

- the current target theorem or branch goal
- relevant `immediate_conclusions`, `toy_examples`, and `counterexamples`
- relevant `failed_paths` and `branch_states`
- recent search results and useful references from `events`

## Procedure

1. Gather the current information that materially constrains the problem: useful examples, failed claims, known obstructions, and relevant search results.
2. Propose materially different decomposition plans.
3. For each plan, state:
   - the main idea of the plan
   - the ordered subgoals
   - why this plan is plausible given the current information
   - which earlier failures or counterexamples it tries to avoid
4. Hand each plan to `$direct-proving` for a quick screening pass.

## Output Contract

Publish one plan per decomposition to global memory with `gm_add` (kind `plan`, a
judgment — `verifiable=false`): `claim` = the plan's goal + summary, `evidence` =
its motivation, plus these fields:

```json
{
  "plan_id": "...",
  "record_type": "decomposition_plan",
  "goal": "...",
  "plan_summary": "...",
  "subgoals": ["..."],
  "motivation": ["..."],
  "uses_information_from": {
    "examples": ["..."],
    "counterexamples": ["..."],
    "key_failures": ["..."],
    "search_results": ["..."]
  },
  "status": "proposed|screening|screened|selected|failed|solved",
  "branch_id": "optional"
}
```

Also note the new plan set in your local memory (`events`).

## Tools

- `gm_add` (publish the plan findings)
- `gm_search` (recall the examples/counterexamples/dead-ends the plans build on)
- `search_arxiv_theorems`

## Failure Logging

If the agent cannot yet propose meaningful decomposition plans, append an `events` record with:

- `event_type="decomposition_plans_not_ready"`
- the missing information
- the blockers that prevent proposing plans

Files in this skill

  • SKILL.md2.3 KB
  • agents/openai.yaml293 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.