Close spike tickets by applying PROMOTE or DISCARD disposition gates.
npx skills add https://github.com/AAbdulghany/fms --skill spike-close-aabdulghany
Please help me install this Agent Skill. Skill: spike-close Source: https://github.com/AAbdulghany/fms/tree/main/.claude/skills/spike-close Command: npx skills add https://github.com/AAbdulghany/fms --skill spike-close-aabdulghany
Close spikes by applying the disposition gate to ensure a determined path: either promote to a production-feature or discard with a memo.
Close an active spike by running /spike-close with --promote or --discard and follow the prompts.
High-intent search queries and answers about installing and using this skill.
To close a spike, apply the disposition gate by running the command with --promote to file a Feature ticket or --discard to generate a spike memo. The skill validates the ticket and cross-references all generated artefacts back to the original spike.
Promoting a spike creates a new Feature ticket for implementation, while discarding a spike generates a memo under docs/spike-memos to document findings. Both actions close the original ticket and cross-reference the generated artefacts.
Yes, GitHub CLI (gh) is required for ticket visibility to view and close issues. The skill uses gh to validate active spike tickets, manage resolution, and close the corresponding branch accordingly.
The skill validates that the active ticket is a spike before proceeding with resolution. It checks the ticket type via gh to ensure the correct disposition gate is applied for promotion or discarding.
Discarded spike learnings are documented in a memo generated under the docs/spike-memos directory. The created memo includes cross-references back to the original spike ticket for full traceability.
Yes, when promoting a spike to a Feature ticket, the skill automatically generates and links the new artefact with cross-references back to the original spike. This maintains full traceability between the investigation and the implementation task.
drvossResolve GitHub issues end-to-end from ticket to pull request.
yves-sSummarize spike results and create follow-up tickets from implementation steps.
SteveGJonesValidate requirements, design, test, and code artefacts for phase-gate progression.
CommonCapitalAutomate project folder creation with Markdown documentation and standardized layouts.
