What do I need to use Desk Research Sprint?

The real question behind the topic; The timebox; What's already known; The output's destination.

Is Desk Research Sprint free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Desk Research Sprint

Q: How do I know the Desk Research Sprint output is good?

The skill verifies itself against its own quality checks: Every question has a good-enough bar set before searching; Sources were planned by question type, not generic-searched; Findings were captured at read-time into the one doc; Questions stopped at their bars; the timebox ended the sprint.

🔵 Stable🕐 updated 2026-07-19 🔷 SkillSpec L3 pm-cowork

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.

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

What to give it

▸The real question behind the topic — "research the CRM market" hides "which three CRMs should we demo?" — the decision the research feeds defines done ([what-to-ask](../what-to-ask/SKILL.md) energy, applied to research)

▸The timebox — two hours and two days are different sprints; the question count and depth budget follow

▸What's already known — prior research, existing beliefs to test (stated as hypotheses, so confirmation bias gets a fence)

▸The output's destination — a recommendation memo? A brief for the boss? The synthesis writes toward its reader from the start

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓Every question has a good-enough bar set before searching

✓Sources were planned by question type, not generic-searched

✓Findings were captured at read-time into the one doc

✓Questions stopped at their bars; the timebox ended the sprint

✓Gaps are labeled as findings, never papered over

⚠️ What it refuses to do

Do not research a topic — decompose to questions or inherit forty tabs

Do not read without capturing — the second read is the sprint's biggest hidden cost

Do not keep researching past the bar — good-enough was defined for exactly this moment

Do not present echoed sources as confirmation — the triangulation rules ride along

Do not end without the synthesis — captured-but-unsynthesized research is tabs with better formatting

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="desk-research-sprint"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Desk Research Sprint is one of 750 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog