conduct-spike

Solid

Interactively conduct a time-boxed spike — collaboratively reduce uncertainty through discussion mixed with agent-driven research (and small throwaway prototypes where a question is empirical), then record the outcome on the spike's work item. Use when a work item or brief poses open questions that must be resolved before planning or implementation can proceed with confidence.

AI & Automation 30 stars 1 forks Updated today MIT

Install

View on GitHub

Quality Score: 85/100

Stars 20%
50
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Conduct Spike !`${CLAUDE_PLUGIN_ROOT}/bin/accelerator config context --skill conduct-spike --fail-safe` !`${CLAUDE_PLUGIN_ROOT}/bin/accelerator config agents --fail-safe` If no "Agent Names" section appears above, use these defaults: accelerator:web-search-researcher, accelerator:codebase-locator, accelerator:codebase-analyser, accelerator:codebase-pattern-finder, accelerator:documents-locator, accelerator:documents-analyser. **Work items directory**: !`${CLAUDE_PLUGIN_ROOT}/bin/accelerator config path work --fail-safe` You are tasked with conducting a **spike**: a time-boxed, uncertainty-reducing investigation. The spike is mostly conceptual, but a question is often best answered by building a small throwaway prototype or test case. Your job is to take an open, ambiguous brief and **iteratively reduce its uncertainty through collaborative discussion** — backed by agent-driven research and, where needed, small experiments — until the team can proceed with confidence, then record the outcome. This is **not** an interview and **not** a report you generate alone. It is a **collaborative discussion**: you surface evidence, propose interpretations, and the human steers — together you converge on answers. Lean on the research agents to do the legwork so the conversation stays high-level. ## Initial Response When this command is invoked: 1. **If a brief reference was provided**, resolve it in this order: - A **path** (e.g. `meta/work/0003-skill-evaluation-framework-sel...

Details

Author
atomicinnovation
Repository
atomicinnovation/accelerator
Created
5 months ago
Last Updated
today
Language
HTML
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

rig-spike

Run a time-boxed research spike to answer an open technical question or de-risk an approach BEFORE committing to implementation. Produces written findings + a recommendation (and optionally a throwaway prototype), not production code. Use when the team needs to evaluate feasibility, compare options, or reduce uncertainty before a feature is planned. Triggers on: 'spike', 'research spike', 'investigate', 'evaluate feasibility', 'de-risk', 'proof of concept', 'POC', 'compare options', 'can we', 'what would it take'.

3 Updated 3 days ago
agent-rig
AI & Automation Listed

spike

Use when the user wants to feel out an idea before committing to a real build — "spike this out", "try it", "is this even possible?", "compare A vs B". Throwaway experiments that decompose into 2-5 feasibility questions, build minimal observable prototypes, and return VALIDATED / PARTIAL / INVALIDATED verdicts. Disposable by design. Adapted from Hermes Agent / GSD.

0 Updated 2 weeks ago
fabioc-aloha
AI & Automation Featured

develop-spike-summary

Documents the results of a completed technical or design spike, capturing the original question, approach, evidence-backed findings, and a clear proceed-or-not recommendation so the team does not re-litigate the exploration. Use once a time-boxed investigation has concluded. For the architecture decision the spike informs, use develop-adr instead; for research-based exploration, use discover-interview-synthesis.

557 Updated today
product-on-purpose