implement

Implements ticket requirements on an existing feature branch or master with validated code targets.

Updated Jul 11, 2026
One-click install
npx skills add https://github.com/danielsuguimoto/skills --skill implement-danielsuguimoto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/danielsuguimoto/skills/tree/main/skills/implement
Command: npx skills add https://github.com/danielsuguimoto/skills --skill implement-danielsuguimoto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a ticket into working code requires loading requirements, finding the right code locations, resolving ambiguities, and making minimal verified changes — this Skill automates that entire implementation workflow while enforcing strict branch and scope discipline. ## Core Features & Use Cases - Ticket-Driven Implementation: Loads the ticket via the issue tracker tool, parses acceptance criteria, checklists, and attachments into a structured todo list with inherited code targets (file/symbol/location/patch). - Branch Safety Rules: Never creates or switches to feature branches — works on the current relevant branch or falls back to master/main, stopping on uncommitted changes. - Drift Validation & Grilling: Validates plan-inherited code targets against the current codebase and grills the user only when genuine ambiguities or conflicts exist. - Use Case: A developer receives an approved ticket with an implementation checklist; the Skill loads it, builds the todo list, implements each item with lint and test verification, then presents the diff without committing. ## Quick Start Implement the ticket at https://tracker.example.com/browse/PROJ-123 on the current branch.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I implement a ticket from an issue tracker automatically?▼

Provide the ticket URL and the Skill loads it via the issue tracker tool, parses acceptance criteria and checklists into a todo list, then implements each item with lint and test runs. It presents the diff and stops without committing.

How does the implement skill choose which branch to work on?▼

It stays on the current branch if it is a feature/fix branch matching the ticket title or summary slug, otherwise it switches only to master/main. It never creates branches and never checks out other feature branches.

Does the implement skill commit or push changes?▼

No. It implements and validates changes, then presents the diff and stops. Committing, pushing, and opening pull requests are handled by separate skills like commit-and-push or ship-changes.

What happens if the ticket's planned code targets no longer match the codebase?▼

The Skill validates each inherited file/symbol/location target against current code and reports drift. If the correct replacement is ambiguous, it grills the user with one grounded question at a time before proceeding.

What happens when the issue tracker tool is unavailable?▼

The Skill returns BLOCKED with NO_MCP_ACCESS if the ticket load tool is missing. For context gathering failures, it falls back to grep, file search, and code navigation tools to resolve targets.