implement

Implements work items from specs or tickets with dependency tracking and test-driven workflow.

6|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/northguild/gmt --skill implement-northguild
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/northguild/gmt/tree/main/.agents/skills/implement
Command: npx skills add https://github.com/northguild/gmt --skill implement-northguild

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written spec or ticket into finished, verified code requires coordinating dependency checks, test-driven development, typechecking, and status tracking — steps that are easy to skip or do out of order. This Skill enforces that disciplined implementation workflow so work lands correctly and downstream stories unblock properly. ## Core Features & Use Cases - Dependency-aware start: Reads the story's Blocked by cell in the tracker before starting, distinguishing true blockers from shared primitives that must be built inline. - Structured implementation loop: Applies test-driven development at pre-agreed seams, runs typechecking and single test files regularly, and executes the full test suite once at the end. - Tracker lifecycle management: Flips the story status to Done, runs dependency sync to clear other rows' blockers, and updates the provided-capabilities section when outputs change. - Use Case: A developer picks up an epic story from the tracker, confirms its dependencies are cleared, implements it with TDD, reviews the result, and marks it Done so dependent stories become startable. ## Quick Start Ask the assistant to implement the work described in a specific spec or ticket ID from the tracker.

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 or spec with an AI coding assistant?▼

Point the assistant at the spec or ticket and let it follow the implementation workflow: check dependencies first, build with test-driven development, run typechecking and tests, then review the result. The work is left unstaged in the working tree for your inspection.

How does the skill handle blocked stories in a dependency tracker?▼

It reads the story's Blocked by cell before starting. A non-empty cell means the story cannot start and it says so; a parenthesised entry is a shared primitive the story must build itself, which gets folded into the work.

Does the implement skill commit or push changes to git?▼

No. All changes are left unstaged in the working tree. It never runs git add, commit, push, branching, or opens a pull request unless the user explicitly asks in plain words.

What happens after the implementation work is finished?▼

The work goes through a code review step, the story status flips to Done in the tracker, and a dependency sync runs to clear the story from other rows' Blocked by cells. A commit message can be drafted on request.

When should I not use a spec-driven implementation workflow?▼

Avoid it for quick exploratory prototypes or one-off scripts with no tracker entry, where dependency checks and status syncing add overhead without value. It is designed for tracked stories in an epic-based workflow.