A structured workflow for developing a software feature through research, design, implementation, and validation phases. It requires approval between phases.

Clarifying feature requests, researching existing solutions, creating worktrees, implementing changes, and running build, test, and end-to-end checks.

It provides checkpoints for decisions and testing, reducing the chance of implementing the wrong feature or skipping important verification.

feature — Command for Claude Code by qwickapps/ai-sdlc-workflows

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/qwickapps/ai-sdlc-workflows

agentmods

npx agentmods add commands/qwickapps/ai-sdlc-workflows/feature

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/qwickapps/ai-sdlc-workflows/feature/github.svg)](https://agentmods.dev/commands/qwickapps/ai-sdlc-workflows/feature)

Your own site

<a href="https://agentmods.dev/commands/qwickapps/ai-sdlc-workflows/feature"><img src="https://agentmods.dev/badge/commands/qwickapps/ai-sdlc-workflows/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/qwickapps/ai-sdlc-workflows/feature"><img src="https://agentmods.dev/badge/commands/qwickapps/ai-sdlc-workflows/feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 10 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,703 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00010	$0.02703
Opus 5.5	$0.00004	$0.01081
Sonnet 5.5	$0.00002	$0.00541
Haiku 4.5	$0.00001	$0.00270

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

Security

Grade A, and why

feature scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- **For JIRA tickets**: Use JIRA CLI `jira issue attach <ticket-key> <frd-path>` or REST API `curl -X POST -H "X-Atlassian-Token: no-check" -F "file=@<frd-path>" <jira-url>/rest/api/2/issue/<ticket-key>/attachments`

claude/.claude/commands/feature.md · 341 lines

How it starts

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

Feature Development Workflow

You are now in Feature Development Mode. Follow this SDLC workflow strictly.

<critical_rules>

CRITICAL RULES

NEVER skip phases - each phase requires user approval before proceeding
NEVER auto-commit - always wait for explicit user approval
NEVER add legacy support unless explicitly requested
REUSE FIRST - always check existing solutions (see RESEARCH-DEPTH.md)
No attributions in commit messages
When blocked - STOP and discuss (see COMMUNICATION-PROTOCOL.md)
Validate thoroughly - build, test, E2E (see VALIDATION-GATES.md)
Use worktree script - NEVER use git commands directly (see WORKTREE-ENFORCEMENT.md) </critical_rules>

<interactive_setup>

Interactive Setup

Check if $ARGUMENTS is provided.

If $ARGUMENTS is empty or unclear, ask: "What feature would you like to implement? Please provide:

A brief description of the feature
Issue/ticket number (GitHub issue, JIRA ticket, etc.)
Or context about the problem being solved"

Extract and store the issue/ticket number from the response for:

Branch naming (feature/ISSUE-123)
Document attachment
Commit messages

Wait for response before proceeding. </interactive_setup>

Workflow Phases

<phase_1_requirements>

PHASE 1: Requirements (Product Manager)

Adopt the product-manager agent persona. Your job is to:

Understand the request - Ask clarifying questions about:
- What problem does this solve?
- Who are the users/stakeholders?
- What are the success criteria?
- What are the constraints (time, technical, business)?
- Are there existing solutions to reuse?
Document requirements - Create a Feature Request Document:
- Save to: .claude/engineering/frd/FRD-<id>-<short-name>.md
- Use template from .claude/templates/FRD.md
Attach FRD to issue/ticket (if issue number provided):
- For GitHub issues: Use gh issue comment <issue-number> --body-file <frd-path> or gh issue edit <issue-number> --add-attachment <frd-path> (if supported)
- For JIRA tickets: Use JIRA CLI jira issue attach <ticket-key> <frd-path> or REST API curl -X POST -H "X-Atlassian-Token: no-check" -F "file=@<frd-path>" <jira-url>/rest/api/2/issue/<ticket-key>/attachments
- If attachment fails or not applicable: Inform user to attach manually

Read the full file on GitHub · 341 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.

2mo ago First seen · 341 lines · 10 tokens per session scan A 7c855e2e3512

Subscribe to this mod's changes

feature is a command published in the GitHub repository qwickapps/ai-sdlc-workflows (2 stars, last pushed 7mo ago), licensed MIT. It adds 10 tokens to every session and 2,703 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Planning

feature

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Makes network callslowCapability

How it starts

Feature Development Workflow

CRITICAL RULES

Interactive Setup

Workflow Phases

PHASE 1: Requirements (Product Manager)

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

converge

implement

speckit.bug.fix