speckit.assess.research
Gathers evidence on users, market, prior art and data to support or challenge an idea, and records it.
- Kind
- Prompt
- Works with
- Claude Code, Codex, GitHub Copilot, Cursor, Windsurf / Devin, Cline
- Source
- github/spec-kit @ c00dc0551583
- Path
- extensions/assess/commands/speckit.assess.research.md
- License
- MIT
- Jobs
- Planning
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
# Research an Idea Gather the **evidence** needed to judge an idea honestly, and record it at `.specify/assessments/<slug>/research.md`. This stage exists to *challenge* the idea as much as support it — surfacing prior art, real user signal, market context, and data so the later `__SPECKIT_COMMAND_ASSESS_DEFINE__` and `__SPECKIT_COMMAND_ASSESS_DECIDE__` stages rest on facts, not enthusiasm. Research **collects and cites evidence; it does not decide.** No verdict, no solution design. ## User Input ```text $ARGUMENTS ``` The input carries the slug and (optionally) research direction or links. **Ancestor path safety (before any filesystem lookup here)**: where `.specify` or `.specify/assessments` already exist, verify each is a real directory (not a symlink) resolving inside the project root, and refuse and report if either exists as a symlink or escapes the root — a not-yet-created directory is allowed and will be created safely later. Only then resolve the slug: 1. **Explicit slug** (`slug=…`, `--slug …`, or an obvious token) — normalize it (see **Slug safety** below). …