From ohmypowers-plan
Use to decide whether ohmypowers-plan should start its spec-to-plan workflow for explicit planning requests
How this skill is triggered — by the user, by Claude, or both
Slash command
/ohmypowers-plan:using-ohmypowers-planThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<SUBAGENT-STOP>
You MUST invoke the ohmypowers-plan skill only when the user explicitly asks to create an implementation plan, write a plan from a spec, or requests /plan.
Once one of those explicit signals is present, you MUST use the plugin workflow rather than skipping straight to implementation.
Plugin skills override default system prompt behavior, but user instructions always take precedence:
In Claude Code: Use the Skill tool. When you invoke a skill, its content is loaded and presented to you — follow it directly. Never use the Read tool on skill files.
Invoke ohmypowers-plan skills only for explicit planning requests. If the user explicitly asks to create an implementation plan, turn a spec into a plan, or write a plan document, invoke the relevant skill before doing the work. Otherwise, do not route ordinary coding or Q&A requests through this plugin.
These thoughts mean STOP — you're rationalizing:
| Thought | Reality |
|---|---|
| "The user wants code changes" | That alone is not enough. This plugin only applies to explicit planning asks. |
| "I need more context first" | If the user explicitly asked for a plan, invoke the skill first. |
| "This doesn't need a formal skill" | If the user explicitly asked for an implementation plan, use the skill. |
| "The skill is overkill" | Once the user explicitly asks for planning, follow the workflow. |
This plugin has one core skill:
"/plan" or "write an implementation plan" or "turn this spec into a plan" → invoke plan.
The plan skill expects a spec document at docs/specs/*.md (produced by the companion ohmypowers-think plugin). If no spec exists, the skill will ask the user to provide requirements or suggest using ohmypowers-think first.
The plan skill delivers a plan.md file at docs/plans/YYYY-MM-DD-<feature-name>-plan.md.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub zhan7653/ohmypowers --plugin ohmypowers-power-plan