develop

Locate a sprint ticket and orchestrate a TDD workflow with RED/GREEN sub-agents.

1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Olino3/anvil --skill develop-olino3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: develop
Source: https://github.com/Olino3/anvil/tree/main/plugins/anvil/skills/develop
Command: npx skills add https://github.com/Olino3/anvil --skill develop-olino3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implement a single sprint ticket using TDD by coordinating the dev-agent with RED/GREEN sub-agents to ensure correct behavior and fast feedback loops.

Core Features & Use Cases

  • Ticket discovery and sprint context retrieval: locate the target ticket under docs/anvil/sprints, verify the sprint context, and read the project configuration from docs/anvil/config.yml. For example, MVP-001 in a MVP sprint.
  • Isolated work environment and TDD orchestration: create an isolated git worktree on the sprint branch, dispatch the dev-agent to execute RED/GREEN/REFACTOR, and update the ticket status accordingly.
  • Post-implementation integration options: present a choice of integration strategies (squash merge, merge, create PR, keep worktree, or discard) and finalize changes while preserving sprint traceability.

Quick Start

Invoke /anvil:develop MVP-001 to implement a single sprint ticket using TDD.

Frequently Asked Questions about develop

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

FAQPage Schema
How do I automate TDD workflow for a sprint ticket?

Automating TDD workflow involves orchestrating a dev-agent to execute RED, GREEN, and REFACTOR steps for a sprint ticket. The skill locates the target ticket under docs/anvil/sprints and dispatches sub-agents to ensure correct behavior and fast feedback loops.

What is a git worktree and when do I need it for branch isolation?

A git worktree creates an isolated working environment on your sprint branch. You need it when implementing a ticket to avoid disrupting the main workspace while running tests and managing code changes independently.

How do I set up project configuration for TDD orchestration?

TDD orchestration requires reading the project configuration from docs/anvil/config.yml. You must ensure the configuration file exists and verify branch alignment before dispatching the dev-agent to execute implementation steps.

Does this TDD agent work with MVP sprint tickets?

Yes, the TDD agent works with MVP sprint tickets. It is explicitly applicable when working on MVP tickets across branches, supporting ticket discovery, sprint context retrieval, and isolated implementation workflows.

What integration options are available after TDD implementation?

After TDD implementation, available integration options include squash merge, regular merge, create PR, keep worktree, or discard changes. These strategies finalize updates while preserving sprint traceability across the project.

Why does my sprint ticket implementation fail during branch validation?

Sprint ticket implementation fails during branch validation if branch alignment is incorrect or the project configuration in docs/anvil/config.yml is missing or invalid. The skill ensures branch alignment and validates config before proceeding with orchestration.