feature-dev

Coordinate end-to-end feature development across discovery, design, implementation, and review.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/japurcell/skills --skill feature-dev-japurcell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-dev
Source: https://github.com/japurcell/skills/tree/main/skills/feature-dev
Command: npx skills add https://github.com/japurcell/skills --skill feature-dev-japurcell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams coordinate end-to-end feature development across discovery, design, implementation, and review, ensuring clear ownership and consistent handoffs.

Core Features & Use Cases

  • Calibrate the workflow by selecting Light, Standard, or Deep based on scope, ambiguity, and risk.
  • Guide teams to ask high-leverage questions, read relevant files flagged by agents, and leave reusable handoff artifacts.
  • Provide a concrete handoff plan and implementation map to keep multi-file changes organized and auditable.

Quick Start

Define the feature scope, choose a track, and start Phase 1 discovery to create a work plan and change-timeline artifact.

Frequently Asked Questions about feature-dev

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

FAQPage Schema
How do I coordinate end-to-end feature development across multiple files and teams?

Feature development coordination is managed by calibrating a Light, Standard, or Deep workflow track based on scope and risk. This enforces a formal implementation process using TDD loops, code-simplifier refactoring, and an independent code reviewer.

What is the best way to structure handoffs for medium-to-large features requiring architecture decisions?

Structured handoffs for large features are achieved by generating reusable handoff artifacts, a concrete handoff plan, and an implementation map. This keeps multi-file changes organized, auditable, and ensures consistent stakeholder communication.

How do I apply TDD and code review discipline to a complex multi-file feature workflow?

TDD and code review discipline are applied by breaking work into implementation slices within the workflow track. Each slice enforces the TDD loop, code-simplifier refactor, and independent code-reviewer stages to ensure consistent quality before handoff.

Can I use this feature development workflow for small single-file changes?

This workflow is designed for medium-to-large features that require cross-file coordination, architecture decisions, and stakeholder questions. Small single-file changes would likely find the Light track overly formal for the scope.

When do I need a formal implementation and review process for feature delivery?

A formal implementation and review process is needed when features involve high ambiguity, risk, or cross-file coordination. The workflow calibrates the process depth by selecting Light, Standard, or Deep tracks based on these project factors.

How do I start phase 1 discovery to create a work plan and change-timeline artifact?

Phase 1 discovery starts by defining the feature scope and selecting a workflow track. Teams then ask high-leverage questions, read relevant files flagged by agents, and leave reusable handoff artifacts to produce the work plan.