skills.rest
LaiTszKin
LaiTszKinCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

enhance-existing-features

Coordinate risk-aware planning and testing for brownfield feature changes.

4|2|Updated Feb 25, 2026
Search Tags:#planning#testing#risk-management#brownfield#specs#generate-spec
One-click install
npx skills add https://github.com/LaiTszKin/apollo-toolkit --skill enhance-existing-features
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: enhance-existing-features
Source: https://github.com/LaiTszKin/apollo-toolkit/tree/main/enhance-existing-features
Command: npx skills add https://github.com/LaiTszKin/apollo-toolkit --skill enhance-existing-features

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Build and extend brownfield features in an existing codebase. Always explore the codebase first, then decide from the user's requested change whether specs (spec.md/tasks.md/checklist.md) are required before coding. When specs are required, depend on generate-spec for the shared planning, clarification, approval, and backfill workflow. Even when specs are not required, still add and run related tests for unit/property-based/user-critical integration chain/E2E coverage. Tests must not stop at happy-path validation: for business-logic changes require property-based testing unless explicitly N/A with reason, design adversarial/regression/authorization/idempotency/concurrency coverage where relevant, use mocks for external services in logic chains, and verify meaningful business outcomes rather than smoke-only success.

Core Features & Use Cases

  • Explore the existing codebase to identify entrypoints, data flow, dependencies, and user-critical logic.
  • Decide whether specs are required based on change scope; trigger generate-spec if needed to create or update docs.
  • Implement changes with minimal scope, preserving existing behavior unless required.
  • Add risk-based tests including unit, property-based, regression, integration, and E2E coverage; ensure explicit approval when planning docs are generated.
  • Backfill planning artifacts and keep artifacts traceable and aligned with completion results.

Quick Start

Map the affected codebase, decide whether specs are required, trigger the generate-spec workflow when needed, and implement with minimal, well-tested changes.

Frequently Asked Questions about enhance-existing-features

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

FAQPage Schema
How do I safely extend existing features in a brownfield codebase?▼

To safely extend brownfield features, you must first explore the codebase to map dependencies and data flow, then decide whether planning specs are required before implementing minimal, well-tested changes.

When do I need to generate specs for an existing codebase update?▼

You need to generate specs for an existing codebase update when the change scope warrants shared planning artifacts. This triggers explicit approval workflows and backfills planning docs like spec.md and tasks.md.

How do I plan risk-aware updates across existing modules?▼

Risk-aware updates across existing modules require mapping affected entrypoints and dependencies first, then enforcing comprehensive testing coverage spanning unit, integration, and E2E chains regardless of spec usage.

What testing coverage is required when modifying existing code?▼

Modifying existing code requires tests beyond happy-path validation, including unit, property-based, regression, integration, and E2E coverage. You must use mocks for external services and verify meaningful business outcomes.

Can I skip planning artifacts for minor brownfield changes?▼

You can skip planning artifacts for minor brownfield changes if spec generation is deemed unnecessary, but you must still add and run risk-based tests covering unit, property-based, integration, and E2E scenarios.

Related Skills

Explore More Software Engineering Skills→
freire19freire19

audit-1-setup

Create audit documentation and map codebase structure for pre-audit context.

Community
Intermediate
DataDogDataDog
648

run-tests

Identify changed files and run affected test suites via scripts/run-tests.

Official
Advanced
LaiTszKinLaiTszKin
4

generate-spec

Generate and synchronize spec.md, tasks.md, and checklist.md from templates.

Community
Intermediate
NooBatNooBat

plan

Generate phased, design-driven implementation plans from codebase scans.

Community
Advanced