Menu
Determines where to place files based on their purpose. Auto-consulted when Claude needs to create a new file and is deciding between .claude-work/ subdirectories or docs/.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Add a dependency relationship between GitHub issues using the native addBlockedBy mutation
Reusable file sequence numbering with prefix (NNNN-name) and suffix (name-NNNN) modes. Returns the next available zero-padded sequence number for a given directory.
Drop a timestamped note for the current issue - collected by /finish-issue for PR descriptions
Create or update CHANGELOG entries with tone guardrails, thematic grouping, and implementation-detail leak detection.
Delete an issue's working directory (.claude-work/issues/<ID>/) after confirming with the user via interactive prompt
Create a commit message file in .claude-work/commit-msgs/ with auto-numbered filenames. Focuses on WHY not WHAT. The diff already shows what changed. User reviews and commits manually.
| name | file-placement |
| version | 2026.07.27@6dc7d1d |
| user-invocable | false |
| description | Determines where to place files based on their purpose. Auto-consulted when Claude needs to create a new file and is deciding between .claude-work/ subdirectories or docs/. |
When creating a new file, use this decision tree to determine the correct location.
| Question | Destination | Skill |
|---|---|---|
| Is it a question needing user input? | .claude-work/questions/ | /question |
| Is it a commit message draft? | .claude-work/commit-msgs/ | /commit-msg |
| Is it a quick note, finding, or result? | .claude-work/notes/ | /note |
| Is it a temporary working document with formal step tracking? | .claude-work/scratchpads/ | /scratchpad |
| Is it a note during issue work? | .claude-work/issues/<ID>/breadcrumb.md | /breadcrumb |
| Is it permanent documentation? | docs/ or package README | N/A |
Composite skills default to /note. /start-issue, /start-side-quest, and /tackle-pr-comment all create a /note by default and only fall back to /scratchpad when the user explicitly opts in (--scratchpad flag or equivalent natural-language trigger). The opt-in path is reserved for workflows that want /tackle-scratchpad-block to drive execution against a JSON step block; otherwise, the LLM self-organizes in-session.
Evaluate from top to bottom. The first matching row determines the destination.
Each skill owns its own file format, naming conventions, and auto-numbering. Consult the referenced skill for specifics. For the numbered working-file skills: /scratchpad, /question, and /commit-msg. Directory organization (flat vs issue-scoped subdirectories) is handled by ~/.claude/skills/issue-context/target-path.sh, which those skills call internally. /note uses timestamp-based filenames and detects branch context on its own; /breadcrumb writes a single file per issue directly. All ephemeral working files live under .claude-work/.
.claude-work/ paths must never appear in commits, PRs, GitHub issues, or any output visible on GitHub. These files are local-only working documents that don't exist in the repository. Referencing them creates broken, meaningless links.
src/ directory__tests__/ directory