Loading…
Turns an accepted plugin or component concept into a concrete component inventory — which skills, agents, commands, and hooks to build, how many, and how much content depth each needs (Minimal/Standard/Rich, reusing this plugin's own 80% Rule and skill-category vocabulary rather than a new rubric). Use when the user asks to "plan the architecture", "decide what components I need", "plan this plugin's structure", or has an accepted plugin-ideation Concept Card or plugin-conception Conception Brief ready for the next step. Produces a component inventory and depth plan, not designed components — see the matching Design skill (skill-development, agent-development, command-development, hook-development, rule-development) for that.
plugin-planning is an agent skill entry in ChatHome Skills, sourced from GitHub Skill Search and scored 58/100. # Plugin Planning Turns an accepted concept into a concrete build list: which components, how many, and how much content depth each one needs — before any singl. As an agent skill, it packages a reusable instruction set that AI coding agents such as Codex and Claude Code can load to perform this task without hand-written glue code. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding plugin-planning to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.
codex skill install AndreHahm/andres-cc-marketplaceReview the upstream source before running this command.
Scan coverage: Install metadata and the indexed document body.
Automated signals from install metadata and a bounded skill body — not a full code security audit and not a recursive source or dependency review.
# Plugin Planning Turns an accepted concept into a concrete build list: which components, how many, and how much content depth each one needs — before any single component is desig