Skip to content

commandWorkflow

Research Topic

Researches a technical question and returns a short sourced brief with options compared and one clear recommendation.

npx workspacetemplates add research-topic --tool claude-code

Writes 1 file to .claude/commands/

.claude/commands/research-topic.md16 lines · 1.3 KBFile
---
description: Researches a technical question and returns a short sourced brief with options compared and one clear recommendation.
argument-hint: "<question, e.g. \"queue library for Node with retries\">"
---

Research this question and give a brief: $ARGUMENTS

1. Restate the question and the constraints you can see in this repository: language, runtime, hosting, existing dependencies, license rules. Ask one clarifying question only if the answer would change the result.
2. Find two to four candidates. Use official documentation, release notes and the project's repository first; check last release date, open issue trends and license. Search the codebase for existing solutions before proposing a new dependency.
3. Compare on what matters here: fit, effort to adopt, operating cost, lock-in, maturity, security record.
4. Prefer facts you can cite. Mark anything uncertain as such. Never invent version numbers or benchmark results.

Format, under 400 words:
**Recommendation** (one sentence), **Options** (table with pros, cons, source link each), **Why this one**, **Risks**, **What would change my mind**, **Sources** (URLs with the date accessed).

Do not install packages or edit files. Offer a small proof of concept as a next step and ask whether to start it.

What it does

Choosing a library or approach from memory is risky, because versions and advice go stale. This command checks the official docs, release notes and your own repository, then compares the realistic options.

Every claim in the brief points to a source, and the final recommendation says what would change the answer.

Example

you › /research-topic background job library for a Python FastAPI service

agent › Recommendation: Arq, because the app already runs Redis and needs only retries and cron. Options: Celery (heavy), RQ (no async), Arq. Would change if jobs need complex workflows. Sources: three official docs links. Build a proof of concept?

Questions

Does it install what it recommends?
No. It only reads and reports, and offers a proof of concept as a separate step.
How does it avoid outdated advice?
It prefers current official docs and release pages, and dates every source it cites.
  • Debug Error

    CommandWorkflow

    Free
  • Estimate Task

    CommandWorkflow

    Free
  • Explain Code

    CommandWorkflow

    Free
  • Plan Feature

    CommandWorkflow

    Free