Skip to content
TrustedSkillsbeta
Back to all skills

Planning

Checked
binhmuc·vlatest·productivity

Generates detailed, actionable plans to achieve complex goals, considering resource constraints and potential obstacles.

Repository

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 binhmuc/autobot-review --skill planning -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

binhmuc

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 binhmuc/autobot-review at a2b4913a35.

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

Commit
a2b4913a35
Manifest
.claude/skills/planning/SKILL.md
Scanned
6 files, 560 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 generates detailed, actionable technical implementation plans to achieve complex goals. It leverages research, codebase analysis, solution design, and comprehensive documentation to create these plans, always adhering to YAGNI, KISS, and DRY principles. The output is a plan file path accompanied by a summary, ensuring the plan is self-contained with necessary context and potentially including code snippets or pseudocode for clarification.

When to use it

This skill is helpful when:

  • Planning new feature implementations
  • Architecting system designs
  • Evaluating technical approaches
  • Creating implementation roadmaps
  • Breaking down complex requirements
  • Assessing technical trade-offs

Key capabilities

  • Research and Analysis: Conducts research and analysis, optionally using provided reports.
  • Codebase Understanding: Analyzes existing codebases, potentially leveraging pre-existing "scout" reports.
  • Solution Design: Creates architectural and implementation designs.
  • Plan Organization: Organizes plans with a specific directory structure including research, reports, scout information, the main plan document (plan.md), and phase-specific documents.
  • Output Standards: Adheres to defined output standards for clarity and actionability.
  • Active Plan Management: Tracks and manages active vs. suggested plans using session state.

Example prompts

  • "Create a plan for implementing user authentication."
  • "Generate an implementation roadmap for migrating our database."
  • "What's the best approach to integrating with the new payment gateway? Create a plan outlining the steps."

Tips & gotchas

  • The skill does not implement code; it only creates plans.
  • Pay attention to the "Plan:" or "Suggested:" context injected into prompts, as this indicates whether an existing plan should be used or if a new one needs to be created.
  • Reports are stored in specific locations depending on whether they relate to an active or suggested plan.