implement-feature

implement-feature is a command for Claude Code from alexgvozden/claude-plugin. It costs 13 tokens per session (2,664 once invoked), scanned A, original, MIT.

A command that carries out a software feature plan one step at a time from a planning document.

In plain words
What is it for?
Use it when a feature plan has defined phases and tasks, and you want those tasks executed with review points.
Why use it?
It helps keep implementation tied to agreed requirements, tests, and acceptance checks instead of starting from an incomplete plan.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md). Also seen: mentions CLAUDE.md.

Good fit Use it when a feature plan has defined phases and tasks, and you want those tasks executed with review points.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/alexgvozden/claude-plugin/implement-feature
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/alexgvozden/claude-plugin

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for implement-feature

README.md
[![agentmods](https://agentmods.dev/badge/commands/alexgvozden/claude-plugin/implement-feature/github.svg)](https://agentmods.dev/commands/alexgvozden/claude-plugin/implement-feature)
Your own site
<a href="https://agentmods.dev/commands/alexgvozden/claude-plugin/implement-feature"><img src="https://agentmods.dev/badge/commands/alexgvozden/claude-plugin/implement-feature/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for implement-feature

Your own site · 80×15
<a href="https://agentmods.dev/commands/alexgvozden/claude-plugin/implement-feature"><img src="https://agentmods.dev/badge/commands/alexgvozden/claude-plugin/implement-feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,664 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00013 $0.02664
Opus 5.5 $0.00005 $0.01066
Sonnet 5.5 $0.00003 $0.00533
Haiku 4.5 $0.00001 $0.00266

Measured 2mo ago against content hash 08e0da0901f2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

implement-feature scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/implement-feature.md · 368 lines

How it starts

The opening of the file, as written. The whole thing — 368 lines — stays where its author put it; the contents beside it link to each section on GitHub.

IMPORTANT: IMPLEMENTATION WITH STEP-BY-STEP EXECUTION

This command implements a feature based on a planning document, executing one logical step at a time with user review checkpoints.

Required Parameter

Planning Document Path: You MUST provide the path to the feature planning markdown file.

Example usage:

/implement-feature planning/my-feature.md

Instructions

1. Validate Planning Document

Read the planning document and verify:

  1. File exists at the provided path
  2. Contains ### Implementation Phases with clear phase breakdown and specific tasks
  3. Has required sections: Overview, Requirements, Technical Design, Testing Strategy, Acceptance Criteria

If validation fails: Inform user what's missing and suggest running /plan-feature first. EXIT without proceeding.

2. Create Implementation Plan

If all validation passes, create a detailed implementation plan:

Extract Phases and Tasks Parse the ### Implementation Phases section Create a structured list of all phases and tasks Number tasks hierarchically (1.1, 1.2, 2.1, 2.2, etc.) Identify file paths for each task Note any dependencies between tasks Add Progress Tracker to Planning Document IMPORTANT: Update the planning document by adding a progress tracker table at the TOP of the file (right after the feature title, before Overview):

Feature: [Feature Name]

Implementation Progress

Phase Task Status Notes
Phase 1: [Name]
1.1 [Task description] ⏸️ Pending
1.2 [Task description] ⏸️ Pending
Phase 2: [Name]
2.1 [Task description] ⏸️ Pending
2.2 [Task description] ⏸️ Pending
Phase 3: [Name]
3.1 [Task description] ⏸️ Pending

Legend: ✅ Complete | 🔄 In Progress | ⏸️ Pending | ❌ Blocked


Overview

[Rest of original planning document content...] Present Implementation Plan to User Show the user a summary:

📋 Implementation Plan Created

Read the full file on GitHub · 368 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 368 lines · 13 tokens per session scan A 08e0da0901f2

Subscribe to this mod's changes

implement-feature is a command published in the GitHub repository alexgvozden/claude-plugin (11 stars, last pushed 11mo ago), licensed MIT. It adds 13 tokens to every session and 2,664 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

implement-feature compared with commands from other repositories

implement-feature next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
implement-featurealexgvozden/claude-pluginCommand1111mo agoMITA13Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code