spec

Presents an implementation plan for user approval before making code changes.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/sergeiwallace/skills --skill spec-sergeiwallace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/sergeiwallace/skills/tree/main/skills/spec
Command: npx skills add https://github.com/sergeiwallace/skills --skill spec-sergeiwallace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents unwanted or premature code modifications by requiring an explicit plan review and approval step before any implementation begins. ## Core Features & Use Cases - Plan-First Workflow: Analyzes the request by reading relevant files and researching the codebase before proposing anything. - Structured Plan Presentation: Lists what will change (files, functions, configs), why, and any trade-offs or alternatives considered. - Approval Gate: Waits for explicit user approval and produces no persistent document, keeping the interaction lightweight. - Use Case: Before adding a health-check endpoint to a service, invoke the skill to get a plan describing the exact files and functions to modify, then approve it only when the approach looks right. ## Quick Start Ask the agent to run /spec followed by a task description, such as planning how to add a health-check endpoint, and review the proposed plan before approving.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I review a plan before an AI makes code changes?

Invoke /spec followed by your task description. The skill analyzes the request, presents a plan listing what will change and why, then waits for your explicit approval before implementing anything.

How to use the spec skill in Claude Code?

Install it with gh skill install sergeiwallace/skills spec --agent claude-code --scope user, then type /spec followed by a task description in chat. It returns a plan and pauses until you approve.

Does the spec skill create any files or documents?

No. The skill is an interactive plan-then-approve gate that presents the plan in chat and produces no persistent document. Files are only changed after you approve the plan and implementation begins.

What happens if I reject the proposed implementation plan?

Nothing changes. The skill explicitly waits for approval and does not proceed until you say to go ahead, so rejecting or ignoring the plan leaves your codebase untouched.

When should I not use a plan-approval workflow?

Skip it for trivial, low-risk edits where a review gate adds overhead, such as typo fixes or one-line changes. The approval step is most valuable for multi-file or architecturally significant modifications.