build-skill
Implement features and changes from implementation plans. Takes a plan file path as input and executes the implementation steps, then reports changes. Use when you have a detailed plan document and need to code it up, or want to implement specifications written in markdown format.
When & Why to Use This Skill
The build-skill is a powerful agentic tool designed to bridge the gap between planning and execution by automating the implementation of software features. It interprets detailed markdown implementation plans and autonomously performs file operations, code modifications, and system commands to transform technical specifications into functional code, ensuring consistency and speed in the development lifecycle.
Use Cases
- Feature Implementation: Automatically code complex modules, such as authentication systems or payment gateways, by following a structured implementation plan generated from architectural requirements.
- System Refactoring: Execute large-scale code changes and migrations across multiple files by providing a plan that outlines specific modification steps and patterns.
- Rapid Scaffolding: Quickly set up new project structures, middleware, or API endpoints by feeding the skill a markdown specification of the desired boilerplate and logic.
| name | build-skill |
|---|---|
| description | Implement features and changes from implementation plans. Takes a plan file path as input and executes the implementation steps, then reports changes. Use when you have a detailed plan document and need to code it up, or want to implement specifications written in markdown format. |
| allowed-tools | Read, Edit, Write, Bash, Glob, Grep |
Build
Implement code changes and features from a detailed implementation plan. This skill reads a plan file, follows its instructions step-by-step, and reports the completed work.
Prerequisites
- A plan file in markdown format (typically from
/quick-planskill) - The plan contains clear implementation steps
- You have access to the files that need to be modified
Workflow
- Validate plan - Confirm a plan file path has been provided
- Analyze plan - Read the plan and understand all implementation requirements
- Implement - Execute each step of the plan, modifying code as needed
- Report - Summarize changes and show diff statistics
Instructions
- If no plan file path is provided, ask the user to provide it and stop
- Read the plan file thoroughly - understand the full scope of work
- Think deeply about the implementation approach before starting
- Execute the plan step-by-step:
- Create new files as specified
- Modify existing files as outlined
- Follow code patterns and conventions from the plan
- After implementation, report:
- Summary of completed work (bullet points)
- Files changed with
git diff --stat
Examples
Example 1: Building from a plan
User: /build specs/authentication-system.md
Claude: [Reads authentication-system.md plan]
[Implements all steps]
Summary:
- Created JWT middleware in src/middleware/auth.ts
- Added login endpoint to src/routes/auth.ts
- Added password hashing utilities
[Shows git diff --stat output]
Example 2: Implementing a feature plan
User: Build the payment integration from specs/stripe-integration.md
Claude: [Reads plan and implements stripe integration]
Summary:
- Integrated Stripe API client
- Created payment endpoints
- Added webhooks for payment events