construct-spike-run

Runs external graph-analysis tools against isolated workspace copies and captures structured results.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/mabstruct/construct --skill construct-spike-run-mabstruct
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: construct-spike-run
Source: https://github.com/mabstruct/construct/tree/main/CONSTRUCT-CLAUDE-impl/claude/skills/construct-spike-run
Command: npx skills add https://github.com/mabstruct/construct --skill construct-spike-run-mabstruct

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Evaluating external graph-analysis tools like Graphify or InfraNodus normally risks corrupting canonical workspace data. This Skill runs those tools against temporary isolated copies of the workspace, capturing outputs safely so you can assess tag extraction and graph exploration quality without touching real knowledge data. ## Core Features & Use Cases - Isolated spike execution: Copies only canonical files (cards/, refs/, connections.json, domains.yaml) to a temp directory before running the external tool, then cleans up automatically. - Structured result capture: Writes stdout, stderr, output files, duration, and success status to log/spike-results/{tool}-{timestamp}.json for later review. - Evaluation frameworks: Provides per-spike criteria for Graphify-style tag extraction (precision, recall, novelty) and InfraNodus-style graph exploration (structural insight, UI applicability). - Use Case: Run construct spike run graphify --workspace test-ws/my-construct to see whether extracted candidate tags are novel compared to existing search-seeds, then document findings as design input. ## Quick Start Ask the agent to run a graphify spike against your test workspace and review the captured results file in log/spike-results.

Frequently Asked Questions about construct-spike-run

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

FAQPage Schema
How do I run a Graphify or InfraNodus spike on my workspace?▼

Use the construct CLI: run `construct spike list` to see available spike types, then `construct spike run <tool-name> --workspace <path>`. Results are written to log/spike-results/{tool}-{timestamp}.json with captured outputs and logs.

Does running a spike modify my canonical workspace data?▼

No. The spike runner copies only canonical files (cards/, refs/, connections.json, domains.yaml) to a system temp directory and runs the external tool there. The temp copy is cleaned up afterward, even on failure, so canonical data is never at risk.

What happens if the external tool is not installed or times out?▼

If the tool is missing from PATH you get an error suggesting installation or passing --tool-path. If execution exceeds the timeout (default 300 seconds, configurable via --timeout), the spike reports a timeout and still cleans up the temp workspace.

How do I evaluate whether spike results are useful?▼

Each spike type has defined criteria. For Graphify, assess precision, recall, novelty, and signal-to-noise of extracted tags against existing search-seeds. For InfraNodus, evaluate structural insight, UI applicability, and overlap with the existing bridge detection pipeline.

When should I use the InfraNodus spike versus the built-in bridge pipeline?▼

The InfraNodus spike is evaluation-only per decision D-09 and is not a permanent feature. Use it to explore graph metrics and UI patterns as design input for v0.5; the existing L1/L2/L3 bridge pipeline remains the production path for connection detection.