feature-implementation

Automate end-to-end feature implementation from GitHub issue specifications.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/dczmer/skill-issues --skill feature-implementation-dczmer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-implementation
Source: https://github.com/dczmer/skill-issues/tree/main/skills/feature-implementation
Command: npx skills add https://github.com/dczmer/skill-issues --skill feature-implementation-dczmer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating end-to-end feature implementation from GitHub issue specifications using test-driven development, subagent delegation, and auditable checkpoints to reduce manual toil and errors.

Core Features & Use Cases

  • End-to-end workflow: derives plan from issues labeled feature-plan and orchestrates planning, testing, stubbing, implementation, and verification with multiple subagents.
  • Checkpoints and rollback: supports commit tags and checkpoints to safely revert progress if a step fails.
  • Parallel execution where safe: runs independent tasks in parallel (e.g., code-fixer and test suite) to speed delivery while preserving sequential requirements for tests and stubs.
  • Interactive decision points: prompts the user for critical choices (branch naming, plan approval, retry/fallback options) to maintain control.
  • GitHub and CLI integration: relies on gh and git tooling to manage branches, PRs, and issue updates.

Quick Start

Invoke it with /feature-implementation [optional feature name] to begin implementing a feature from a GitHub issue specification.

Frequently Asked Questions about feature-implementation

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

FAQPage Schema
How do I automate feature implementation from a GitHub issue using TDD?

You can automate feature implementation by invoking a multi-subagent workflow that reads a labeled GitHub issue, creates a branch, writes tests, generates stubs, implements code, and verifies deliverables. This TDD-driven process ensures safe and auditable progress.

What is the best way to orchestrate parallel subagents for test-driven development?

Orchestrating parallel subagents for TDD allows independent tasks like code generation and test execution to run simultaneously. The workflow preserves sequential requirements for writing tests and stubs, while using checkpoints and rollback strategies to maintain safety.

Can I use GitHub CLI tooling to manage branches and PRs during automated feature delivery?

Yes, automated feature delivery integrates directly with GitHub CLI tooling. It uses git operations and the gh CLI to manage branch creation, pull requests, and issue updates automatically as the TDD workflow progresses through implementation and verification.

How do checkpoints and rollback strategies work during automated code generation?

Checkpoints and rollback strategies use commit tags to safely revert progress if a workflow step fails. This ensures auditable progress during automated code generation by allowing the system to fall back to a previous state without manual intervention.

Do I need to manually approve the feature plan before subagent orchestration begins?

No, but the workflow includes interactive decision points that prompt you for critical choices. You will be asked to approve the feature plan, confirm branch naming, and select retry or fallback options to maintain control over the subagent orchestration.

What limitations exist when using subagent delegation for end-to-end feature implementation?

Subagent delegation for feature implementation requires strict sequential ordering for tests and stubs to prevent conflicts. While independent tasks run in parallel, complex feature plans may require frequent manual intervention at interactive decision points to ensure correct deliverables.