# Feature Dev

> Develop a non-trivial feature through research, consultation, planning, delegated implementation, testing, and independent review

- Skill: `iabuelruzz/feature-dev` (Agent Skill)
- Install (CLI): `npx skillmds@latest add iabuelruzz/feature-dev`
- Raw SKILL.md: https://api.skillmd.com/api/skills/iabuelruzz/feature-dev/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Research & Search
- Author: IAbuElRuzz (https://skillmd.com/u/iabuelruzz)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/iabuelruzz/feature-dev

---


# Feature Development Workflow

The argument supplied by the user is the feature request:

$ARGUMENTS

## Stage 1: Investigate

Do not modify code.

Launch appropriate research subagents to investigate:

- Existing architecture and affected code
- Similar existing features
- Required tests
- Security and compatibility implications

Run investigations in parallel only when they are independent.

## Stage 2: Reconcile

Review all findings and produce a single implementation proposal containing:

- Scope
- Assumptions
- File-level changes
- Interfaces and data structures
- Error handling
- Tests
- Validation commands
- Risks

Resolve contradictory recommendations yourself.

## Stage 3: Plan

Create work packages that have non-overlapping file ownership.

Use Sonnet implementers for normal coding work.

Use Opus implementers only when the task requires unusually difficult
reasoning, security-sensitive implementation, or broad architectural changes.

## Stage 4: Implement

Delegate independent work packages in parallel.

Each implementation assignment must include:

- Exact objective
- File ownership
- Constraints
- Required tests
- Validation commands
- Expected return format

Do not allow overlapping edits.

## Stage 5: Integrate and validate

After the implementation work returns:

1. Inspect all changes.
2. Resolve integration problems.
3. Run the complete relevant test suite.
4. Run type checking, linting, formatting, and build checks.
5. Run an Opus reviewer against the complete diff.
6. Correct all blocker and high-severity findings.
7. Re-run validation.

## Stage 6: Report

Provide:

- Implementation summary
- Design decisions
- Files changed
- Tests and commands actually run
- Remaining limitations