new-feature

Orchestrate spec-driven feature implementation and testing workflows in isolated worktrees.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/alexmensch/claude-sdlc-plugins --skill new-feature-alexmensch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-feature
Source: https://github.com/alexmensch/claude-sdlc-plugins/tree/main/plugins/feature-development/skills/new-feature
Command: npx skills add https://github.com/alexmensch/claude-sdlc-plugins --skill new-feature-alexmensch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces a disciplined, spec-driven workflow for implementing new features so teams avoid ad-hoc coding, mismatched tests, and unreviewed changes that break quality or traceability.

Core Features & Use Cases

  • Technical-spec first: Generates or accepts a confirmed technical specification that drives both implementation and tests.
  • Parallel implementation and tests: Launches isolated implementer and test-writer worktrees, merges implementation before tests, and surfaces design discrepancies for user confirmation.
  • Review, coverage, and release mechanics: Runs coverage and code-review checks, applies approved fixes, updates a project roadmap and documentation, and prepares a single coherent PR.
  • Use case: A developer provides a requirements file for a new API endpoint and this skill coordinates spec generation, parallel test and implementation work, coverage gaps remediation, code review fixes, and a PR with roadmap updates.

Quick Start

Create a new branch, provide a requirements file path or a detailed chat description, confirm the summarized technical spec when prompted, and proceed with the workflow.

Frequently Asked Questions about new-feature

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

FAQPage Schema
How do I coordinate test-driven feature implementation from a technical specification?

Test-driven feature implementation is coordinated by generating a technical spec, launching parallel worktrees for code and tests, merging implementation before tests, and running coverage checks before PR creation.

What is the best way to automate code review and pull request creation for new features?

Automating code review and pull request creation involves running coverage checks, applying single-commit review fixes, updating the roadmap, and preparing a single coherent PR from an isolated worktree.

How do I manage isolated git worktrees for parallel implementation and test writing?

Isolated git worktrees for parallel implementation and test writing are managed by branching from the default branch, running separate worktrees for code and tests, then merging implementation first and tests second.

Can I use a requirements file to generate a technical spec and drive feature development?

Yes, a requirements file can be accepted or a detailed chat description provided to generate a technical spec that drives both implementation and test-writing workflows for the new feature.

How do I resolve design discrepancies between feature implementation and tests?

Design discrepancies between feature implementation and tests are resolved through user confirmation during the merge sequencing step, where implementation is merged before tests to surface mismatches.

When should I not use a spec-driven workflow for software feature delivery?

A spec-driven workflow for software feature delivery should not be used for ad-hoc coding or unreviewed changes, as it enforces technical-spec generation, coverage checks, and single-commit granularity for all modifications.