enhancement

Adds small features to existing production applications using established design and code patterns.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/scoots31/engineering-playbook --skill enhancement-scoots31
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: enhancement
Source: https://github.com/scoots31/engineering-playbook/tree/main/skills/enhancement
Command: npx skills add https://github.com/scoots31/engineering-playbook --skill enhancement-scoots31

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Small improvements to a live product often get over-engineered into full project phases or built without regard for existing patterns, creating duplicate solutions and broken conventions. This Skill provides a disciplined, lightweight workflow for shipping contained enhancements that fit naturally into what already exists. ## Core Features & Use Cases - Context-First Building: Reads existing backlog, design files, process flows, and code before writing anything, ensuring the change extends current patterns rather than creating parallel solutions. - Scope Discipline: Forces a one-sentence scope statement with explicit boundaries, verifiable done criteria, and a clear list of what will not change. - Lite QA and Isolated Deploys: Runs targeted verification on affected screens and deploys the enhancement alone on its own branch, never bundled with other work. - Use Case: A solo builder wants to add a status filter to an existing orders screen. The Skill guides them to review the current design and data sources, scope the change to one sentence, build on an enhancement/ branch matching existing code patterns, verify in the browser, and deploy independently. ## Quick Start Ask the assistant to add a small improvement to your existing app, for example: add a date-range filter to the reports screen using the current design and data patterns.

Frequently Asked Questions about enhancement

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

FAQPage Schema
How do I add a small feature to an existing production app?

Read the existing backlog, design files, and relevant code first, then state the change in one sentence with explicit scope boundaries. Build on a dedicated enhancement branch matching current patterns, run targeted QA on affected screens, and deploy the change alone.

What is the difference between an enhancement and a new feature phase?

An enhancement is a contained addition like a new field, filter, or configuration option that fits existing screens and process flows. If the change needs new design screens, a new process flow, or more than a few hours of build time, it should go through full design and planning instead.

When should I not use a lightweight enhancement workflow?

Avoid it when the change requires new design screens, alters a process flow, or exceeds a few hours of work. Those cases need the full design-review and planning flow to stay traceable to the product's process map.

Why should enhancements be deployed separately from bug fixes?

Bundling changes makes it impossible to isolate the cause when something breaks in production. Deploying each enhancement on its own branch with its own commit keeps rollbacks simple and verification unambiguous.

How much QA does a small enhancement need?

A targeted check is enough: confirm the change does what was described, renders correctly, and did not break adjacent screens. Verify in the actual environment with a manual browser pass scoped to the screens the change touches.