From maestro
Use when closing an issue without implementing it — wont-fix, deferred, or duplicate. Issues only; for archiving tracks use manage.
How this skill is triggered — by the user, by Claude, or both
Slash command
/maestro:issue-close <issue-file-path> [--reason wont-fix|deferred|duplicate]<issue-file-path> [--reason wont-fix|deferred|duplicate]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Archive an issue without creating a track.
Archive an issue without creating a track.
Argument: <file-path> [--reason wont-fix|deferred|duplicate]
Read the issue file
status is already implemented, wont-fix, deferred, or duplicate, the issue is already closed — inform the user and stop.status field, inform the user and stop.Get reason if not provided as argument — ask:
Why are you closing this issue?
1. wont-fix — not worth doing
2. deferred — valid but not now
3. duplicate — already covered elsewhere
If duplicate — ask which issue file or conductor track it duplicates
Update issue file frontmatter:
status to the reason (wont-fix | deferred | duplicate)date +%Y-%m-%d — do not assume you know it. Add closed: YYYY-MM-DDduplicate-of: <issue-filename-or-track-id>## Notes if user provides oneMove to issues/archived/<reason>/
Confirm closure with file location
npx claudepluginhub owebboy/maestro --plugin maestroGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.