multi-agent-squad: Command for Claude Code

.claude/commands/start-feature.md

start-feature is a command for Claude Code from bijutharakan/multi-agent-squad. It costs 23 tokens per session (584 once invoked), scanned A, original, MIT.

A command that starts a software feature project by collecting requirements, creating a GitHub issue, preparing separate workspaces, and assigning coding agents.

In plain words
What is it for?
Use it to start features, record their requirements, identify affected parts of a project, create worktrees, and begin multi-agent development.
Why use it?
It organizes the early work needed before development begins and keeps the feature tracked.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is bijutharakan/multi-agent-squad's own configuration. It tells Claude Code how to work on multi-agent-squad itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything multi-agent-squad configures →

Reuse

Borrowing it

Nothing to install: this file belongs to bijutharakan/multi-agent-squad. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/bijutharakan/multi-agent-squad/main/.claude/commands/start-feature.md
Clone the repo
git clone --depth 1 https://github.com/bijutharakan/multi-agent-squad

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 start-feature

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/bijutharakan/multi-agent-squad/start-feature"><img src="https://agentmods.dev/badge/commands/bijutharakan/multi-agent-squad/start-feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 584 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.00023 $0.00584
Opus 5.5 $0.00009 $0.00234
Sonnet 5.5 $0.00005 $0.00117
Haiku 4.5 $0.00002 $0.00058

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

Security

Grade A, and why

start-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.

.claude/commands/start-feature.md · 90 lines

How it starts

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

Start Feature Command

This command initiates a new feature development with full Multi-Agent Squad orchestration.

What This Command Does

  1. Gathers Requirements - Prompts for feature details
  2. Creates GitHub Issue - Tracks the feature (if integrated)
  3. Analyzes Impact - Determines which repositories are affected
  4. Creates Worktrees - Sets up isolated development environments
  5. Assigns Agents - Deploys appropriate specialists
  6. Begins Development - Kicks off implementation

Usage

Simply say:

  • /start-feature
  • "Start a new feature"
  • "I want to add [feature description]"

Interactive Process

I'll ask you:

  1. Feature Name (kebab-case, e.g., "user-authentication")
  2. Feature Description (what should it do?)
  3. User Story (as a user, I want...)
  4. Affected Components (or I'll analyze)
  5. Priority (high/medium/low)
  6. Target Deadline (optional)

Example Flow

You: /start-feature

Me: Let's start a new feature! What would you like to call it?

You: payment-integration

Me: Great! Please describe what this feature should do.

You: Add Stripe payment processing for subscriptions

Me: I'll analyze which repositories this affects...
- Backend: API endpoints for payment processing
- Frontend: Payment forms and subscription management
- Database: Schema updates for subscriptions

Creating worktrees:
✓ backend/feature-payment-integration
✓ frontend/feature-payment-integration

Assigning agents:
- Backend Developer Agent → Payment API
- Frontend Developer Agent → Payment UI
- Database Expert → Schema updates

GitHub Issue #47 created: "Feature: Payment Integration"

Ready to begin development! The PM Agent will now create detailed requirements.

What Happens Next

  1. Product Manager Agent creates detailed requirements
  2. Solution Architect designs the implementation
  3. Developers work in their assigned worktrees
  4. Progress is tracked in GitHub
  5. PRs are created when ready
  6. Review by senior engineers
  7. Merge and cleanup when complete

Read the full file on GitHub · 90 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 · 90 lines · 23 tokens per session scan A ea41977dd803

Subscribe to this mod's changes

start-feature is a command published in the GitHub repository bijutharakan/multi-agent-squad (88 stars, last pushed 1y ago), licensed MIT. It adds 23 tokens to every session and 584 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

start-feature compared with commands from other repositories

start-feature next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
start-featurebijutharakan/multi-agent-squadCommand881y agoMITA23Claude Code
merge-conflict-analysisrjmurillo/ai-agentsCommand49yesterdayMITA0GitHub Copilot
release-notesOpenHands/extensionsCommand176yesterdayMITA44Claude Code
commitechoVic/blade-codeCommand18124d agoMITA8Claude Code
repo-audittractorjuice/arc-kitCommand2.3k2d agononeA29Claude Code
propsmill/infrahub-mcpCommand10yesterdayApache-2.0A18Claude Code
codex-reviewoalders/kitchen-sinkCommand53d agoMITA41Claude Code