feature-dev

Name: feature-dev
Availability: InStock
Author: Sami

Plan and coordinate multi-file feature development through a seven-phase workflow.

3|2|Updated Feb 10, 2026

Search Tags:#planning #architecture #phases #code-review #feature-development #design-first

Ready to run

npx skills add https://github.com/sami-abdul/claude-predev-setup --skill feature-dev-sami-abdul

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-dev
Source: https://github.com/sami-abdul/claude-predev-setup/tree/main/scaffold/.claude/skills/feature-dev
Command: npx skills add https://github.com/sami-abdul/claude-predev-setup --skill feature-dev-sami-abdul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when implementing a new feature that requires multiple files and careful planning.

Core Features & Use Cases

Enforces a seven-phase workflow (Discovery, Exploration, Questions, Design, Implementation, Review, Completion) and mandates Phase 2 Exploration and Phase 3 Questions.
Provides a blueprint to map required files, modules, and decisions before touching code, ensuring design-first execution.
Applies to multi-module features, architecture-driven changes, and teams seeking rigorous planning and clear handoffs.
NEVER skip Phase 2 (Exploration) — understanding the codebase prevents bad architecture
NEVER skip Phase 3 (Questions) — assumptions cause rework
NEVER write code before Phase 5 — design first
NEVER skip Phase 6 (Review) — self-review catches 80% of issues
If scope grows beyond the original request, stop and re-scope with the user

Quick Start

Initiate a feature development workflow for a new feature request and progress through all seven phases.

Frequently Asked Questions about feature-dev

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

FAQPage Schema

How do I plan multi-file feature development across multiple modules?▼

Multi-file feature development is planned using a seven-phase workflow that enforces design-first execution, mapping required files and modules before implementation. This structured process ensures architecture-driven changes are carefully staged.

What is the design-first approach for implementing a new feature?▼

A design-first approach mandates exploration and questions before any code is written. It requires mapping a blueprint of required files and decisions in earlier phases to prevent bad architecture and rework.

When do I need a structured workflow for feature development?▼

You need a structured workflow when implementing a new feature that requires multiple files and careful planning. It is applicable for multi-module features and teams seeking rigorous planning and clear handoffs.

Why does feature development require mandatory exploration and questions phases?▼

Mandatory exploration and questions phases are required because understanding the codebase prevents bad architecture, and verifying assumptions avoids rework. Skipping these phases leads to poor design decisions.

What are the limitations if I skip the review phase in a multi-module feature workflow?▼

Skipping the review phase limits your ability to catch issues early, as self-review catches 80% of problems. You also lose the structured handoffs required for completion if scope grows beyond the original request.

Can I write code before completing the design phase for a new feature?▼

No, you must never write code before Phase 5 because the workflow enforces a design-first execution. Code is only implemented after mapping required files, modules, and architectural decisions.