Skip to content
Back to skills

Decompose And Or Goal

ASecurity

Recursively decompose a goal into an AND/OR DAG whose leaves are executable or testable subgoals.

  • 499 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 24, 2026
researchgonode

Security analysis

A100/100

Scanned September 24, 2026

npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill decompose-and-or-goal --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Decompose And Or Goal?

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

Security grade badge for Decompose And Or Goal
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-decompose-and-or-goal/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-decompose-and-or-goal)

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: decompose-and-or-goal
description: "Recursively decompose a goal into an AND/OR DAG whose leaves are executable or testable subgoals."
---

# decompose-and-or-goal

## Purpose

Recursively decompose a goal into an AND/OR DAG whose leaves are executable or testable subgoals.

## Input contract

```yaml
required: [top_goal, constraints]
optional: [actor_profile, obstacle_report, existing_subgoals]
constraints: [branch semantics, dependencies, and leaf criteria must be explicit]
```

## Procedure

1. Split the goal into necessary AND conditions and alternative OR paths.
2. Recurse until each leaf has an observable result or executable action.
3. Attach actors, dependencies, constraints, and unresolved feasibility to each branch.
4. Preserve shared subgoals as DAG nodes rather than duplicating them.

If the AND/OR decomposition is complete enough to test necessity and coverage, consider `validate-goal-tree` as the next tactic.

## Output contract

```yaml
produces: [goal_dag, branch_semantics, executable_leaves, dependency_edges, feasibility_questions]
delta_fields: [findings, hypothesis_updates, uncertainties, open_questions]
```

## Quality gates

- Every leaf traces to the top goal.
- AND/OR labels and dependency directions are unambiguous.
- Cycles and duplicate shared nodes are flagged.

## Failure and counterexamples

Do not split prose into labels without changing testability, and do not treat alternatives as simultaneous requirements.

## Provenance map

- `resolved: north-star-crystallization-and-or-decompose`

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…