prepare-workspace-for-plan
Use when you have a plan file ready and need to create an isolated git worktree for implementation - creates worktree in parent directory following project conventions and moves the plan file
Security Assessment
About prepare-workspace-for-plan
The 'prepare-workspace-for-plan' skill is designed to assist users in creating an isolated git worktree for the purpose of implementing a plan. This skill solves the problem of organizing the workflow in a git repository when a plan has been finalized and needs to be separated into its own working environment. By utilizing a git worktree, users can work on the plan without affecting the main branch or other workspaces, maintaining a clean and efficient development process. This ensures that any changes made during the implementation of the plan will not impact the ongoing work in the primary workspace until they are explicitly merged.
FAQ
How do I create a new workspace using this skill?
To create a new workspace, choose a name based on the project convention (e.g., 'fix-<description>' for bug fixes or 'feat-<description>' for new features). Then, use the 'git worktree add' command to create the new worktree and set up the branch.
What if my git repository doesn't support worktrees?
This skill requires that your git repository supports worktrees. If your repository doesn't support them, you may need to upgrade git or consider using an alternative approach, such as creating new branches without worktrees.
Where is the plan file moved to in the new workspace?
The plan file is moved from the 'plans/' directory in the original workspace to a newly created 'plans/' directory in the new workspace, maintaining the same directory structure.
Are changes in the new worktree automatically reflected in the main branch?
No, changes made in the new worktree will not affect the main branch until they are merged. This allows you to work on the plan independently and isolate changes until they are ready to be integrated.
Is there any git history shared between workspaces?
Yes, the new worktree shares the git history with the main branch but has its own working directory. This ensures that the changes in the new workspace are tracked and can be merged back into the main branch later.
Install prepare-workspace-for-plan
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
go-vikunja/vikunja