implement

Automate ticket implementation with setup, validation, and unit tests.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/nand1234/Agentic-workflow-builder --skill implement-nand1234
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/nand1234/Agentic-workflow-builder/tree/main/ai-dev-worflow/.claude/skills/implement
Command: npx skills add https://github.com/nand1234/Agentic-workflow-builder --skill implement-nand1234

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end implementation of a ticket in its worktree, including setup, validation, and test coverage.

Core Features & Use Cases

  • Orchestrates ticket worktree setup, dependency checks, and status updates across the ticket lifecycle.
  • Enforces design-context checks for frontend/backend scope and validates RTM mappings before coding.
  • Writes and runs 100% unit tests, commits, and pushes changes to the ticket branch.

Quick Start

Follow the ticket flow to implement the feature in its worktree and verify all tests pass.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I automate ticket implementation in a git worktree with test coverage?

Ticket implementation in a git worktree is automated end-to-end by orchestrating worktree setup, validating design context, running 100% unit tests, and pushing changes to the ticket branch. It enforces workspace-scoped rules and prevents modifications to main or master.

What is ticket-driven workflow automation for fullstack features?

Ticket-driven workflow automation handles the complete lifecycle of a feature spanning frontend and backend. It performs dependency checks, validates RTM mappings, writes unit tests, and commits code to isolated worktrees before pushing to the ticket branch.

How do I set up a git worktree for a new feature ticket?

Setting up a git worktree for a feature ticket involves creating an isolated branch, validating design context and dependencies, and enforcing workspace-scoped rules. The automation handles this setup phase before any coding begins.

Can I use automated ticket implementation for both frontend and backend scopes?

Automated ticket implementation supports fullstack scopes by enforcing design-context checks for both frontend and backend. It validates RTM mappings and dependencies before coding to ensure the feature meets requirements across the stack.

Does the automated worktree workflow prevent direct commits to main or master?

The automated worktree workflow prevents modifications to main or master by enforcing workspace-scoped rules. All changes are committed and pushed exclusively to the isolated ticket branch after passing 100% unit test coverage.

Why do I need dependency checks and RTM validation before coding in a worktree?

Dependency checks and RTM validation are needed before coding to ensure design-context accuracy and traceability. The automation validates these prerequisites within the worktree to prevent scope errors and maintain ticket documentation throughout the lifecycle.