write-spike

Use when starting a new initiative spike, investigating technical feasibility, assessing impact across services, or writing an engineering discovery document — produces a structured spike doc with diagrams and a private notes file.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable multi-phase workflow with strong validation checkpoints. Its main weakness is progressive disclosure: it leans on referenced bundle files (spike-template.md, requirements.json, company-config.example.yaml) that are not present in the skill bundle.

Suggestions

Add the referenced bundle files (spike-template.md, requirements.json, company-config.example.yaml) under references/ so the navigation targets actually exist, or inline the essential template structure directly in SKILL.md.

Trim the motivational persona opening ('You are a senior staff engineer... You've seen spikes that changed architectural direction...') to a one-line role framing to recover token budget.

Provide a minimal inline skeleton of the spike template sections so the skill remains actionable even when spike-template.md is absent.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete configs, a Mermaid flow, and tables, but the opening persona paragraph ('You are a senior staff engineer... You've seen spikes that changed architectural direction...') is motivational padding Claude does not need.	4 / 5
Actionability	Provides executable invocation examples, a config YAML schema, named subagent tasks, and a quality-gates table; minor gaps where referenced artifacts (spike-template.md) are described but their structure is not inlined as a fallback.	4 / 5
Workflow Clarity	Four mandatory phases are explicitly sequenced with a Mermaid diagram, and validation is built in (preflight dep check, Phase 4 self-review, grill-me pass, quality gates table, 'fix inline' feedback loop).	5 / 5
Progressive Disclosure	References several sibling files (requirements.json, spike-template.md, company-config.example.yaml), but none of those bundle files actually exist in references/scripts/assets, so the navigation points to missing material and the core template is not inlined.	3 / 5
	Total	16 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly defines both trigger conditions and concrete outputs in the third person. Trigger term coverage is good though slightly short of full synonym/file-extension completeness.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions ('investigating technical feasibility', 'assessing impact across services', 'writing an engineering discovery document') and specific outputs ('structured spike doc with diagrams and a private notes file').	5 / 5
Completeness	Explicitly answers both 'when' ('Use when starting a new initiative spike, investigating...') and 'what' ('produces a structured spike doc with diagrams and a private notes file') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural keywords ('initiative spike', 'technical feasibility', 'engineering discovery document') users would actually say, but lacks synonyms/variations beyond the listed trigger phrases.	4 / 5
Distinctiveness Conflict Risk	Clear niche ('initiative spike', 'engineering discovery document') with distinct outputs that are unlikely to overlap with other skills' triggers.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: AndreJorgeLopes/devflow
Path: devflow-plugin/flows/review/skills/write-spike/SKILL.md
Commit: bd4b70c

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.