Agent skill · Workflow & Productivity

desk-research-sprint

Run a timeboxed desk-research sprint that ends with an answer instead of forty tabs — the question decomposition, the source plan by question type, the capture discipline that prevents re-reading, and the stop rule that beats completionism. Use when asked research this market/tool/topic by Friday, I have two hours to get smart on X, structure my desk research, or I keep researching and never concluding. Produces the decomposed questions, the source plan, the capture format, and the timeboxed synthesis with confidence labels.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill desk-research-sprint --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: skills/desk-research-sprint/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Desk Research Sprint Skill Unstructured research expands to fill all available time and ends with tabs instead of answers — because "research X" was never converted into questions that can be *done*. The sprint fixes the shape: decompose into 3–5 answerable questions (each with what-good-enough-looks-like), plan sources by question type (market numbers, user sentiment, and technical claims live in different places), capture findings in one running doc *at reading time* (re-reading is the silent time-thief), and obey the stop rule — the timebox ends, the synthesis gets written from whatever's captured, gaps labeled honestly. ## What This Skill Produces - **The question set** — the vague topic decomposed into 3–5 answerable questions with good-enough bars - **The source plan** — per question: where answers of that type actually live, and the [source-triangulation](../source-triangulation/SKILL.md) depth it deserves - **The capture doc** — one running format: finding → source → confidence → which question it feeds - **The synthesis** — the answers at their earned confidence, the gaps named, the next-sprint questions if any ## Required Inputs Ask for these if not provided: - **The re

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Framework: The Sprint Rules
  4. Output Format
  5. The Questions
  6. Source Plan
  7. The Capture Doc (running)
  8. Synthesis
  9. Quality Checks
  10. Anti-Patterns
More from pm-claude-skills
All skills →
About this skill
What does the desk-research-sprint skill do?

Run a timeboxed desk-research sprint that ends with an answer instead of forty tabs — the question decomposition, the source plan by question type, the capture discipline that prevents re-reading, and the stop rule that beats completionism. Use when asked research this market/tool/topic by Friday, I have two hours to get smart on X, structure my desk research, or I keep researching and never concluding. Produces the decomposed questions, the source plan, the capture format, and the timeboxed synthesis with confidence labels.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill desk-research-sprint --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going