plan-change

Orchestrates multi-agent triage and delegates OpenSpec change artifact creation to a subagent.

Updated Nov 7, 2023
One-click install
npx skills add https://github.com/lstellway/nixfiles --skill plan-change-lstellway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-change
Source: https://github.com/lstellway/nixfiles/tree/main/modules/home-manager/claude/skills/plan-change
Command: npx skills add https://github.com/lstellway/nixfiles --skill plan-change-lstellway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Planning a non-trivial code change often requires input from multiple domain specialists and produces inconsistent specs. This Skill structures that process: it validates the request's scope, consults relevant specialist agents in parallel, resolves open decisions with you, and delegates OpenSpec artifact creation to a subagent. ## Core Features & Use Cases - Shape pre-flight: Detects requests that are too big, too small, or ambiguous before spending agent budget, and proposes splits or clarifications. - Dynamic agent routing: Discovers specialist agents from ~/.claude/agents/ and .claude/agents/ and fans out to 2-4 relevant ones in parallel. - Delegated artifact creation: Spawns a general-purpose subagent that runs the openspec-ff-change procedure against a synthesized brief, keeping artifact text out of the main thread. - Use Case: You want to add Google sign-in to your app. The skill checks scope, consults security, UX, and framework specialists, resolves tradeoffs with you, then produces an OpenSpec change with proposal and tasks files. ## Quick Start Ask the assistant to plan a change by describing what you want to build, for example: plan a change to add Google sign-in to the public site.

Frequently Asked Questions about plan-change

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

FAQPage Schema
How do I plan a software change with multiple specialist agents?

Describe the change you want to build as the skill's input. It triages the request, discovers specialist agents from ~/.claude/agents/ and .claude/agents/, consults 2-4 relevant ones in parallel, then delegates OpenSpec artifact creation to a subagent.

What is OpenSpec and why does this skill require it?

OpenSpec is a spec-driven change workflow whose artifacts (proposal, tasks) live under openspec/changes/. The skill bails if openspec/config.yaml is absent, since its output is an OpenSpec change; run openspec init first to set it up.

What happens if my change request is too big or too small?

The shape pre-flight flags oversized requests with a concrete split sketch into separate changes, and flags trivial ones (typos, config tweaks) as better suited to a direct PR. It stops in both cases unless you explicitly tell it to proceed.

Can I use this skill without any specialist agents installed?

No. If no agents with name and description frontmatter are found in ~/.claude/agents/ or .claude/agents/, the skill stops and suggests installing agents via the agent-domain, agent-discipline, agent-technology, or agent-persona skills.

Why does the skill delegate spec writing to a subagent?

The subagent runs the openspec-ff-change procedure non-interactively against a complete brief and returns only artifact paths and a summary. This keeps lengthy artifact text out of the main conversation thread and enforces that tradeoffs are resolved beforehand.