plugins/pokayokay/skills/deep-research/SKILL.md
Use for multi-day technology evaluations, competitive analysis, architectural exploration, best practices research, or major strategic decisions requiring comprehensive investigation and stakeholder reports. Unlike spike (time-boxed hours), supports extended multi-day investigation.
npx skillsauth add srstomp/pokayokay deep-researchInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Comprehensive investigation that informs major decisions. Produces structured reports for stakeholders.
| | Spike | Deep Research | |-|-------|---------------| | Duration | Hours | Days | | Scope | Single question | Multiple questions | | Output | GO/NO-GO decision | Comprehensive report | | Depth | Proof of concept | Full evaluation |
spike for quick GO/NO-GO decisionsarchitecture-review for structural analysis of what's already built| Reference | Description | |-----------|-------------| | research-types.md | Technology evaluation, competitive analysis, best practices | | source-quality.md | Evaluating source reliability and relevance | | synthesis-patterns.md | Comparison matrices, decision frameworks | | research-report-template.md | Template for comprehensive research reports | | comparison-matrix-template.md | Template for multi-option comparison scoring |
development
Use when starting AI development sessions, resuming interrupted work, managing multi-session projects, or orchestrating work with human checkpoint control (supervised, semi-auto, auto, or unattended modes).
testing
Use when analyzing PRD documents, concept briefs, or feature specs to create implementation plans, breaking work into epics/stories/tasks with dependencies and estimates, or generating PROJECT.md and kanban tracking.
development
Use when starting AI development sessions, resuming interrupted work, managing multi-session projects, or orchestrating work with human checkpoint control (supervised, semi-auto, auto, or unattended modes).
development
Use when designing test architecture, building API test suites, validating API contracts, setting up component or E2E testing, managing test data, debugging flaky tests, reviewing coverage strategy, or organizing test files. Covers test pyramid, mocking (MSW), frontend (React Testing Library, Playwright), and CI integration.