skills.rest
matt-riley
matt-rileyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

reverse-prompt

Translate rough user asks into repository-grounded execution briefs.

1|1|Updated May 3, 2026
Search Tags:#workflow#planning#prompt-engineering#repository-context#reverse-prompt#execution-brief
One-click install
npx skills add https://github.com/matt-riley/agent-skills --skill reverse-prompt-matt-riley
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reverse-prompt
Source: https://github.com/matt-riley/agent-skills/tree/main/skills/reverse-prompt
Command: npx skills add https://github.com/matt-riley/agent-skills --skill reverse-prompt-matt-riley

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps convert rough, ambiguous user requests into repository-grounded execution briefs that can be acted on with minimal back-and-forth, reducing miscommunication and speeding up planning.

Core Features & Use Cases

  • Generates precise, repo-grounded briefs from vague asks
  • Helps determine scope, constraints, deliverables, and validation criteria
  • Supports mode routing between rewrite-and-return and rewrite-and-proceed for safe execution

Quick Start

Provide a rough user request and let the skill generate a repo-grounded brief ready for planning or execution.

Frequently Asked Questions about reverse-prompt

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

FAQPage Schema
How do I convert vague feature requests into clear execution plans for my codebase?▼

To convert vague requests into execution plans, you ground the rough ask in repository context to produce a self-contained brief specifying goal, scope, constraints, deliverables, and validation criteria.

What is a repo-grounded execution brief and when do I need one?▼

A repo-grounded execution brief is a reusable planning document derived from repository context that defines scope and deliverables, needed when rough asks require structured clarification before implementation.

How do I write a prompt engineering brief that sets clear project constraints?▼

You write a prompt engineering brief by translating rough requests into a structured document that explicitly defines project scope, constraints, deliverables, validation methods, and recommended next phases.

Can I generate a planning brief without automatically starting implementation?▼

Yes, you can generate a planning brief without execution by using a rewrite-and-return mode that produces a self-contained brief and avoids performing any actual work unless explicitly requested.

What's the best way to define validation criteria for ambiguous development tasks?▼

The best way to define validation criteria for ambiguous tasks is routing the request through a reverse-prompt process that grounds the brief in repository context and clarifies expected deliverables.

Related Skills

Explore More Software Engineering Skills→
hujianbesthujianbest
51

hf-frame

Define project scope and risk during HarnessFlow's Frame stage.

Community
Intermediate
XWIlluDeluXWIlluDelu

humanizer

Rewrite AI-generated text to sound natural and human.

Community
Intermediate
GMNAPIGMNAPI

feature-planner

Analyze feature documentation and generate phase-by-phase implementation plans.

Community
Advanced
Owl-ListenerOwl-Listener
2.0k

design-brief

Define and document a design brief with problem space, audience, constraints, and success criteria.

Community
Intermediate