feature-dev-guide

feature-dev-guide is a command for Claude Code from eddiebelaval/squire. It costs 0 tokens per session (2,308 once invoked), scanned A, original, MIT.

A guided feature-development process that combines planning and implementation with lessons on professional software practices. It covers the path from understanding a user need to preparing the code for development.

In plain words
What is it for?
Use it to clarify a feature, compare approaches, inspect the project, create a Git branch, and build an implementation plan.
Why use it?
It helps newer developers learn how to define scope, explore an existing codebase, estimate work, and organize changes before coding.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

Good fit Use it to clarify a feature, compare approaches, inspect the project, create a Git branch, and build an implementation plan.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/eddiebelaval/squire/feature-dev-guide
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/eddiebelaval/squire

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 feature-dev-guide

README.md
[![agentmods](https://agentmods.dev/badge/commands/eddiebelaval/squire/feature-dev-guide/github.svg)](https://agentmods.dev/commands/eddiebelaval/squire/feature-dev-guide)
Your own site
<a href="https://agentmods.dev/commands/eddiebelaval/squire/feature-dev-guide"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/feature-dev-guide/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 feature-dev-guide

Your own site · 80×15
<a href="https://agentmods.dev/commands/eddiebelaval/squire/feature-dev-guide"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/feature-dev-guide.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 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,308 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.00000 $0.02308
Opus 5 $0.00000 $0.01154
Sonnet 5 $0.00000 $0.00462
Haiku 4.5 $0.00000 $0.00231

Measured 5d ago against content hash 89f9485877a5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

feature-dev-guide 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 5d 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/feature-dev-guide.md · 469 lines

How it starts

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

/feature-dev - Your Personal Development Mentor

What Makes This Command Special? 🌟

This isn't just building a feature - it's a complete learning experience. Think of it as having a patient senior developer sitting next to you, teaching you professional practices while building real features.


How It's Different

Other Commands:

/start feature-name
→ Creates branch, plans, ready to code
→ Fast and efficient

/feature-dev:

/feature-dev
→ Discovers user needs
→ Explains technical decisions
→ Teaches as it builds
→ Educational + productive

The Complete Journey 🗺️

Phase 1: Discovery (10 min)

What happens:

  • Understand the problem
  • Define success criteria
  • Explore alternatives

What you learn:

  • Product thinking
  • User-first approach
  • Scope definition

Phase 2: Planning (15 min)

What happens:

  • Search existing codebase
  • Break down components
  • Estimate complexity

What you learn:

  • Code exploration
  • Architecture thinking
  • Resource planning

Phase 3: Setup (5 min)

What happens:

  • Create feature branch
  • Build todo list
  • Confirm approach

What you learn:

  • Git workflow
  • Task breakdown
  • Planning methodology

Phase 4-6: Building (1-4 hours)

What happens:

  • Data structures first
  • Then logic
  • Then UI
  • Polish throughout

What you learn:

  • Bottom-up development
  • Component architecture
  • State management
  • Error handling
  • Accessibility
  • Loading states

Phase 7: Quality (30 min)

What happens:

  • Write tests
  • Visual testing with Playwright
  • Documentation

What you learn:

  • Testing strategies
  • Automation
  • Documentation practices

Phase 8: Ship (15 min)

What happens:

  • Final review
  • Create PR
  • Celebrate!

What you learn:

  • Quality checklist
  • PR best practices
  • Professional delivery

Real Example Walkthrough

User Says:

/feature-dev

Claude Responds:

🎓 Welcome to Feature Development Workshop!

I'm going to walk you through building a feature
like a professional developer would - step by step,
teaching you along the way.

Let's start with understanding what you want to build.

❓ What problem are you trying to solve?

Read the full file on GitHub · 469 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. 5d ago First seen · 469 lines · 0 tokens per session scan A 89f9485877a5

Subscribe to this mod's changes

feature-dev-guide is a command published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 23d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,308 tokens. 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-09-03.