mcpField
D
ds-sharpen

ds-sharpen

github.com/aicodekingAgent workflows263436 installsUpdated 2w ago
Repository

About ds-sharpen

ds-sharpen is a skill for refining a task prompt before work begins. It clarifies the request, identifies useful source material and verification methods, then presents a tighter prompt and any choices that remain open.

Key features

  1. 01Restates the request and underlying problem
  2. 02Identifies raw materials and methods
  3. 03Names an external verification check
  4. 04Rewrites the prompt without expanding scope
  5. 05Optionally stress-tests risky plans

Use cases

  1. 01Clarifying an ambiguous task before execution
  2. 02Defining evidence to verify a proposed result
  3. 03Testing a risky plan with independent agents

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/aicodeking/deepseek-stack --skill ds-sharpen

After installing, type/ds-sharpenin Claude Code to confirm it loaded.

Details

From the project README

ds-sharpen

A sharper prompt saves more tokens than any loop. Fix the ask before doing the work.

Steps

  1. Restate, in your own words, what the user wants and the problem behind it. Keep it to three sentences. If you cannot, ask one question.
  2. Deepen the task. Answer briefly:
    • What would a top professional do here that the user did not ask for?
    • What raw material would they start from, instead of a summary?
    • What methods and tools would they use?
    • What outside check, not you or the user, would show the result is right? Name a command, test, metric or source.
  3. Rewrite the prompt to ask for exactly that. Keep it no bigger in scope. Leave choices that belong to the user open and list them.
  4. Optional stress test, when the plan is risky or the user asks. Spawn two or three subagents with fresh context and give each the plan and the goal. Ask each to break it and back every finding with a run: a failing test, a probe script, or real command output. Drop findings with no run behind them.
  5. Present the restatement, the rewritten prompt, open choices, and any surviving findings with their commands and output.

Stop when

  • The user accepts or edits the rewritten prompt.
  • Or the stress test returns. Do not loop it more than once without the user.

Rules

  • Deeper, not bigger. Do not add features.
  • Do not apply fixes from the stress test. Report them.
  • A finding without output is an opinion. Leave it out.

Comments

Markdown supported