ood-add-feature

Integrate a new feature draft into existing OOD artifacts using the 6-step workflow.

Updated Mar 22, 2026

Search Tags:#design #architecture #traceability #design-patterns #grasp #ood #use-case-driven

Ready to run

npx skills add https://github.com/GoGradually/usecase-driven-design-skills --skill ood-add-feature

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ood-add-feature
Source: https://github.com/GoGradually/usecase-driven-design-skills/tree/main/usecase-driven-design/skills/ood-add-feature
Command: npx skills add https://github.com/GoGradually/usecase-driven-design-skills --skill ood-add-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Existing OOD projects often need to add new features without breaking the established architecture, lineages, and design decisions. This skill enables safe extension by analyzing both the current OOD outputs and the new OOA inputs, ensuring reuse and consistency.

Core Features & Use Cases

Analyze existing OOD artifacts and incoming OOA drafts to determine integration points.
Progress the 6-step OOD workflow (Architecture, Use Case Realization, GRASP, Patterns, DCD, and cross-cutting concerns) with traceability.
Ensure seamless reuse of existing classes and packages while introducing minimal, coherent changes.

Quick Start

Review existing OOD outputs and OOA drafts, then follow the 6-step workflow to draft and integrate the new feature.

Frequently Asked Questions about ood-add-feature

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

FAQPage Schema

How do I add a new feature to an existing object oriented design without breaking the architecture?▼

To add a new feature to an existing object oriented design, analyze current OOD artifacts and incoming OOA drafts to identify integration points. This ensures reuse of established classes and packages while introducing minimal, coherent architectural changes.

What is the use-case-driven workflow for extending object oriented design?▼

The use-case-driven workflow for extending object oriented design progresses through six steps: Architecture, Use Case Realization, GRASP, Patterns, DCD, and cross-cutting concerns. Each step maintains traceability between existing design artifacts and the new feature draft.

Do I need existing OOA drafts and OOD artifacts to integrate a new feature draft?▼

Yes, you need existing OOA drafts and OOD artifacts to integrate a new feature draft. The process requires analyzing both current design outputs and new analysis inputs to safely extend the architecture and maintain domain object consistency.

How does GRASP apply when reusing current architecture for a new feature?▼

Applying GRASP when reusing current architecture involves assigning responsibilities to existing or new domain objects during the realization step. This guides the integration by ensuring the new feature draft adheres to established design patterns and principles.

What's the best way to maintain traceability when adding a new OOD feature draft?▼

The best way to maintain traceability when adding a new OOD feature draft is following the structured 6-step OOD workflow. This provides structured outputs for design drafts and maps new realization decisions back to existing architecture and OOA inputs.