dev-research
/dev-research
Write dated research notes with a source beside every fact, for market, competitors or technical options. Use for "research the market", "compare these options", "who else does this", or when dev reaches the research step.
- Author
- HarunRRayhan ↗
- Repository
- RayStack ↗
- Licence
- MIT
- Last repository change
- 06.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 06.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Write dated research notes with a source beside every fact, for market, competitors or technical options. Use for "research the market", "compare these options", "who else does this", or when dev reaches the research step.
Triggers from the description
Original author description
Write dated research notes with a source beside every fact, for market, competitors or technical options. Use for "research the market", "compare these options", "who else does this", or when dev reaches the research step.
How it works
- 1. Check the tool first
- 2. Scope the question
- 3. Gather and record
- 4. Write the note
- 5. Finish
SKILL.md preview
--- name: dev-research description: Write dated research notes with a source beside every fact, for market, competitors or technical options. Use for "research the market", "compare these options", "who else does this", or when dev reaches the research step. --- # Dev research This skill turns a question into a note in `docs/research/`. Formats, IDs and question rules are in `../dev/references/dev-contract.md`. ## 1. Check the tool first You need a web search or page-fetch tool from the host. If there is none, say so in one line and stop. Do not write notes from memory: a note with no sources is worse than none. Offer to resume when the user can pass in pages, files or links to read. ## 2. Scope the question Read `DECISIONS.md` and the existing `docs/research/` first. Do not redo a settled question. If the topic is unclear, ask through the question tool, one question per call, recommended option first. Typical scopes: - **Market**: who buys, what they pay, what they use now. - **Competitors**: what each does, what it costs, what it explicitly does not do. - **Technical options**: the real choices, their limits, how mature each one is. One note per topic. Split a broad ask into several notes. ## 3. Gather and record - Prefer primary pages: vendor docs, pricing pages, changelogs, filings, repos. - Put a source beside every fact: a URL in the same table row or bullet. A fact with no link does not go in. - Mark a claim `unverified` when it comes from one third-party page, a forum post or a press summary, or when you could not open the page. Keep it, label it, and link it. - Give dates for anything that changes: prices, versions, funding, launch dates. - Where sources disagree, show both and say which you trust and why. - Copy no long passages. Paraphrase and link. ## 4. Write the note Save `docs/research/YYYY-MM-DD-<topic>.md` with today's date: ``` # <Topic>, <Month YYYY> ## Question One or two lines: what this note answers and why. ## Findings Tables or bullets. A source beside every fact. `unverified` where it applies. ## Gaps What you could not find or confirm. ## What this means for the product 3 to 6 bullets: what to build, avoid or test, tied to the findings. No new facts here. ``` Never edit an old note. If a fact changed, write a new dated note and link the old one. ## 5. Finish Tell the user the file path, the three strongest findings and the biggest gap. If a finding settles a choice, propose a `D-` row for `DECISIONS.md` and ask before adding it. Then hand back to `dev`, which goes straight on to the next step, usually `dev-prd`.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · HarunRRayhan/RayStack | 100 | MIT |
| nchandar/dev-kit | 90 | MIT |
Database snapshot: 13.11.2026 · package version 5c2178de6cde (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100research
Research assistant — gathers information, performs competitive analysis, and generates structured research reports. Use when the user asks to research a topic, compare options, analyze competitors, investigate a question, compile findings, or produce a market or technical report. - 100market-research
Deep web research skill using Firecrawl MCP. Use when estimating market size (TAM/SAM/SOM), analyzing trends, or scraping competitors. For competitor teardowns, see competitor-analysis. - 87market-research
Produces sized, sourced, decision-ready market and competitive analysis rather than a collection of facts. Builds every market size twice, top-down and bottom-up, reconciles the two, separates the total market from the serviceable slice from what could realistically be won, maps… - 100market-research-skill
Runs structured supplier and market research, capability comparison, pricing observations, and risk checks. Use for market scans, longlists, and sourcing research. - 100market-research
Competitive analysis and market research with source attribution. Parallel fan-out across web, review sites, and news. Triggers on: "market research", "competitive analysis", "competitor comparison". - 100research
Engineering OS research playbook — rigorous, source-backed research on technologies, libraries, vendors, markets, competitors, papers, and \"what's the best way to X\" questions, producing a decision-ready brief with citations. Use whenever the user asks to research, compare,…