[tylercschneider]

One Sentence Summary

A developer who sets up symphony now gets the next-task, issue-strategist and issue-portfolio commands installed with its other commands, without keeping separate copies in dotfiles.

ACs Covered

• The next-task, issue-strategist and issue-portfolio commands are in symphony's commands folder, so its install links them like the other commands.
• The next-task command keeps its behaviour, including taking the next ready dyb_web work item when no number is named.
• The issue-strategist command points at the installed issue rules and label script instead of copies in dotfiles.
• The README lists all six commands.

Decision Log

Where should the next-task command and its change to take work items from dyb_web live?

It moves into symphony with the change, and the dotfiles pull request that made the change only in dotfiles is closed.

Should the issue-strategist and issue-portfolio commands move into symphony too?

All three commands that follow symphony's issue rules move together, rather than moving next-task alone.

Is the dotfiles pull request that taught next-task to take work items closed instead of merged, now that the command is moving to symphony?

It had already merged, so the command moves to symphony exactly as dotfiles main holds it, rather than closing that pull request.

Code Example

Not relevant.

Out of Scope

• Removing the three commands from the dotfiles repo happens in a dotfiles pull request after this one merges.

Ticket Billed Against

Not specified.

Tokens Used

Not measured.

Effort

Not measured.

Time Spent

Not measured.

---

Generation Metadata

Scribe: pr-scribe 9d1ee89
Rules: pr-body 9d1ee89, draft-reading 0d470c5, writing-style c3c2f61
Model: claude-sonnet-5-5, cc 2.1.314

🤖 Generated with Claude Code