Skip to main content
command CX Codex

feature-development · ormus-solutions — Claude Code command for feature delivery

feature-development is a Claude Code command that coordinates feature work from requirements through deployment preparation. It starts from a feature description.

MIT ★ 126 updated 2026-10-04

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add Ormus-Solutions/LibreUIUX-Claude-Code
/plugin install backend-development@libreuiux
Open on GitHub

What feature-development does

The command divides feature work into stages: requirements analysis, architecture design, risk assessment, implementation, testing, and deployment preparation. Specialized subagents handle the stages, with earlier results passed forward as context.

Its configuration describes traditional, TDD, BDD, and DDD methods, plus direct, canary, feature-flag, blue-green, and A/B-test deployment strategies. The workflow covers frontend and backend work, data integration, automated tests, and security checks. Claude Code setup starts by adding the marketplace, then installing backend-development@libreuiux.

What it helps with

  • turn a feature brief into requirements and acceptance criteria
  • design architecture and APIs for a new feature
  • coordinate frontend and backend implementation
  • prepare automated tests and security checks
  • choose a deployment strategy for a feature

Example prompts for the agent

  • Develop a reporting export feature from requirements through deployment.
  • Plan a new feature with TDD and outline its implementation stages.
  • Build a feature plan that includes security checks and automated tests.

How to install feature-development

1Plugin marketplace

/plugin marketplace add Ormus-Solutions/LibreUIUX-Claude-Code
/plugin install backend-development@libreuiux

2Manually: put the files in place

.claude/commands/feature-development.md

Call it with /feature-development. For all projects use ~/.claude/commands/

Questions about feature-development

How do I install feature-development in Claude Code?

Run /plugin marketplace add Ormus-Solutions/LibreUIUX-Claude-Code, then /plugin install backend-development@libreuiux. The command file is .claude/commands/feature-development.md.

What does feature-development do?

It organizes feature work into stages, from requirements analysis and architecture design to implementation, testing, and deployment preparation. Specialized subagents receive context from earlier stages.

Which development methods does feature-development support?

Its configuration describes traditional, TDD, BDD, and DDD methods. Deployment strategies include direct, canary, feature-flag, blue-green, and A/B testing.

Source text

feature-development.md · MIT
---
description: "Orchestrate a feature from requirements through implementation, tests, and deployment"
argument-hint: "[feature description]"
---

Orchestrate end-to-end feature development from requirements to production deployment:

[Extended thinking: This workflow orchestrates specialized agents through comprehensive feature development phases - from discovery and planning through implementation, testing, and deployment. Each phase builds on previous outputs, ensuring coherent feature delivery. The workflow supports multiple development methodologies (traditional, TDD/BDD, DDD), feature complexity levels, and modern deployment strategies including feature flags, gradual rollouts, and observability-first development. Agents receive detailed context from previous phases to maintain consistency and quality throughout the development lifecycle.]

## Configuration Options

### Development Methodology
- **traditional**: Sequential development with testing after implementation
- **tdd**: Test-Driven Development with red-green-refactor cycles
- **bdd**: Behavior-Driven Development with scenario-based testing
- **ddd**: Domain-Driven Design with bounded contexts and aggregates

### Feature Complexity
- **simple**: Single service, minimal integration (1-2 days)
- **medium**: Multiple services, moderate integration (3-5 days)
- **complex**: Cross-domain, extensive integration (1-2 weeks)
- **epic**: Major architectural changes, multiple teams (2+ weeks)

### Deployment Strategy
- **direct**: Immediate rollout to all users
- **canary**: Gradual rollout starting with 5% of traffic
- **feature-flag**: Controlled activation via feature toggles
- **blue-green**: Zero-downtime deployment with instant rollback
- **a-b-test**: Split traffic for experimentation and metrics

## Phase 1: Discovery & Requirements Planning

1. **Business Analysis & Requirements**
   - Use Task tool with subagent_type="business-analytics::business-analyst"
   - Prompt: "Analyze feature requirements for: $ARGUMENTS. Define user stories, acceptance criteria, success metrics, and business value. Identify stakeholders, dependencies, and risks. Create feature specification document with clear scope boundaries."
   - Expected output: Requirements document with user stories, success metrics, risk assessment
   - Context: Initial feature request and business context

2. **Technical Architecture Design**
   - Use Task tool with subagent_type="comprehensive-review::architect-review"
   - Prompt: "Design technical architecture for feature: $ARGUMENTS. Using requirements: [include business analysis from step 1]. Define service boundaries, API contracts, data models, integration points, and technology stack. Consider scalability, performance, and security requirements."
   - Expected output: Technical design document with architecture diagrams, API specifications, data models
   - Context: Business requirements, existing system architecture

3. **Feasibility & Risk Assessment**
   - Use Task tool with subagent_type="security-scanning::security-auditor"
   - Prompt: "Assess security implications and risks for feature: $ARGUMENTS. Review architecture: [include technical design from step 2]. Identify security requirements, compliance needs, data privacy concerns, and potential vulnerabilities."
   - Expected output: Security assessment with risk matrix, compliance checklist, mitigation strategies
   - Context: Technical design, regulatory requirements

## Phase 2: Implementation & Development

4. **Backend Services Implementation**
   - Use Task tool with subagent_type="backend-architect"
   - Prompt: "Implement backend services for: $ARGUMENTS. Follow technical design: [include architecture from step 2]. Build RESTful/GraphQL APIs, implement business logic, integrate with data layer, add resilience patterns (circuit breakers, retries), implement caching strategies. Include feature flags for gradual rollout."
   - Expected output: Backend services with APIs, business logic, database integration, feature flags
   - Context: Technical design, API contracts, data models

5. **Frontend Implementation**
   - Use Task tool with subagent_type="frontend-mobile-development::frontend-developer"
   - Prompt: "Build frontend components for: $ARGUMENTS. Integrate with backend APIs: [include API endpoints from step 4]. Implement responsive UI, state management, error handling, loading states, and analytics tracking. Add feature flag integration for A/B testing capabilities."
   - Expected output: Frontend components with API integration, state management, analytics
   - Context: Backend APIs, UI/UX designs, user stories

6. **Data Pipeline & Integration**
   - Use Task tool with subagent_type="data-engineering::data-engineer"
   - Prompt: "Build data pipelines for: $ARGUMENTS. Design ETL/ELT processes, implement data validation, create analytics events, set up data quality monitoring. Integrate with product analytics platforms for feature usage tracking."
   - Expected output: Data pipelines, analytics events, data quality checks
   - Context: Data requirements, analytics needs, existing data infrastructure

## Phase 3: Testing & Quality Assurance

7. **Automated Test Suite**
   - Use Task tool with subagent_type="unit-testing::test-automator"
   - Prompt: "Create comprehensive test suite for: $ARGUMENTS. Write unit tests for backend: [from step 4] and frontend: [from step 5]. Add integration tests for API endpoints, E2E tests for critical user journeys, performance tests for scalability validation. Ensure minimum 80% code coverage."
   - Expected output: Test suites with unit, integration, E2E, and performance tests
   - Context: Implementation code, acceptance criteria, test requirements

8. **Security Validation**
   - Use Task tool with subagent_type="security-scanning::security-auditor"
   - Prompt: "Perform security testing for: $ARGUMENTS. Review implementation: [include backend and frontend from steps 4-5]. Run OWASP checks, penetration testing, dependency scanning, and compliance validation. Verify data encryption, authentication, and authorization."
   - Expected output: Security test results, vulnerability report, remediation actions
   - Context: Implementation code, security requirements

9. **Performance Optimization**
   - Use Task tool with subagent_type="application-performance::performance-engineer"
   - Prompt: "Optimize performance for: $ARGUMENTS. Analyze backend services: [from step 4] and frontend: [from step 5]. Profile code, optimize queries, implement caching, reduce bundle sizes, improve load times. Set up performance budgets and monitoring."
   - Expected output: Performance improvements, optimization report, performance metrics
   - Context: Implementation code, performance requirements

## Phase 4: Deployment & Monitoring

10. **Deployment Strategy & Pipeline**
    - Use Task tool with subagent_type="deployment-strategies::deployment-engineer"
    - Prompt: "Prepare deployment for: $ARGUMENTS. Create CI/CD pipeline with automated tests: [from step 7]. Configure feature flags for gradual rollout, implement blue-green deployment, set up rollback procedures. Create deployment runbook and rollback plan."
    - Expected output: CI/CD pipeline, deployment configuration, rollback procedures
    - Context: Test suites, infrastructure requirements, deployment strategy

11. **Observability & Monitoring**
    - Use Task tool with subagent_type="observability-monitoring::observability-engineer"
    - Prompt: "Set up observability for: $ARGUMENTS. Implement distributed tracing, custom metrics, error tracking, and alerting. Create dashboards for feature usage, performance metrics, error rates, and business KPIs. Set up SLOs/SLIs with automated alerts."
    - Expected output: Monitoring dashboards, alerts, SLO definitions, observability infrastructure
    - Context: Feature implementation, success metrics, operational requirements

12. **Documentation & Knowledge Transfer**
    - Use Task tool with subagent_type="documentation-generation::docs-architect"
    - Prompt: "Generate comprehensive documentation for: $ARGUMENTS. Create API documentation, user guides, deployment guides, troubleshooting runbooks. Include architecture diagrams, data flow diagrams, and integration guides. Generate automated changelog from commits."
    - Expected output: API docs, user guides, runbooks, architecture documentation
    - Context: All previous phases' outputs

## Execution Parameters

### Required Parameters
- **--feature**: Feature name and description
- **--methodology**: Development approach (traditional|tdd|bdd|ddd)
- **--complexity**: Feature complexity level (simple|medium|complex|epic)

### Optional Parameters
- **--deployment-strategy**: Deployment approach (direct|canary|feature-flag|blue-green|a-b-test)
- **--test-coverage-min**: Minimum test coverage threshold (default: 80%)
- **--performance-budget**: Performance requirements (e.g., <200ms response time)
- **--rollout-percentage**: Initial rollout percentage for gradual deployment (default: 5%)
- **--feature-flag-service**: Feature flag provider (launchdarkly|split|unleash|custom)
- **--analytics-platform**: Analytics integration (segment|amplitude|mixpanel|custom)
- **--monitoring-stack**: Observability tools (datadog|newrelic|grafana|custom)

## Success Criteria

- All acceptance criteria from business requirements are met
- Test coverage exceeds minimum threshold (80% default)
- Security scan shows no critical vulnerabilities
- Performance meets defined budgets and SLOs
- Feature flags configured for controlled rollout
- Monitoring and alerting fully operational
- Documentation complete and approved
- Successful deployment to production with rollback capability
- Product analytics tracking feature usage
- A/B test metrics configured (if applicable)

## Rollback Strategy

If issues arise during or after deployment:
1. Immediate feature flag disable (< 1 minute)
2. Blue-green traffic switch (< 5 minutes)
3. Full deployment rollback via CI/CD (< 15 minutes)
4. Database migration rollback if needed (coordinate with data team)
5. Incident post-mortem and fixes before re-deployment

Feature description: $ARGUMENTS

© Seth Hobson · MIT · Ormus-Solutions/LibreUIUX-Claude-Code

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

feature-development by other authors comes first.

feature-development Seth Hobson feature-development runs a feature through requirements, architecture and implementation step by step, pausing for your approval and keeping state in .feature-dev/. CX Codex +1 ★ 42,780repo stars backend-development-feature-development sickn33 The backend-development-feature-development skill coordinates feature work from requirements and architecture through implementation, testing, and rollout. Use it for changes spanning services or teams. CX Codex +1 2installs devkit.feature-development Giuseppe Trisciuoglio devkit.feature-development — a slash command that carries a new feature through seven phases: code exploration, questions, architecture, implementation, review. Handy when you start from scratch. CX Codex +1 ★ 372repo stars feature-dev notedit feature-dev walks the agent through eight phases: codebase exploration, clarifying questions, architecture options, implementation, tests and review. CX Codex +1 552installs generic-feature-developer travisjneuman generic-feature-developer walks a feature from reading the codebase to picking patterns, shipping small commits and checking edge cases before you close it. CX Codex +1 142installs feature aeonfun The feature skill builds repository enhancements and opens PRs. Choose a sweep across watched repos, one external target, or a dormant project. CX Codex +1 ★ 797repo stars instrument-feature-flags PostHog instrument-feature-flags — a Claude Code skill that gates new functionality with PostHog feature flags. Runs after implementing features or during PR reviews to safeguard rollouts. CX Codex +1 630installs

From the same set42

The whole set →
performance-optimization performance-optimization coordinates end-to-end performance audits, database optimizations, frontend tuning, and load testing. CX Codex +1 ★ 126repo stars incident-response The incident-response command coordinates incident triage, investigation, mitigation, and recovery. Give it an incident description to start a staged response. CX Codex +1 ★ 126repo stars ui-responsive The ui-responsive command analyzes a component or page at five breakpoints and gives specific fixes for mobile, tablet and desktop layouts. CX Codex +1 ★ 126repo stars jungian-archetypes jungian-archetypes maps twelve brand archetypes to UI layout, typography, animations, and Tailwind styling. CX Codex +1 ★ 126repo stars legacy-modernize legacy-modernize — a command for gradually updating legacy systems using the strangler fig pattern. Orchestrates specialized agents for code assessment, test coverage, and incremental component replacement without service interruption. CX Codex +1 ★ 126repo stars design-masters design-masters is a Claude Code skill that draws on established designers’ work to guide UI decisions. The agent calls it for a named reference or a direction for a design. CX Codex +1 ★ 126repo stars archetypal-alchemist archetypal-alchemist pairs a Jungian archetype with a Major Arcana card to shape layout, color and mood, then returns Tailwind components and palettes built around that pairing. CX Codex ★ 126repo stars modern-card modern-card is a Claude Code prompt for styling modern card components with Tailwind CSS. Ask for a product, blog, team, or dashboard card. GP ChatGPT ★ 126repo stars

Project sponsors

Companies that keep this analytics open