Skip to content
TrustedSkillsbeta
Back to all skills

feature-planning

Checked
mhattingpete·v1.0.0·productivity·Apache-2.0

Break down feature requests into detailed, implementable plans with clear tasks. Use when user requests a new feature, enhancement, or complex change.

Install on your platform

Showing OpenClaw.

  1. 1

    Run this in your terminal

    terminal
    $

What we know about this skill

Publisher

mhattingpete

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 mhattingpete/claude-skills-marketplace at b5b34bcf4c.

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

Commit
b5b34bcf4c
Manifest
engineering-workflow-plugin/skills/feature-planning/SKILL.md
Scanned
2 files, 511 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

This skill decomposes high-level feature requests into actionable implementation plans. It breaks down requests for new features, enhancements, or complex changes into smaller, well-defined tasks suitable for development teams. The resulting plan includes a clear outline of steps needed to deliver the requested functionality.

When to use it

  • A product manager asks for "improved search functionality" and needs a detailed breakdown of what that entails.
  • A user requests a new integration with a third-party service, requiring a structured approach to development.
  • You need to estimate the effort required for a complex feature before assigning resources.
  • A stakeholder proposes a significant change to an existing product and you want to clarify the scope and steps involved.

Key capabilities

  • Breaks down feature requests into detailed tasks.
  • Creates implementable plans.
  • Clarifies requirements for development teams.

Example prompts

  • "Please create a feature plan for adding user profile pictures."
  • "Break down the request to 'improve reporting' into actionable steps."
  • "Develop a plan for integrating with the X API, including necessary tasks and considerations."

Tips & gotchas

The skill is most effective when provided with a clear description of the feature request. Vague or ambiguous requests may result in less detailed plans.