skills.rest
chenziyang110
chenziyang110COMMUNITY
Explore all skills by this author →
GitHub

sp-research

Routes sp-research invocations to the sp-deep-research feasibility gate workflow.

Updated Jul 6, 2026
Search Tags:#planning#feasibility#spec-kit#deep research#workflow routing#command alias
One-click install
npx skills add https://github.com/chenziyang110/launchdeck --skill sp-research-chenziyang110
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sp-research
Source: https://github.com/chenziyang110/launchdeck/tree/main/.claude/skills/sp-research
Command: npx skills add https://github.com/chenziyang110/launchdeck --skill sp-research-chenziyang110

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Users who invoke sp-research expecting a Spec Kit research command would otherwise create duplicate workflow lanes and artifacts; this Skill redirects them to the canonical sp-deep-research pre-plan feasibility gate without separate state. ## Core Features & Use Cases - Compatibility Alias: Treats sp-research as an alias for sp-deep-research, preserving the user's original arguments and routing immediately. - State Discipline: Ensures any written workflow state uses active_command: sp-deep-research and never persists a separate sp-research artifact set. - Guardrails: Redirects generic web research requests to a passive external research skill instead of writing Spec Kit feature artifacts. - Use Case: A user in a spec-kit project types /sp-research to check feature feasibility; the Skill forwards the request to the deep-research workflow, which produces deep-research.md and updates workflow-state.md under the canonical command name. ## Quick Start Invoke /sp-research with your feasibility question and let it route directly into the sp-deep-research workflow.

Frequently Asked Questions about sp-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a feasibility check before planning a Spec Kit feature?▼

Invoke sp-research or sp-deep-research with your feasibility question. The request routes to the deep-research workflow, which produces deep-research.md and optional research spikes in the feature directory before sp-plan runs.

What is the difference between sp-research and sp-deep-research?▼

sp-research is only a compatibility alias; sp-deep-research is the canonical workflow. All outputs, artifacts, and workflow state belong to sp-deep-research, and no separate sp-research state is persisted.

Does sp-research work outside a spec-kit project?▼

No. It requires a spec-kit project structure with a .specify/ directory, including templates like workflow-blocker-template.md. Without that structure the routing contract cannot be followed.

Can I use sp-research for general web research?▼

No. If the request is generic web research rather than a planning-ready spec feasibility gate, the guardrails route it to a passive external/web research skill instead of writing Spec Kit feature artifacts.

What artifacts does the deep research workflow create?▼

The canonical workflow writes FEATURE_DIR/deep-research.md, optional FEATURE_DIR/research-spikes/ files, and updates workflow-state.md with active_command set to sp-deep-research.

Related Skills

Explore More Software Engineering Skills→
vtexvtex
60

speckit-constitution

Update Spec Kit constitution templates from principle inputs and synchronize dependent files.

Official
Advanced
MINT-IAMINT-IA

gsd-research-phase

Validate a project phase and spawn a subagent to produce RESEARCH.md.

Official
Advanced
bigeasyfreemanbigeasyfreeman
2

learning-capture

Capture verified reusable learnings from ADLC operations after PR closeout.

Community
Advanced
GiantCroissant-LunarGiantCroissant-Lunar

spec-kit-bridge

Coordinate GitHub Spec Kit workflows by mapping spec phases to domain skills.

Official
Advanced