Write Bash commands that don't trigger unnecessary permission prompts. Use Read/Edit/Grep instead of head/tail/sed/awk/cat/echo; split chained commands (&&, ;, ||) into separate Bash calls; drop diagnostic suffixes like `; echo "EXIT=$?"`. The allowlist matches whole command strings — every mismatch costs the user attention.

2026-05-142

commit

tgd1975/AwesomeStudioPedal

Commit user-named files atomically via scripts/commit-pathspec.sh (which wraps `git commit -m "..." -- <files>` and writes the provenance token the pre-commit hook validates). Applies the CLAUDE.md "Pre-commit hook failures on unrelated changes" protocol when the hook fails. Never adds --no-verify silently — explicit user approval is required.

2026-05-142

ts-epic-new

tgd1975/AwesomeStudioPedal

Scaffold a new epic file in docs/developers/tasks/open/ and run housekeep

2026-05-102

ts-task-active

tgd1975/AwesomeStudioPedal

Set a task to active — updates status, moves to active/, runs housekeep. Also resumes paused tasks (paused/ → active/ or active/ with closed prerequisites).

2026-05-102

ts-task-done

tgd1975/AwesomeStudioPedal

Mark a task as closed — writes effort_actual, moves the file to closed/, runs housekeep, and commits

2026-05-102

ts-task-new

tgd1975/AwesomeStudioPedal

Scaffold a new task file in docs/developers/tasks/open/ and update OVERVIEW.md

2026-05-102

name	ts-idea-new
description	Scaffold a new idea file in docs/developers/ideas/open/ and regenerate the ideas OVERVIEW.md

ts-idea-new

The user invokes this as /ts-idea-new "Short idea title".

If no title is provided, ask the user for one before proceeding.

Steps:

Determine the next IDEA-NNN by reading docs/developers/ideas/OVERVIEW.md and scanning the idea tables for the highest existing IDEA-NNN. Add 1. If OVERVIEW.md does not yet exist, fall back to scanning filenames in docs/developers/ideas/open/ and archived/ for idea-NNN-*.md.
Build the filename slug from the title: lowercase, spaces and special characters → hyphens, max 50 chars, prefixed with the new ID (e.g. idea-042-my-new-idea.md).
Ask the user for a one-line description: (shown in the OVERVIEW table). Keep it to ~120 chars. If the user declines, omit the field. 3a. Ask the user for a category:. Pick one of the project's existing categories — read the current set from docs/developers/ideas/OVERVIEW.md (the Category column in the Open and Archived tables). Don't invent a new category without discussing it with the user — the value is rendered in the index and ad-hoc additions break the grouping. If the user genuinely can't place the idea, omit the field; the OVERVIEW renders missing categories as an em dash.
Write the file to docs/developers/ideas/open/ with this template:

---
id: IDEA-NNN
title: <title>
description: <one-line description — optional>
category: <one of the existing categories — optional>
---

# <title>

<body — free-form markdown. Describe the idea, motivation, rough
approach, open questions. No prescribed structure.>

Run python scripts/update_idea_overview.py to regenerate docs/developers/ideas/OVERVIEW.md.
Report the new idea ID and file path.

Do not commit — ideas are usually created as part of a larger brainstorming session, and the user will commit the batch together.

Sub-notes (do not scaffold here)

If the user asks for a sub-note attached to an existing IDEA — a companion design doc, discarded alternative, deep dive on one sub-system — that is not a new IDEA-NNN. Per the convention in docs/developers/ideas/README.md, sub-notes are filenames of the form idea-NNN.<sub-slug>.md (dot between the number and the slug, no frontmatter, never in OVERVIEW). Create them by hand — this skill deliberately does not scaffold them.