new-feature

Plan new user-facing features via impact analysis and test planning in Rails event-sourced applications.

504|85|Updated Jul 8, 2019

Search Tags:#impact analysis #feature planning #test design #rails #event sourcing #app architecture

Ready to run

npx skills add https://github.com/RailsEventStore/ecommerce --skill new-feature-railseventstore

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: new-feature
Source: https://github.com/RailsEventStore/ecommerce/tree/main/.claude/skills/new-feature
Command: npx skills add https://github.com/RailsEventStore/ecommerce --skill new-feature-railseventstore

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps teams thoroughly plan new user-facing features by analyzing all necessary changes upfront to prevent missed dependencies.

Core Features & Use Cases

Impact Analysis: Identifies all affected read models, views, controllers, and domain components before starting implementation.
Comprehensive Planning: Guides writing integration tests that cover all UI surfaces and data changes.
Use Case: When adding a new customer attribute, this Skill ensures you analyze where the data appears, update relevant handlers, and verify across the app before coding.

Quick Start

Ask the AI to plan the steps needed to implement a new feature that updates customer data in an existing order management system.

Frequently Asked Questions about new-feature

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I plan feature development across all layers in a Rails event-sourced app?▼

Feature development across all layers requires impact analysis to identify affected read models, views, controllers, and domain components. You can facilitate end-to-end planning for new user-facing features by analyzing necessary changes upfront to prevent missed dependencies.

What's the best way to do impact analysis for new features before implementation?▼

The best way to do impact analysis is to identify all affected read models, views, controllers, and domain components before starting implementation. This comprehensive pre-implementation review ensures thorough change management and prevents missed dependencies in complex applications.

How does test design work for coordinating changes across domain and read-model layers?▼

Test design for coordinating changes guides writing integration tests that cover all UI surfaces and data changes across domain and read-model layers. This ensures you verify every affected component across the app before coding begins.

Can I use this approach to add a new customer attribute to an existing order management system?▼

Yes, you can use this approach to add a new customer attribute to an order management system. It ensures you analyze where the data appears, update relevant handlers, and verify across the app before coding to prevent missed dependencies.

Do I need an event sourcing architecture to coordinate feature planning across controllers and domain layers?▼

Yes, this feature planning approach specifically supports coordination in complex Rails-based event-sourced applications. It delegates tasks across domain, read-model, and controller layers inherent to event sourcing architectures.