feature-development

Implement reviewed task slices behind test boundaries for code review.

1|Updated Mar 17, 2026

Search Tags:#release #code-review #contracts #implement #incremental #tests #task-slice

Ready to run

npx skills add https://github.com/yknothing/prodcraft --skill feature-development-yknothing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-development
Source: https://github.com/yknothing/prodcraft/tree/main/skills/04-implementation/feature-development
Command: npx skills add https://github.com/yknothing/prodcraft --skill feature-development-yknothing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Feature development is the step where a reviewed task slice becomes working software. This skill solves the problem of turning a well-scoped, test-backed plan into a small, mergeable implementation while guarding against scope creep, contract drift, and release-boundary risk.

Core Features & Use Cases

Small, boundary-respecting implementations that land a single, well-scoped change without expanding scope.
Test-backed delivery ensures behavior remains stable as the slice moves to review and integration.
Explicit contracts and handoff safeguard public interfaces and release boundaries during the implementation.

Quick Start

Select the smallest reviewed task slice, implement behind the test boundary, and prepare for code review.

Frequently Asked Questions about feature-development

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

FAQPage Schema

How do I implement a task slice without expanding the project scope?▼

To implement a task slice without scope creep, turn the reviewed plan into a small, mergeable implementation behind tests. This process ensures the slice remains a single, well-scoped change that respects explicit boundaries and preserves public API contracts.

How do I safely deliver incremental code changes across development phases?▼

Safely deliver incremental code changes by implementing behind the test boundary and preparing for code review. This method requires a known architecture and API contract, ensuring behavior remains stable as the slice moves to integration.

What is test-backed delivery for feature development?▼

Test-backed delivery is the practice of implementing a reviewed task slice behind the test boundary. It ensures software behavior remains stable as the slice moves to code review and integration, safeguarding the release boundary against contract drift.

Do I need a known API contract to implement a feature slice incrementally?▼

Yes, you need a known architecture, API contract, and acceptance criteria to implement a feature slice incrementally. These prerequisites are required to demand safe incremental delivery and safeguard public interfaces during the implementation.

When should I avoid incremental feature development for a task slice?▼

You should avoid incremental feature development when a reviewed task slice, known architecture, API contract, and acceptance criteria do not exist. Without these elements, the process cannot guarantee safe delivery or guard against contract drift and release-boundary risk.