implement-code

Execute single-ticket implementation with plan-driven code changes, tests, and linting.

Updated May 16, 2026
One-click install
npx skills add https://github.com/cedricfarinazzo/agile-skills --skill implement-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-code
Source: https://github.com/cedricfarinazzo/agile-skills/tree/main/agile-execution/skills/implement-code
Command: npx skills add https://github.com/cedricfarinazzo/agile-skills --skill implement-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end implementation of a Jira ticket following ADRs and Specs UI, ensuring plan-driven changes are applied, validated, and ready for review.

Core Features & Use Cases

  • Executes a single-ticket implementation from plan to completion, touching data, services, APIs, frontend, and tests in the prescribed order.
  • Enforces the ADR-guided workflow: adhere to plans, flag deviations with reversible decisions, and ensure all ACs have tests.
  • Provides a repeatable, auditable process with branch creation off main, linting, and a finish gate that only passes when all checks are green.

Quick Start

Run the implement-code phase for the targeted ticket, apply changes according to the plan, and verify lint and tests green before pushing.

Frequently Asked Questions about implement-code

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

FAQPage Schema
How do I automate Jira ticket implementation from plan to code changes and tests?

Automating Jira ticket implementation requires a plan-driven workflow that executes code changes, tests, and linting in a prescribed order. This ensures all acceptance criteria are met and validated before a pull request is opened.

What is ADR-guided code implementation and how does it handle plan deviations?

ADR-guided code implementation adheres strictly to architectural decision records while applying planned changes. When deviations occur, it flags them with reversible decisions to maintain an auditable process across data, services, APIs, and frontend layers.

How do I ensure single-ticket build phase coverage for unit and integration tests?

Single-ticket build phase coverage is ensured by a finish gate that only passes when lint, unit, integration, and AC tests are green. This prevents incomplete work from proceeding to the pull request stage.

Does the implement-code workflow handle database migrations and schema changes?

Yes, the workflow handles database migrations and schema changes by ensuring they remain linear and idempotent. This maintains data integrity during the single-ticket build phase before code verification.

Can I use this approach to execute multiple tickets concurrently within an agile sprint?

No, this approach executes one ticket at a time within the agile-10-implement phase. It focuses on a single-ticket build phase to guarantee branch creation off main, plan execution, and verification before pushing.

What's the best way to validate lint and acceptance criteria before pushing a PR?

The best way to validate before pushing a PR is running a finish gate that checks linting, unit, integration, and AC test coverage. This guarantees all constraints are green and the implementation is ready for review.