doc-spike

Generate structured spike reports from predefined templates with evidence-based findings.

7|3|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/eriklieben/agentic-dev-workflow --skill doc-spike
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-spike
Source: https://github.com/eriklieben/agentic-dev-workflow/tree/main/.claude/skills/doc-spike
Command: npx skills add https://github.com/eriklieben/agentic-dev-workflow --skill doc-spike

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of inconsistent, poorly documented research and technical investigations by providing a standardized template for capturing findings, comparisons, and recommendations.

Core Features & Use Cases

  • Standardized Templates: Ensures all research reports follow a consistent structure including findings, evidence, and actionable recommendations.
  • Path Resolution: Automatically detects whether to save reports locally or within a centralized documentation repository.
  • Use Case: When investigating a new library or architectural pattern, use this skill to generate a formal spike report that documents your research question, evidence-based findings, and a clear recommendation for the team.

Quick Start

Use the doc-spike skill to generate a research report for the question of whether we should migrate our state management to Redux.

Frequently Asked Questions about doc-spike

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

FAQPage Schema
How do I generate a structured technical spike report for a software engineering investigation?▼

To generate a structured spike report, this Skill applies predefined templates to capture research questions, evidence-based findings, and actionable recommendations. It formats your technical investigations into a consistent structure for team review.

What is the best way to document research findings and architectural comparisons?▼

Documenting research findings is best handled by using standardized templates that enforce evidence-based comparisons and actionable recommendations. This ensures your technical writing captures all necessary details for project repositories.

How does path resolution work when saving research reports to a centralized documentation repository?▼

Path resolution for research reports works by integrating with your workflow configuration to automatically detect whether to save documentation locally or within a centralized repository. This maintains project-specific knowledge bases without manual path routing.

Can I use this to document a state management migration spike for my team?▼

Yes, you can document a state management migration spike by feeding the research question to the Skill. It generates a formal report outlining your evidence-based findings and a clear recommendation for the team.

Do I need any dependencies to generate standardized technical documentation?▼

No dependencies are required to generate standardized technical documentation. The Skill operates independently to provide predefined templates and path resolution for capturing your research findings and recommendations.