Loading…
Use for multi-file or multi-system changes, once a clear spec exists. Produces a task-broken-down plan written to the project's plans directory, and gets approval before code moves. Trigger on: "plan this out", "write a plan", "how would you approach". If the scope is 1-2 files, route directly to `subpowers-implement`. For read-only discovery or architectural tracing, route to `subpowers-explore`.
subpowers-plan is an agent skill entry in ChatHome Skills, sourced from GitHub Skill Search and scored 58/100. # Plan <directives> Translate the spec into a file-by-file plan before code moves. This file becomes the source of truth for the work, and the handoff record a. 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 subpowers-plan to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.
codex skill install ohiliazov/subpowersReview 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.
# Plan <directives> Translate the spec into a file-by-file plan before code moves. This file becomes the source of truth for the work, and the handoff record a session that has los