incremental-implementation

Guides incremental code implementation following existing conventions, patterns, and quality standards.

Updated Dec 29, 2025
One-click install
npx skills add https://github.com/snoodleboot-io/discrecontinual_equations --skill incremental-implementation-snoodleboot-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: incremental-implementation
Source: https://github.com/snoodleboot-io/discrecontinual_equations/tree/main/.claude/skills/incremental-implementation
Command: npx skills add https://github.com/snoodleboot-io/discrecontinual_equations --skill incremental-implementation-snoodleboot-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? New code often drifts from established codebase conventions, introducing inconsistent patterns, missing context, and review friction. This Skill enforces a disciplined, incremental implementation workflow so every change matches existing architecture and remains easy to review. ## Core Features & Use Cases - Convention Matching: Reads existing files in the same architectural layer and replicates their patterns for naming, error handling, dependency injection, and testing. - Intent-Focused Commenting: Adds inline comments that explain why code exists (workarounds, magic numbers, invariants) rather than restating what it does. - Structured TODO Tracking: Flags judgment calls with categorized TODO comments (Security, Performance, Validation, Incomplete) including owner and date. - Use Case: When adding a new OrderService to a Python FastAPI project, the Skill reads existing services first, then writes the new service with matching constructor injection, async patterns, docstrings, and categorized TODOs—one file at a time. ## Quick Start Implement the new feature incrementally, matching the existing code patterns in this repository and adding TODO comments for any judgment calls.

Frequently Asked Questions about incremental-implementation

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

FAQPage Schema
How do I implement new code that matches existing codebase patterns?▼

Read 2-3 existing files in the same architectural layer before writing anything. Identify their patterns for naming, error handling, and dependency injection, then copy those patterns exactly rather than introducing new approaches.

When should I add inline comments to my code?▼

Add comments to explain why code exists: complex algorithms, magic numbers, workarounds, invariants, and performance optimizations. Never comment what the code already says clearly, such as restating that a loop iterates over items.

What is the correct format for TODO comments in code?▼

Use the format 'TODO: [Category] Description (Owner, Date)' with categories like Security, Performance, Validation, Incomplete, Bug, Refactor, Testing, or Documentation. Vague TODOs like 'fix this' provide no actionable context for future maintainers.

Why should I implement one file at a time instead of in parallel?▼

Completing one file fully before moving on reduces context switching, makes reviews easier, and minimizes merge conflicts. Jumping between half-finished files creates review friction and makes rollback harder when issues appear.

Which programming languages does this implementation workflow support?▼

The workflow supports Python, TypeScript, JavaScript, Go, Rust, Java, C#, PHP, and Ruby. The principles of convention matching, intent commenting, and incremental file completion apply uniformly across all listed languages.