---

name: planning-inventory description: Scans and reports all planning-related components across marketplace bundles allowed-tools:

• Read
• Bash

---

Planning Inventory Skill

Provides a unified view of all planning-related components across the marketplace, including core planning infrastructure and derived components in domain bundles.

Purpose

Planning-related components are distributed across bundles:

This skill provides a single command to discover all planning components.

Note: pm-dev-java and pm-dev-frontend no longer contain planning-specific components. The thin agent architecture in pm-workflow loads domain skills dynamically via config.toon.

When to Use This Skill

Activate this skill when you need to:

• Get a complete inventory of planning-related components
• Understand the planning component ecosystem
• Validate planning system integrity
• Generate reports on planning capabilities

Workflow

Step 1: Execute Planning Inventory Scan

Run the planning inventory scanner script:

Script: pm-workflow:planning-inventory

Copypython3 .plan/execute-script.py pm-workflow:planning-inventory:scan-planning-inventory scan

Step 2: Parse and Return Results

The script outputs JSON organized into core and derived categories.

Script Parameters

--format (optional)

Output format. Default: full

Examples:

Copypython3 .plan/execute-script.py pm-workflow:planning-inventory:scan-planning-inventory scan --format full
python3 .plan/execute-script.py pm-workflow:planning-inventory:scan-planning-inventory scan --format summary

--include-descriptions (optional flag)

When specified, includes description fields from YAML frontmatter.

Copypython3 .plan/execute-script.py pm-workflow:planning-inventory:scan-planning-inventory scan --include-descriptions

Output Format

Full Format

Copy{
  "patterns": ["plan-*", "manage-*", "*-workflow", "*-task-plan", "*-solution-outline", "*-plan-*"],
  "bundles_scanned": ["pm-workflow", "pm-plugin-development"],
  "core": {
    "bundle": "pm-workflow",
    "agents": [{"name": "plan-init-agent"}, {"name": "solution-outline-agent"}, {"name": "task-plan-agent"}, {"name": "task-execute-agent"}],
    "commands": [...],
    "skills": [...],
    "scripts": [...]
  },
  "derived": [
    {
      "bundle": "pm-plugin-development",
      "agents": [],
      "skills": [{"name": "plugin-task-plan"}, {"name": "plugin-solution-outline"}, {"name": "plugin-plan-implement"}]
    }
  ],
  "statistics": {
    "core": {"agents": 4, "commands": 4, "skills": 20, "scripts": 12, "total": 40},
    "derived": {"bundles": 1, "agents": 0, "skills": 3, "total": 3},
    "total_components": 43
  }
}

Summary Format

Copy{
  "core_bundle": "pm-workflow",
  "core_components": [
    {"type": "skills", "names": ["plan-init", "plan-execute", "plan-finalize", ...]},
    {"type": "agents", "names": ["plan-init-agent", "solution-outline-agent", "task-plan-agent", "task-execute-agent"]},
    {"type": "commands", "names": ["task-implement", "plan-manage", "plan-execute", "pr-doctor"]}
  ],
  "derived_bundles": [
    {"bundle": "pm-plugin-development", "agents": [], "skills": ["plugin-task-plan", "plugin-solution-outline", "plugin-plan-implement"]}
  ],
  "statistics": {...}
}

Component Categories

Core Components (pm-workflow bundle)

Thin Agents (4 generic agents that load domain skills dynamically):

• plan-init-agent - Initialize plan, detect domains
• solution-outline-agent - Create deliverables
• task-plan-agent - Create tasks from deliverables
• task-execute-agent - Execute single task

Derived Components (domain bundles)

Note: pm-dev-java and pm-dev-frontend no longer have planning-specific components. Domain skills are loaded by thin agents via config.toon.

Dependencies

This skill uses pm-plugin-development:tools-marketplace-inventory internally with:

• --bundles: Filtered to planning-related bundles
• --name-pattern: Filtered to planning-related patterns

Non-Prompting Requirements

This skill is designed to run without user prompts. Required permissions:

Script Execution:

• Bash(bash:*) - Bash interpreter
• Script permissions synced via /tools-setup-project-permissions

Script only reads marketplace directory structure (no writes).