add-feature

!../principles/SKILL_BODY.md

!../tool-gitnexus/SKILL_BODY.md

---

New Feature / Module Workflow

Core Principle

When adding new features, integrate into the existing architecture like a native, not an outsider who starts from scratch. New code should be fully consistent with existing code in style, structure, and interaction patterns.

---

Complete Execution Workflow

Progress tracking: At the start of each step, output an updated progress block. For Lightweight tasks show only Steps 3–4; for Medium/Large tasks show all steps.

Add Feature Progress
✓ Step 1: Architecture Research     — <one-line finding>
→ Step 2: Solution Design + Confirm — in progress
○ Step 2.5: TDD Contract Tests      — (Large/Medium only)
○ Step 3: Implement
○ Step 4: Architecture Audit

Replace ○ with → for the current step, and ✓ once complete.

---

Step 1: Understand the Existing Architecture

Before starting, you must be able to answer the following questions:

Architecture awareness:

• What architectural pattern does the project use? (MVC / MVVM / Clean Architecture / Component-based / Microservices…)
• How are similar existing features implemented? (Find the best reference)
• What is the logic behind the project's directory structure? (By layer, by feature, by domain?)

Positioning analysis:

• Which layer does the new feature belong to? Where is its entry point?
• Which existing modules does the new feature need to depend on?
• Are there already extendable abstraction points (e.g., existing strategy interfaces, factory registries, event buses), or do new ones need to be created?

Reference module:

• Find the most similar existing module to the new feature as an implementation reference
• Observe its file structure, naming conventions, dependency injection approach, error handling patterns, and test organization
• The new module should follow the same patterns as closely as possible

🔗 When GitNexus is available, use query / context MCP tools for architecture exploration.