wa:dev-task

Develop a tracker issue into a tested feature change with PR creation.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-dev-task
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wa:dev-task
Source: https://github.com/jeremy-newhouse/eck-e2e-weather-app/tree/main/.claude/skills/dev-task
Command: npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-dev-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill turns a tracker issue into a finished, test-validated code change with a repeatable lifecycle that includes planning, gated reviews, QA verification, and tracker updates.

Core Features & Use Cases

  • Full development lifecycle execution: Creates a feature branch, gathers tracker + spec context, plans with approval, and drives implementation through tests, execution, refactor, and review gates.
  • TDD- and rigor-aware workflow: Supports mode calibration (lite/standard/strict) and optional flags to enforce or relax TDD and review stages.
  • Tracker-first delivery: Requires tracker issue context and acceptance criteria, then completes checklist items and adds development notes back to the tracker after PR creation.

Use case example: You have a GitHub-linked tracker item (WA-456) with acceptance criteria; you want an AI-assisted implementation that produces a PR-ready change while ensuring tests fail first (when TDD applies), quality gates pass, and reviewers run appropriate checks before updating the tracker.

Quick Start

Run /wa:dev-task WA-456 to develop a single tracker issue through planning, implementation, verification, and tracker update.

Frequently Asked Questions about wa:dev-task

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

FAQPage Schema
How do I develop a tracker issue into a PR-ready feature end to end?

To develop a tracker issue end to end, you run a command like /wa:dev-task WA-456. The skill then handles branch creation, planning, TDD implementation, QA verification, PR creation, and tracker updates automatically based on acceptance criteria.

What is test-driven development workflow automation for GitHub issues?

Test-driven development workflow automation drives implementation by writing failing tests first, executing them, then implementing code until tests pass. This skill enforces that cycle via dispatched specialist agents, applying TDD flags to control which quality gates run during feature development.

Do I need acceptance criteria in my tracker issue before starting automated development?

Yes, you need a tracker issue with non-empty acceptance criteria before starting automated development. The skill uses these criteria to plan the implementation, verify QA gates, and complete tracker checklist items after the PR is created.

Can I adjust the rigor of code reviews and TDD gates during feature development?

Yes, you can adjust the rigor of code reviews and TDD gates using mode calibration flags. The skill supports lite, standard, and strict modes, along with optional flags like --tdd and --rigor to enforce or relax specific review and testing stages during implementation.

Does the automated development workflow transition my tracker issue to Done?

No, the automated development workflow does not transition your tracker issue to Done. After PR creation, it completes checklist items and adds development notes back to the tracker, leaving the final issue status transition for manual review.

What task prefixes are supported for mode-calibrated development workflows?

Supported task prefixes include BE, FE, BOT, DB, UI, DOC, INFRA, and SEC. The development workflow applies mode calibration to these prefixed tasks, routing implementation through dispatched specialist agents based on the specific technical domain.