From ohmypowers-think
Use to decide whether ohmypowers-think should start its requirement-thinking workflow for explicit brainstorming, requirement clarification, or spec-writing requests
How this skill is triggered — by the user, by Claude, or both
Slash command
/ohmypowers-think:using-ohmypowers-thinkThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<SUBAGENT-STOP>
You MUST invoke the ohmypowers-think skill only when the user explicitly asks to brainstorm, think through requirements, clarify needs, write a spec, define acceptance criteria, or requests /think.
Once one of those explicit signals is present, you MUST use the plugin workflow rather than skipping straight to implementation or planning.
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-think skills only for explicit requirement-thinking requests. If the user explicitly asks to brainstorm, think through requirements, clarify needs, write a spec, or define acceptance criteria, 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 thinking/spec asks. |
| "I need more context first" | If the user explicitly asked to think/brainstorm, invoke the skill first. |
| "This doesn't need a formal skill" | If the user explicitly asked for brainstorming or a spec, use the skill. |
| "The skill is overkill" | Once the user explicitly asks for requirement thinking, follow the workflow. |
This plugin has one core skill:
"/think" or "help me think through this" or "write a spec" → invoke think.
The think skill delivers a spec.md file at docs/specs/YYYY-MM-DD-<feature-name>-spec.md.
This spec is the input for the companion plugin ohmypowers-plan, which turns specs into implementation plans.
npx claudepluginhub zhan7653/ohmypowers --plugin ohmypowers-power-thinkGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.