git-worktrees
Git Worktrees
You are setting up an isolated workspace for a development task. Worktrees prevent work-in-progress from polluting the main working directory and enable easy cleanup or abandonment.
When to Activate
- After a plan is approved and before execution begins
- When the developer wants to work on a task in isolation
- NOT needed for single-file changes or documentation-only updates
Preconditions
Before setting up the worktree, validate inputs exist:
- Plan file: Use the Read tool to read
docs/plans/<issue-id>-plan.md. If the file does not exist, stop with: "No plan file found for this issue. Run planning first before setting up a worktree." - Issue ID: Verify the issue ID matches
^[A-Z]+-[0-9]+$. If invalid, stop and ask the developer.
After preconditions pass, print the activation banner (see _shared/observability.md):
More from brite-nites/britenites-claude-plugins
verification-before-completion
Ensures tasks are genuinely resolved before marking them done. Activates at task checkpoints during plan execution — validates that fixes actually work, tests genuinely pass, and acceptance criteria are met. Prevents premature completion declarations.
16writing-plans
Breaks work into bite-sized tasks before coding. Activates when a multi-step task needs planning — creates tasks small enough for a junior developer to follow (2-5 minutes each), with exact file paths, complete implementation details, and verification steps. References Linear issue context and project-specific test commands from CLAUDE.md.
14systematic-debugging
Four-phase root cause analysis for bug investigation. Activates when debugging unexpected behavior, failing tests, or production issues — follows reproduce, isolate, analyze, fix with defense-in-depth. Uses condition-based waiting instead of arbitrary delays. Available anytime, not tied to the inner loop sequence.
14refine-plan
Refines a v1 project plan into agent-ready tasks with clear context, implementation steps, and validation criteria. Use after /plan-project has produced a v1 plan.
13setup-claude-md
Generates a best-practices CLAUDE.md file for the project. Analyzes the codebase and applies Claude Code best practices for optimal agent performance. Use at project setup or after /create-issues.
13executing-plans
Executes a structured plan using subagent-per-task with TDD enforcement. Activates when given an approved plan to implement — launches fresh subagents for each task, enforces red-green-refactor, runs two-stage review per task, and checkpoints between tasks. Parallelizes independent tasks.
13