From dead-end-registry
List this repo's recorded dead ends — approaches already tried and abandoned, with reasons and cost
How this skill is triggered — by the user, by Claude, or both
Slash command
/dead-end-registry:dead-endsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
!`node "${CLAUDE_SKILL_DIR}/../../dead-end-registry.js" --render 2>/dev/null || node "${CLAUDE_PLUGIN_ROOT}/dead-end-registry.js" --render`
!node "${CLAUDE_SKILL_DIR}/../../dead-end-registry.js" --render 2>/dev/null || node "${CLAUDE_PLUGIN_ROOT}/dead-end-registry.js" --render
The list above is this repository's recorded dead ends — approaches that were tried
and then reverted or ruled out, newest first, each with the date it was tried, why it
was walked back, and the estimated token cost of the detour. It is produced by the
dead-end-registry hook, which mines your transcripts as you work.
Briefly summarize the 1–3 most relevant entries and, if any bear on what the user is currently doing, gently flag that they have been down this road before. If the list is empty, just say so. Keep it short; do not re-run any commands.
npx claudepluginhub karanb192/claude-code-hooks --plugin dead-end-registryGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.