refine-prompt-plan
Iteratively review and revise a prompt plan until no new findings survive evaluation. Runs /review-prompt-plan, /evaluate-findings, /apply-findings, then re-runs itself until stable. Use when the user asks to \"refine the prompt plan\", \"refine this prompt plan\", \"iterate on the prompt plan\", \"tighten the prompt plan\", or \"improve the prompt plan\".
npx skills add majiayu000/claude-skill-registry --skill refine-prompt-plan --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Refine Prompt Plan Loop the prompt plan review pipeline over a prompt plan index and its shell files until no new findings are accepted. Writes back to the index and shell files in place. ## Task Tracking At the start of every invocation (including re-runs from Step 5), use `TaskCreate` to create a task for each step: 1. Resolve the prompt plan 2. Run `/review-prompt-plan` skill 3. Run `/evaluate-findings` skill 4. Run `/apply-findings` skill 5. Re-run `/refine-prompt-plan` skill if changed ## Step 1: Resolve the Prompt Plan Determine which prompt plan index to refine using these rules in order: 1. **Explicit path** — If an absolute or relative path was passed, use it 2. **Explicit slug** — If a slug was passed, resolve to `.turbo/prompt-plans/<slug>.md` 3. **Single file** — Glob `.turbo/prompt-plans/*.md`. If exactly one file exists, use it 4. **Most recent** — If multiple files exist, use the most recently modified 5. **Legacy fallback** — If `.turbo/prompt-plans/` does not exist but `.turbo/prompts.md` exists, use it 6. **Nothing found** — If no prompt plan exists, tell the user to run `/draft-prompt-plan` first and stop If multiple files exist and the most-recent choice is no
- Task Tracking
- Step 1: Resolve the Prompt Plan
- Step 2: Run /review-prompt-plan Skill
- Step 3: Run /evaluate-findings Skill
- Step 4: Run /apply-findings Skill
- Step 5: Re-run /refine-prompt-plan Skill if Changed
- Rules
What does the refine-prompt-plan skill do?
Iteratively review and revise a prompt plan until no new findings survive evaluation. Runs /review-prompt-plan, /evaluate-findings, /apply-findings, then re-runs itself until stable. Use when the user asks to \"refine the prompt plan\", \"refine this prompt plan\", \"iterate on the prompt plan\", \"tighten the prompt plan\", or \"improve the prompt plan\".
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill refine-prompt-plan --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.