coder:add-feature

Automate adding features to existing codebases with the eri-coder workflow.

1|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/CodeAlexx/Eri-Rpg --skill coder-add-feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coder:add-feature
Source: https://github.com/CodeAlexx/Eri-Rpg/tree/main/erirpg/skills/coder-add-feature
Command: npx skills add https://github.com/CodeAlexx/Eri-Rpg --skill coder-add-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Add a feature to an EXISTING codebase (brownfield workflow) to extend functionality without starting from scratch, ensuring compatibility with current code and conventions.

Core Features & Use Cases

  • Guided brownfield feature addition across a project with planning, spec, and verification.
  • Automates environment checks, codebase mapping, SPEC/PLAN/CONTEXT/RESEARCH generation, and execution with verification.
  • Use case: integrate a new capability into an existing project while preserving architecture and tests.

Quick Start

Run the add-feature workflow to introduce a new capability to an existing project.

Frequently Asked Questions about coder:add-feature

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

FAQPage Schema
What is the best way to add features to an existing codebase without breaking current architecture?

Adding features to an existing codebase requires a brownfield workflow that validates the environment, maps the project structure, and generates a spec and plan before execution to ensure compatibility with current architecture.

How do I plan and execute a brownfield feature addition step by step?

You can plan a brownfield feature addition by running an automated workflow that performs environment checks, generates spec and context documentation, executes the plan, and verifies the results against existing tests.

Can I integrate a new capability into a project while preserving existing conventions and tests?

Yes, integrating a new capability while preserving conventions is possible by using an automated brownfield workflow that enforces adherence to current architecture and validates execution outcomes against existing tests.

Does adding a new feature to a brownfield project require manual codebase mapping?

Adding a feature to a brownfield project does not require manual codebase mapping because the automated workflow handles environment validation, codebase mapping, and context generation before planning execution.

What are the limitations of automating feature execution in an existing codebase?

Automating feature execution in an existing codebase is limited by its strict enforcement of existing conventions and architecture, meaning any execution failure requires validating environment checks and generated plans before proceeding.