Manages time-boxed spike issues on GitHub for exploring unscoped work.
npx skills add https://github.com/chris-prener/dev-kit --skill discovery-chris-prener
Please help me install this Agent Skill. Skill: discovery Source: https://github.com/chris-prener/dev-kit/tree/main/dev-kit/skills/discovery Command: npx skills add https://github.com/chris-prener/dev-kit --skill discovery-chris-prener
spike label and a frozen discovery template capturing the question, time-box, and expected artifact. - Findings Tracking: Appends dated findings to the spike issue body as exploration progresses, keeping context durable. - Structured Closure: Closes spikes only with a named artifact (requirements doc, scoped issues, ADR, or not-planned summary), refusing silent closes. - Overrun Audit: Surfaces open spikes whose stated time-box has expired and prompts continue, cut-scope, or close decisions. - Use Case: Your team is asked to integrate an unfamiliar third-party API. Open a 2-day spike, log findings as you probe the API, then close with scoped implementation issues filed via the backlog workflow. ## Quick Start Ask the assistant to open a time-boxed spike to investigate whether we should build the proposed feature, with a requirements doc as the target artifact.High-intent search queries and answers about installing and using this skill.
Open a spike issue with the spike label using a template that records the question, time-box, and target artifact. Append dated findings as you explore, then close with a structured comment naming the artifact produced, such as scoped issues or an ADR.
Use a spike when scope itself is unknown — unfamiliar data sources, competing approaches, or whether to build at all. If scope is already clear, file a regular issue through the backlog workflow instead of opening a spike.
A spike closes with one of four artifacts: a requirements doc, a set of scoped issues, an architecture decision record (ADR), or a documented not-planned decision summary. Spikes never produce production code.
The close operation refuses to proceed without a named artifact selection. However, closing the issue directly with raw gh commands or the GitHub UI bypasses this check, since there is no periodic auditor enforcing closure discipline.
The audit operation queries open spike-labeled issues, parses the Time-box and Opened fields from the body, and compares expiry against current UTC time. Overrun spikes are flagged with a recommendation to continue, cut scope, or close.
kiurakkuRuns time-boxed spikes and throwaway prototypes to answer technical feasibility questions.
stark-ai-deInterview users to capture requirements and draft Codex-executable implementation specs.
poindexter12Apply a standardized label taxonomy and triage workflow to GitHub issues.
sarkarshivaditya-labPlans massive multi-epic work requests through research spikes, decision logs, and milestone structures.