feat: upgrade /planwt to full orchestrator — one-shot plan + worktree creation#14
Merged
Merged
Conversation
…aft new /planwt now drives the complete planning sequence in one shot: 1. infers branch name from task description 2. writes .worktree-task.md with bounded contract 3. runs `wtcraft new <branch>` automatically Eliminates the manual two-step flow (plan → then separately create worktree). Synced across all three planwt.md locations. https://claude.ai/code/session_01A5oU4c7YSGpwatMA2PK1AE
git worktrees are local filesystem constructs — committing them as submodules was wrong. worktrees/ is now ignored globally. https://claude.ai/code/session_01A5oU4c7YSGpwatMA2PK1AE
… resolve conflicts
…e for Codex/Planner
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/planwtis now a full orchestrator — previously it only wrote.worktree-task.mdcontent, requiring the user to manually runwtcraft new <branch>as a separate step/planwt <task>drives the complete sequence in one shot:<type>/<short-slug>).worktree-task.mdwith bounded Scope, Steps, Off-limits, Context, and Verificationwtcraft new <branch-name>automaticallyplanwt.mdlocations (.claude/commands/,templates/,src/wtcraft/templates/)worktrees/to.gitignore— git worktrees are local constructs and should never be committedWhy
The two-step flow (
/planwt→wtcraft new) was unnecessary friction. The planner/orchestrator layer should drive all commands. A single/planwt add oauth loginnow takes you from intent to a ready worktree with no intermediate manual step.This also aligns with the design principle that wtcraft's Claude skills are the orchestration entry point, not just content generators.
Test plan
/planwt <task description>infers branch name and runswtcraft newautomatically.worktree-task.mdwtcraft statusshows the new worktreeplanwt.mdfiles are identicalhttps://claude.ai/code/session_01A5oU4c7YSGpwatMA2PK1AE
Generated by Claude Code