skills.rest
yuchenbigpen1
yuchenbigpen1COMMUNITY
Explore all skills by this author →
GitHub

prompt-improver

Clarifies vague business requests through 1-3 targeted questions with concrete options.

4|1|Updated Feb 8, 2026
Search Tags:#requirements#clarification#prompt#business-context#non-technical#context-gathering
One-click install
npx skills add https://github.com/yuchenbigpen1/normies --skill prompt-improver-yuchenbigpen1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prompt-improver
Source: https://github.com/yuchenbigpen1/normies/tree/main/packages/shared/assets/workspace-template/skills/prompt-improver
Command: npx skills add https://github.com/yuchenbigpen1/normies --skill prompt-improver-yuchenbigpen1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps teams move from vague, ambiguous requests to clear, actionable requirements by guiding users to articulate goals, constraints, and context with focused questions.

Core Features & Use Cases

  • Guiding a 1–3 question clarification flow in plain language to surface essential business context.
  • Providing concrete, multiple-choice options to minimize confusion and decision fatigue.
  • Use Case: When a project request is unclear (build vs buy, scope, success criteria), the skill generates a crisp context for the next planning steps.

Quick Start

Ask 1–3 focused, business-relevant questions to elicit missing details and collect responses before proceeding.

Frequently Asked Questions about prompt-improver

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

FAQPage Schema
How do I clarify vague business requirements before starting a project?▼

Clarifying vague business requests involves asking 1-3 targeted, business-relevant questions to surface essential context. This approach uses plain language and concrete options to help teams articulate goals, constraints, and success criteria before proceeding with planning.

What is the best way to gather missing context for unclear project requests?▼

Gathering missing context uses a structured clarification flow that asks 1-3 targeted questions with concrete options. This method surfaces critical details like scope and success criteria, transforming ambiguous project requests into structured context for immediate planning.

Can I use structured questions to turn ambiguous requests into actionable requirements?▼

Yes, using structured, business-relevant questions with concrete options effectively turns ambiguous requests into actionable requirements. This plain-language approach extracts essential goals and constraints without confusing non-technical stakeholders.

How do I reduce decision fatigue when gathering business context from stakeholders?▼

Reduce decision fatigue during context gathering by limiting clarification to 1-3 focused questions with concrete, multiple-choice options. This minimal approach prevents overwhelming stakeholders while extracting essential business parameters.

When should I use a clarification flow for business requests?▼

Use a clarification flow when a user's objective is unclear or critical business context is missing. It is specifically designed for ambiguous requests involving scope, build versus buy decisions, or undefined success criteria.

Related Skills

Explore More Personal & Entrepreneur Skills→
OpenAEC-FoundationOpenAEC-Foundation
163

frappe-agent-interpreter

Interpret vague ERPNext/Frappe requests into technical specifications with skill mappings.

Official
Advanced
SumitvedpathakSumitvedpathak

speckit-tasks

Generate dependency-ordered task lists from design artifacts.

Community
Intermediate
rafazshrafazsh

project-planner

Break down complex projects into tasks, timelines, dependencies, and milestones.

Community
Intermediate
tjesperstjespers
1

speckit-constitution-primer

Generate grounded directional prompts for /speckit.constitution from project context.

Community
Advanced