feature

Coordinate feature development from spec through test-first implementation and review.

8|1|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/duthaho/skillhub --skill feature-duthaho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature
Source: https://github.com/duthaho/skillhub/tree/main/.claude/skills/feature
Command: npx skills add https://github.com/duthaho/skillhub --skill feature-duthaho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents vague, scope-creeping feature work by turning a request into an agreed spec, an executable plan, and a test-first build process with checkpoints and evidence.

Core Features & Use Cases

  • Effort-scaled workflow: Chooses the lightest valid process for trivial, small, or standard changes so simple fixes do not get buried under heavyweight ceremony.
  • Spec and plan discipline: Captures decisions, assumptions, task order, file targets, and verification steps so work can resume cleanly across sessions.
  • Test-first execution: Drives implementation through failing tests, minimal code changes, checkpoint commits, and a final evidence-based finish gate.
  • Use case: A developer asks for a new feature, a bug fix, or a resumed multi-file change and needs a structured process that keeps scope, quality, and progress visible.

Quick Start

Use the feature skill to plan and execute this change with the smallest valid workflow.

Frequently Asked Questions about feature

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

FAQPage Schema
How do I prevent scope creep when implementing a new feature?

Prevent scope creep by turning the feature request into an agreed spec with executable plans and acceptance criteria. This enforces checkpoint commits and evidence-backed completion before shipping, keeping work visible and contained.

What is test-first development with checkpoint commits?

Test-first development drives implementation through failing tests and minimal code changes. Checkpoint commits save session-safe state at task milestones, ensuring work can resume cleanly across interrupted development sessions.

How do I resume a multi-file coding change across sessions?

Resume multi-file changes by capturing decisions, assumptions, task order, and file targets in a spec. This session-safe state allows you to pick up exactly where you left off with explicit scope control intact.

Do I need heavyweight spec planning for a trivial bug fix?

No, spec planning applies effort-scaled workflows to choose the lightest valid process. Trivial fixes avoid heavyweight ceremony, while standard changes still get task-level verification and evidence-backed finish gates.

When should I not use a feature workflow for coding tasks?

Avoid feature workflows for trivial edits that require no explicit scope control or session-safe state. If a change needs no approved acceptance criteria or task-level verification, the heavyweight process adds unnecessary overhead.

What's the best way to ship features with specs and checkpoints?

The best way to ship features is coordinating from request sizing through spec, plan, test-first implementation, and checkpoint commits. This requires approved acceptance criteria and evidence-backed completion before final review.