implement-feature

Implement approved feature plans using git worktrees and phased execution.

1|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/VIPER-Metrics/claude-code-skills --skill implement-feature-viper-metrics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement-feature
Source: https://github.com/VIPER-Metrics/claude-code-skills/tree/main/skills/implement-feature
Command: npx skills add https://github.com/VIPER-Metrics/claude-code-skills --skill implement-feature-viper-metrics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams implement a feature strictly from an approved feature plan, enabling isolated development using git worktrees to avoid disrupting the main branch.

Core Features & Use Cases

  • Load the feature plan from wiki/issues/$ARGUMENTS/feature-plan.md
  • Create a dedicated git worktree from master for isolated development
  • Validate the plan's prerequisites, including the data model changes checklist
  • Execute the plan in phases (Data Layer, Server Layer, Client Layer, Integration)
  • Create and publish a test plan to wiki and post it to the GitHub issue
  • Post-implementation steps include committing changes, verifying final state, and preparing a PR

Quick Start

Use the implement-feature skill to initiate work on a feature from an approved plan. Provide the issue number to begin (e.g., /implement-feature 123).

Frequently Asked Questions about implement-feature

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

FAQPage Schema
How do I implement a feature from an approved plan using git worktree?▼

To implement a feature using a git worktree, load the approved plan, create a master-based worktree for isolated development, validate prerequisites, execute phases, and commit changes before preparing a PR.

What is the best way to isolate feature work from the main branch?▼

The best way to isolate feature work is creating a dedicated git worktree from master, preventing disruption to the main branch while you validate prerequisites and execute phased implementation.

How do I execute a feature plan across data, server, and client layers?▼

Execute a feature plan across layers by following phased implementation: Data Layer, Server Layer, Client Layer, and Integration, validating prerequisites and data model changes before starting each phase.

Do I need an approved feature plan before starting implementation?▼

Yes, you need an approved feature plan loaded from wiki/issues before starting implementation, as the workflow validates its prerequisites and data model changes checklist.

Can I make database changes without confirmation during feature implementation?▼

No, database changes require explicit confirmation during feature implementation, ensuring data model modifications in the Data Layer phase are reviewed before proceeding to subsequent layers.

How do I publish a test plan and prepare a PR after feature implementation?▼

Publish a test plan to the wiki and GitHub issue after phased implementation, then verify the final state, commit all changes, and prepare a PR to merge the isolated worktree.