sharpen-prompt

Rewrites ambiguous requests into precise briefs with explicit done-criteria and stated assumptions.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/dxiiren/project-skeleton --skill sharpen-prompt-dxiiren
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sharpen-prompt
Source: https://github.com/dxiiren/project-skeleton/tree/main/.claude/skills/sharpen-prompt
Command: npx skills add https://github.com/dxiiren/project-skeleton --skill sharpen-prompt-dxiiren

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Vague requests like "fix the forms" or "check everything" get claimed done on the wrong evidence, forcing two or three challenge rounds before the real work starts. This Skill converts any ambiguous ask into a five-line brief — objective, definition of done with live evidence, scope boundaries, execution shape, and stated assumptions — so the work matches the intent on the first pass. ## Core Features & Use Cases - Sharpened brief generation: Produces a five-line brief (Objective, Done when, Not doing, Shape, Assumed) and starts work immediately without blocking on confirmation. - Evidence-based done criteria: Forces the "Done when" line to name pasteable, live evidence (probe URLs, test runner summaries, rendered output) instead of "tests pass" or "it works". - Execution shape selection: Routes work into inline, report-only subagent, checkpointed batch, or codify-it shapes based on the request type. - Use Case: A developer says "add validation to the forms". The Skill rewrites it as a brief specifying the full form inventory with a count, a rejected submission shown on screen, edge cases pasted, and the assumption that only user-submittable forms are in scope — then proceeds. ## Quick Start Ask the assistant to sharpen this request before starting: "audit all the endpoints and fix the slow page".

Frequently Asked Questions about sharpen-prompt

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

FAQPage Schema
How do I turn a vague request into a clear task brief?

Run the sharpen-prompt flow before starting work: it prints a five-line brief covering objective, done-when evidence, scope exclusions, execution shape, and assumptions, then begins immediately. Corrections to a stated assumption cost one message instead of multiple challenge rounds.

What makes a good definition of done for a coding task?

A good done criterion names evidence that can be pasted, produced by exercising the running system — for example a probe URL returning 200, a Playwright run showing rendered output, or a test runner's summary line. "Tests pass" or "the build is green" are rejected as insufficient.

When should I not sharpen a prompt before starting?

Skip sharpening for genuinely unambiguous one-liners like "commit", "push", or "what's the branch". Applying the brief format to trivial requests adds the ceremony the technique is designed to remove.

How do I handle a request that could be read two different ways?

Pick the reading a careful colleague would choose, state it explicitly in the Assumed line, and proceed. Only ask a question when proceeding under the wrong reading would be unsafe or waste the whole task — and then ask exactly one question with the two readings as options.

What execution shape should large multi-item tasks use?

Large "do this for all N items" tasks use the checkpointed batch shape: maintain a progress ledger with one line per item, run in foreground chunks of about 20, and resume from the ledger on restart so an interrupted run costs minutes rather than hours.