craft-analyze
CommandPost-cycle analysis — QA, UX, Creative, and Style audits using MCP browser tools.
Permanently delete a story.
> /plugin marketplace add drobins25/craft> /plugin install craft@craft
name: story-delete description: "Permanently delete a story." argument-hint: "[story-name]"
Permanently remove a story. This is destructive — use archive if you might want it later.
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)"
> "⚠️ **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.
${CLAUDE_PLUGIN_ROOT}/hooks/scripts/delete-story.sh "[story-file-path]"> "**[Story Name]** deleted."
/craft:story-delete [story-name]
Still requires confirmation — no silent deletes.
Post-cycle analysis — QA, UX, Creative, and Style audits using MCP browser tools.
Point at anything in a live browser tab - every pin gets a live attempt on the page the moment you SEND it, and the session keeps…
Consult a craft agent. Routes your question to the best mind in the workshop - not a menu, a recommendation.
Agent crystallization command. Studies a tool, role, or person and produces a portable 9-section agent that inhabits the domain -…
File a bug without fixing it, from a person mid-conversation or an agent mid-run. One door, a complete record on disk, nobody…
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.