builder-set

Set the active plan for a Claude builder session and persist it.

1|Updated Aug 6, 2022
One-click install
npx skills add https://github.com/wormholecowboy/.dotfiles --skill builder-set
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: builder-set
Source: https://github.com/wormholecowboy/.dotfiles/tree/main/claude-config/skills/builder-set
Command: npx skills add https://github.com/wormholecowboy/.dotfiles --skill builder-set

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill lets you quickly switch the active plan for the current Claude builder session and persist that choice for later sessions, eliminating manual context reconstruction.

Core Features & Use Cases

  • Set the active plan by name to switch context across tasks.
  • Persist the current plan to .claude/skills/builder/.current-plan for quick resumption.
  • Display or infer status from the plan's state.yaml and enable /builder-resume to load full context.

Quick Start

Use the builder-set command to activate a plan, for example: /builder-set my-feature

Frequently Asked Questions about builder-set

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I switch the active plan and persist context for a Claude builder session?

To switch the active plan, use the builder-set command with an explicit plan name. This persists your choice to .claude/skills/builder/.current-plan, enabling quick context resumption across sessions.

Can I set the active plan automatically based on recent work and file paths?

Yes, setting the active plan supports context-based inference. It determines the current plan by analyzing recent work and file paths, eliminating the need for manual context reconstruction.

What is the best way to resume a workflow after switching plans in the builder?

The best way to resume a workflow is using the /builder-resume command. It reads the persisted .current-plan file and the plan's state.yaml to load full context and display current status.

Do I need a specific directory structure to manage and set builder plans?

Yes, you need the .claude/plans directory to store your plans. The skill interacts with this directory and writes the active plan status to .claude/skills/builder/.current-plan.

Why does my builder session lose context when switching between different plans?

Context is lost without persisting the active plan. The builder-set skill solves this by writing the current plan to a local file, allowing later sessions to read the state and resume seamlessly.

What is a builder plan and when do I need to set it explicitly?

A builder plan defines the active workflow context. You need to set it explicitly by passing a plan name when automatic inference from recent files cannot accurately determine your intended task.