arib-dev-feature

Standardize feature development with research, branching, snapshots, and TDD.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/AribSudia/claude-code-methodology --skill arib-dev-feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arib-dev-feature
Source: https://github.com/AribSudia/claude-code-methodology/tree/main/.claude/skills/arib-dev-feature
Command: npx skills add https://github.com/AribSudia/claude-code-methodology --skill arib-dev-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates common development pitfalls like scope creep, untested code, and lost work by enforcing a rigorous, 7-step protocol for feature implementation.

Core Features & Use Cases

  • Safety-First Workflow: Mandates branch creation and safety snapshots before any code is written, ensuring an easy rollback path.
  • TDD Enforcement: Requires a Red-Green-Refactor cycle to ensure code quality and test coverage.
  • Structured Planning: Facilitates user alignment through a mandatory implementation plan and approval gate before execution.

Quick Start

Initiate the development of a new feature by running the skill with the name of the feature you intend to build.

Frequently Asked Questions about arib-dev-feature

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

FAQPage Schema
How do I standardize feature development with TDD and git?

Standardize feature development through a 7-step protocol enforcing branch creation, safety snapshots, and a TDD Red-Green-Refactor cycle to guarantee code quality and test coverage.

What's the best way to prevent scope creep during feature implementation?

Prevent scope creep through a structured implementation plan and mandatory approval gate before execution, ensuring strict project alignment before any code is written.

How does a safety snapshot workflow protect against lost work in git?

A safety snapshot workflow protects against lost work by mandating branch creation and checkpoints before writing code, ensuring an easy rollback path if feature implementation fails.

Do I need git to use a TDD-driven feature development workflow?

Yes, you need git for version control within this TDD-driven feature development workflow, as it mandates branching and safety snapshots to maintain an easy rollback path.

When should I use a structured TDD lifecycle for new functionality?

Use a structured TDD lifecycle for all new functionality requests to eliminate untested code, enforce best practices, and ensure adherence to project-specific constraints and technical documentation.