/craft-story-delete
Permanently delete a story.
$ npx -y skills add drobins25/craft --agent claude-codeShips with craft. Installing the plugin gets this command.
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/craft-story-delete
Context preview
What this command does when you run it.
Permanently delete a story.
Command definition
craft-story-delete.mdname: story-delete
description: "Permanently delete a story."
argument-hint: "[story-name]"
Story Delete
Permanently remove a story. This is destructive — use archive if you might want it later.
Flow
Step 1: Select Story
If no story specified, show all stories:
> "Which story do you want to delete?" > > **In Cycle [X]:** > - [Story 1] — ready > - [Story 2] — active > > **In Backlog:** > - [Story 3] > - [Story 4]
Use **AskUserQuestion**:
question: "Which story to delete?"
header: "Delete"
options:
- label: "[Story 1] (cycle)"
- label: "[Story 2] (cycle)"
- label: "[Story 3] (backlog)"
Step 2: Confirm (Required)
> "⚠️ **Permanently delete [Story Name]?** > > This will: > - Remove the story file entirely > - Delete all chunks and decisions > - Update cycle counts (if in cycle) > > **This cannot be undone.** Use `/craft:story-archive` to keep it in backlog instead."
Use **AskUserQuestion**:
question: "Confirm permanent deletion?"
options:
- label: "Yes, delete permanently"
description: "Cannot be undone"
- label: "Archive instead"
description: "Move to backlog, keep for later"
- label: "Cancel"
description: "Keep the story"**If "Archive instead":** Run `/craft:story-archive` flow instead.
Step 3: Execute
${CLAUDE_PLUGIN_ROOT}/hooks/scripts/delete-story.sh "[story-file-path]"Step 4: Confirm
> "**[Story Name]** deleted."
Quick Usage
/craft:story-delete [story-name]
Still requires confirmation — no silent deletes.
Safety
- Always requires explicit confirmation
- Offers archive as alternative
- Updates cycle state automatically
- Git history preserves deleted files (if committed)
Read more
name: story-delete description: "Permanently delete a story." argument-hint: "[story-name]"
Story Delete
Permanently remove a story. This is destructive — use archive if you might want it later.
Flow
Step 1: Select Story
If no story specified, show all stories:
> "Which story do you want to delete?" > > **In Cycle [X]:** > - [Story 1] — ready > - [Story 2] — active > > **In Backlog:** > - [Story 3] > - [Story 4]
Use **AskUserQuestion**:
question: "Which story to delete?" header: "Delete" options: - label: "[Story 1] (cycle)" - label: "[Story 2] (cycle)" - label: "[Story 3] (backlog)"
Step 2: Confirm (Required)
> "⚠️ **Permanently delete [Story Name]?** > > This will: > - Remove the story file entirely > - Delete all chunks and decisions > - Update cycle counts (if in cycle) > > **This cannot be undone.** Use `/craft:story-archive` to keep it in backlog instead."
Use **AskUserQuestion**:
question: "Confirm permanent deletion?"
options:
- label: "Yes, delete permanently"
description: "Cannot be undone"
- label: "Archive instead"
description: "Move to backlog, keep for later"
- label: "Cancel"
description: "Keep the story"**If "Archive instead":** Run `/craft:story-archive` flow instead.
Step 3: Execute
${CLAUDE_PLUGIN_ROOT}/hooks/scripts/delete-story.sh "[story-file-path]"Step 4: Confirm
> "**[Story Name]** deleted."
Quick Usage
/craft:story-delete [story-name]
Still requires confirmation — no silent deletes.
Safety
- Always requires explicit confirmation
- Offers archive as alternative
- Updates cycle state automatically
- Git history preserves deleted files (if committed)
Stop Vibing. Start Crafting. Claude Code plugin: guided + controlled development orchestration harness with built-in workflow + state management, for designing + building durable, production-ready software through the entire product lifecycle - new projects
Repo: drobins25/craft
Other commands on craft.
- /craft-analyze
Post-cycle analysis — QA, UX, Creative, and Style audits using MCP browser tools.
Open command - /craft-ask
Consult a craft agent. Routes your question to the best mind in the workshop - not a menu, a recommendation.
Open command - /craft-become
Agent crystallization command. Studies a tool, role, or person and produces a portable 9-section agent that inhabits the domain - with beliefs, scar tissue, and instincts.
Open command - /craft-cycle-assign
Move a story from backlog to a cycle.
Open command - /craft-cycle-complete
Complete a cycle. Triggers reflection if pending learnings, then archives.
Open command - /craft-cycle-design
Design a cycle — create new cycles with planned stories, detail existing planning cycles, or quick-sketch a roadmap. Detects planning docs in .craft/planning/ and sources the cycle from them when relevant.
Open command

