Skip to content
TrustedSkillsbeta
Back to all skills

Epic Breakdown Advisor

Checked
deanpeters·vlatest·productivity

This skill provides a structured process for analyzing complex problems ("epics") and identifying actionable steps to achieve desired outcomes, boosting productivity & clarity.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add deanpeters/product-manager-skills --skill epic-breakdown-advisor -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

deanpeters

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned deanpeters/product-manager-skills at cfcb697f14.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
1 file, 678 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The Epic Breakdown Advisor skill helps users decompose large, complex projects (epics) into smaller, manageable tasks. It can suggest subtasks based on the epic description and identify dependencies between them. This allows for better planning, estimation, and execution of larger initiatives by breaking them down into actionable steps.

When to use it

  • You have a large project or "epic" that feels overwhelming and you need help structuring it.
  • You're struggling to estimate the effort required for a significant piece of work.
  • You want to identify potential dependencies between different parts of a project before starting.
  • You’re looking for ways to improve task clarity and assignment within a larger initiative.

Key capabilities

  • Epic decomposition: Breaks down large epics into smaller tasks.
  • Subtask suggestion: Proposes relevant subtasks based on epic descriptions.
  • Dependency identification: Identifies potential dependencies between tasks.

Example prompts

  • "Break down the 'Implement User Authentication' epic into smaller tasks."
  • "What are some possible subtasks for an epic called 'Redesign Customer Checkout Flow'?"
  • "Given the epic 'Integrate with Third-Party Payment Provider', identify potential dependencies between tasks."

Tips & gotchas

The quality of the breakdown depends heavily on a clear and detailed description of the initial epic. Providing context and background information will improve the accuracy and relevance of suggested subtasks.