implement-v2

Orchestrate a 5-phase feature workflow from Jira ticket to merged PR.

1|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/jonball4/claude-dev-skills --skill implement-v2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-v2
Source: https://github.com/jonball4/claude-dev-skills/tree/main/skills/implement-v2
Command: npx skills add https://github.com/jonball4/claude-dev-skills --skill implement-v2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the entire process of implementing a new feature, from initial discovery and planning to code execution, review, and pull request creation, reducing manual coordination and ensuring consistency.

Core Features & Use Cases

  • End-to-End Workflow: Manages feature implementation across five distinct phases: Discovery, Planning, Execution, Review, and Handoff.
  • Multi-Agent Coordination: Utilizes specialized agents for each phase to handle complex tasks like context gathering, architectural design, parallel TDD implementation, and automated code review.
  • Use Case: When starting a new feature like "Implement user authentication flow" tied to a Jira ticket (e.g., PX-1234), this Skill will gather requirements, design the architecture, implement the code using TDD in parallel for different components, run integration tests, and finally create a well-documented GitHub Pull Request.

Quick Start

Use the implement-v2 skill to start implementing the feature for ticket PX-1234.

Frequently Asked Questions about implement-v2

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

FAQPage Schema
How do I automate feature implementation from a Jira ticket to a merged pull request?

Automated feature implementation orchestrates a five-phase workflow—discovery, planning, parallel execution, review, and handoff—to move a Jira ticket through test-driven development to a merged pull request.

What is multi-agent test-driven development and how does it work for feature implementation?

Multi-agent test-driven development assigns specialized agents to gather context, design architecture, and implement code components in parallel, ensuring isolated test execution before integration testing and automated pull request creation.

Do I need Git with GPG signing and Claude Code to orchestrate feature implementation?

Yes, orchestrated feature implementation requires Claude Code for multi-agent execution, Git with GPG signing for commits, a configured test framework for TDD, and Superpowers to run automated code reviews.

How to manage parallel component implementation using test-driven development?

Parallel component implementation using test-driven development is managed by orchestrating specialized agents that independently write tests and execute code for different architectural components before running integration tests.

What's the best way to automate code review and PR creation for new features?

Automating code review and pull request creation is best handled by an orchestrated workflow that uses multi-agent execution to implement features and generates a well-documented GitHub pull request after verifying integration tests.

When should I not use an orchestrated multi-agent workflow for feature implementation?

You should avoid an orchestrated multi-agent workflow if your project lacks a test framework for test-driven development, requires manual code review oversight, or does not use Git with GPG signing for automated commits.