create-spike

Investigate vague problems and generate structured GitHub issues for build-from-issue workflows.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/x402agent/openclawd-stack --skill create-spike
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-spike
Source: https://github.com/x402agent/openclawd-stack/tree/main/openclawd-stack/OpenShell-main/.agents/skills/create-spike
Command: npx skills add https://github.com/x402agent/openclawd-stack --skill create-spike

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps turn vague feature ideas or problems into concrete, actionable GitHub issues by performing a deep codebase investigation and producing a structured spike document for the build-from-issue workflow.

Core Features & Use Cases

  • Deep codebase investigation using a reviewer agent to map problems to code paths and identify involved components.
  • Generate a structured GitHub issue containing both a stakeholder-friendly summary and a full technical investigation suitable for build-from-issue.
  • Aligns with the build-from-issue workflow to plan implementations and accelerate handoffs between discovery and execution.

Quick Start

Describe a vague problem and trigger keywords, then run the spike workflow to generate a structured GitHub issue ready for review.

Frequently Asked Questions about create-spike

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

FAQPage Schema
How do I turn a vague software idea into an actionable GitHub issue?

Yes, you can generate a structured GitHub issue from a rough problem description by running a deep codebase investigation that produces both a stakeholder-friendly summary and a full technical spike document for implementation.

What is a spike investigation in software development?

A spike investigation maps vague problem descriptions to concrete, buildable GitHub issues by exploring the codebase, identifying involved components, and generating a structured issue with technical findings and architecture context.

How do I scope a vague feature request for developers?

Scoping a vague feature request involves investigating the codebase to identify involved components and generating a structured GitHub issue containing both a stakeholder-friendly summary and detailed technical findings for developers.

Does the build-from-issue workflow require a structured technical investigation?

The build-from-issue workflow requires a structured GitHub issue that includes a full technical investigation with architecture context and code path mappings to properly plan implementations and accelerate handoffs.

Can I use a reviewer agent to investigate a codebase before creating an issue?

Using a reviewer agent to investigate a codebase maps problems to specific code paths and identifies involved components, generating a structured spike document that feeds the build-from-issue workflow.