Package spike findings into a project-local skill and summary.
npx skills add https://github.com/hadpadrahul/school-erp --skill gsd-spike-wrap-up
Please help me install this Agent Skill. Skill: gsd-spike-wrap-up Source: https://github.com/hadpadrahul/school-erp/tree/main/.codex/skills/gsd-spike-wrap-up Command: npx skills add https://github.com/hadpadrahul/school-erp --skill gsd-spike-wrap-up
Spike research and exploratory findings often live in ephemeral notes. This Skill packages those findings into a persistent project skill that can be loaded by future build conversations, ensuring learnings are not lost and can guide decisions.
Summarize the latest spike and save it as a project-local skill for future builds.
High-intent search queries and answers about installing and using this skill.
To save spike findings for future build sessions, this Skill packages your research into a persistent project skill stored under .codex/skills/spike-findings-[project]/, ensuring learnings are loaded automatically later.
Documenting spike investigations is best handled by packaging findings into a reusable skill and writing a concise summary to .planning/spikes/, keeping your project history and learnings accessible.
Yes, you can persist spike research notes by wrapping them into a project-local skill, which outputs the packaged findings to a local directory for quick loading in future conversations.
You need to wrap up a spike investigation when you have exploratory findings or research that should guide future decisions, preventing ephemeral notes from being lost across sessions.
Yes, this spike wrap-up approach works without external dependencies, relying solely on local project directories like .codex/skills/ and .planning/spikes/ to store and manage your findings.
jedmamostoValidate product or engineering ideas through structured spike experiments.
Poom5741Package spike findings into a reusable skill with .qwen/skills output and YAML frontmatter naming.
aslaiiComplete the following steps: 1. **Replace the stub with your actual content.** 2. **Profit!** (Optional: delete this step if unnecessary. 😉)
qdzshConvert spike artifacts into a project-local SKILL.md with a spike reference.
