reprompt

Rewrite vague user requests into structured working specifications with goals and constraints.

3|1|Updated May 12, 2026
One-click install
npx skills add https://github.com/LumenWipe/lumenwipe --skill reprompt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reprompt
Source: https://github.com/LumenWipe/lumenwipe/tree/main/.claude/skills/reprompt
Command: npx skills add https://github.com/LumenWipe/lumenwipe --skill reprompt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill transforms vague or underspecified requests into clear working specifications, reducing ambiguity and helping ensure the intended outcome is addressed before execution.

Core Features & Use Cases

  • Structured Prompt Rewriting: Converts rough requests into a concise specification covering the goal, context, task, constraints, and success criteria.
  • Ambiguity Handling: Identifies uncertainties that could change the result and asks targeted clarification questions before proceeding.
  • Personalized Defaults: Uses an optional Stellar profile to incorporate preferred domains, scope, technology stacks, and tone.
  • Use Case: Give the Skill a loosely worded development request, and it will turn it into an actionable specification before handing the work to the appropriate implementation skill.

Quick Start

Use the reprompt skill to clarify and structure the following request before acting on it: help me improve my app.

Frequently Asked Questions about reprompt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I rewrite vague prompts into clear task specifications?

To rewrite vague prompts into clear task specifications, the skill restructures rough requests around goals, context, tasks, constraints, and success criteria to reduce ambiguity before execution.

What is ambiguity detection in prompt engineering?

Ambiguity detection in prompt engineering identifies uncertainties that could alter outcomes, prompting targeted clarification questions to resolve underspecified requests before proceeding with the task.

How do I convert rough development requests into actionable prompts?

You convert rough development requests into actionable prompts by structuring them into working specifications, applying personalization from a local profile to define scope, technology stacks, and tone.

Can I use a local profile to personalize prompt rewriting?

Yes, you can use an optional local profile to personalize prompt rewriting by incorporating preferred domains, scope, technology stacks, and tone into the generated working specifications.

When do I need to clarify requirements before handing off to implementation skills?

You need to clarify requirements before handing off to implementation skills when a user request is loosely worded or underspecified, ensuring the intended outcome is addressed before execution begins.