
orchestration
Core orchestration guidelines for conversation style, code style, testing, tool conventions, and workflow automation
- version
- 1.42.0
- GitHub stars
- 20
Install
/plugin install orchestration@motlin-claude-code-pluginsRun it inside Claude Code after adding the marketplace with /plugin marketplace add motlin/claude-code-plugins.
Contents
Discovered from sourceSkills 5
Conversation Style
- If the user asks a question, only answer it; don't edit code.
- If the user says to read something, read it and report what it says; don't act on it.
- If the user asks what a document says, show the relevant section instead of paraphrasing.
- Judge ideas on their merits and say plainly where they are wrong.
- Open with the answer, with no praise, apology or preamble.
- Cut empty intensifiers, words that add emphasis without changing meaning:
- "any" is often unnecessary ("any changes" → "changes")
- "actually", "really", "genuinely", "truly"
- "completely", "totally", "fully"
- "definitely", "certainly", "absolutely" (false confidence)
- "just", "simply", "merely"
- Test: remove the word. If the sentence means the same thing, delete it.
- In AskUserQuestion options, name the actor instead of a bare "I" or "you" ("Claude will tag it" / " will tag it"), so it is clear who does what.
Finish Workflow
If the working tree is clean and there is nothing to verify, report that there is nothing to finish.
Use the caller's prompt as the commit intent. Run every applicable step, in order:
- Commit with the
git:commitskill, distilling the caller's prompt into a single-line message. Commit before precommit becausegit test run HEADrefuses a dirty tree and tests the committedHEAD. - Run the
build:precommitskill. Cached successes pass quickly. - Rebase with the
git:git-rebaseskill. - Review the committed diff for reuse, quality, and efficiency, and make cleanup changes when warranted.
- If cleanup changed anything, create a fixup commit for
HEAD. - Run the
build:precommitskill again.
If the work added many tests or the suite got slower, a code:test-speed pass is an option. Judge whether it is warranted and mention it to the user when it is.
LLM Context Guidelines
The .llm/ directory at the root of a git repository holds extra context for LLMs.
.llm/is not tracked. If it has untracked content, make sure it is listed in.git/info/exclude..llm/todo.md, when present, is the current task list. Use themarkdown-tasks:tasksskill for it, and edit it as plans change to keep it in sync..llm/scratch/is writable scratch space for temporary files and output, used when the harness provides no session scratchpad directory.- Everything else in
.llm/is read-only reference, such as git clones of tools and saved documentation, unless a skill names its own working directory there.
Memory
Skills, commands, agents, and CLAUDE.md files are markdown too. When a lesson is about how one of them behaves, edit that file. Don't write a memory for it.
Find the owner
Before writing a memory, ask which instructions governed the behavior that went wrong:
- A skill, command, or agent from a plugin: edit its source in the plugin's git repository.
- A project's
CLAUDE.mdorAGENTS.md: edit that file. - The user's global
~/.claude/CLAUDE.md: edit it, or propose the edit when it is outside the current task.
Keep the fix lean
Add only the rule the correction showed. Leave out lists of examples, destinations, or past decisions that a later session can infer from the files on disk.
- Skip decisions that happened once, and decisions the session got right on its first guess. A later session will guess right too.
- Record a convention only when it breaks the obvious default, such as a naming scheme that differs from the rest of the folder.
- Don't add rationale or "how to apply" sections, and don't expand existing ones to cover new rules.
What still belongs in memory
Write a memory only for a fact that no instruction file owns.
A memory that patches a gap in a skill should be deleted once the skill is fixed.
Skill Guidelines
Most tasks use several of these skills:
| Skill | When to use |
|---|---|
code:code-quality | Before editing code |
code:cli | When running shell commands |
build:precommit | After code changes |
git:git-workflow | For all git operations |
orchestration:conversation-style | For response guidelines |
orchestration:llm-context | When working with .llm/ directories |
orchestration:memory | Before saving a memory |
recap:recap | Before ending a turn |
Git
Use the git:commit skill to commit, git:conflicts to resolve merge or rebase conflicts, and git:git-rebase to rebase the current branch on upstream.
Temporary files
Write scratch files and temporary output to the session scratchpad directory when the harness provides one, and otherwise to .llm/scratch/. Avoid /tmp and other system temp directories; reading from them triggers permission prompts.
Finishing
Before returning control after a task that changed files or git state, use the orchestration:finish skill.
Sponsors
Details
- Marketplace
- motlin/claude-code-plugins
- Source
- plugins/orchestration
- Author
- Craig Motlin
- Category
- Productivity
More from motlin/claude-code-plugins
All 30- plans-dashboardv1.42.0
- plugin-and-skill-devv1.42.0
- pushoverv1.14.0
- recapv1.42.0
- stop-phrase-guardv1.42.0
- temporal-datav1.42.0
- tmux-titlesv1.42.0
- upstream-syncv1.42.0
- worktree-setupv1.42.0
- bash-guardsv1.42.0
- buildv1.42.0
- builtin-tasksv1.14.0
- burnv1.42.0
- codev1.42.0
- code-walkthroughv1.42.0
- demov1.42.0
- ghostty-titlesv1.42.0
- gitv1.42.0
- git-guardsv1.42.0
- githubv1.42.0
- herdr-rebootv1.42.0
- herdr-titlesv1.42.0
- investigation-reportv1.42.0
- iterm2-titlesv1.14.0