implement

Implements scoped work from specs or tickets using design approval and test-driven development.

9|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/Yassimba/loom --skill implement-yassimba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/Yassimba/loom/tree/main/skills/implement
Command: npx skills add https://github.com/Yassimba/loom --skill implement-yassimba

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an agreed spec or ticket into working code often stalls on unclear scope, skipped design review, and missing tests. This Skill drives the implementation step end to end: it picks up the next actionable ticket when none is given, enforces a design checkpoint before coding, and routes the finished work into code review. ## Core Features & Use Cases - Automatic ticket pickup: When no spec is supplied, it claims the next ready, unassigned ticket from a Beads tracker using bv --robot-next and atomic br update --claim, avoiding double-assignment. - Design-before-code gate: Invokes the blueprint skill to present the design for approval before any non-trivial change, skipping only trivial fixes like renames. - Test-driven implementation: Applies the tdd skill at pre-agreed seams, treating a ticket's Rules & Examples map as the scenario list with one test per example. - Use Case: A developer finishes planning and says "implement the CSV export ticket." The Skill claims the ticket, shows the design for approval, writes tests per example, implements the change reusing existing code via ponytail, and hands off to code-review. ## Quick Start Use the implement skill to build the CSV export ticket from our 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 from a Beads tracker with an AI agent?

Run the implement skill with no arguments and it runs `bv --robot-next` to find the next ready ticket, verifies it is open and unassigned with `br show`, then claims it atomically with `br update --claim`. The ticket body becomes the implementation scope.

How does the implement skill handle design review before coding?

It invokes the blueprint skill to present the design and waits for approval before writing code. This gate is skipped only for trivial changes such as a rename or one-line fix.

Does the implement skill require test-driven development?

It applies the tdd skill where useful at pre-agreed seams. A ticket's Rules & Examples map serves as the scenario list, with one test written per example.

What happens if no actionable ticket exists in the tracker?

The skill reports that no actionable ticket exists and stops. It does not invent scope or proceed without a spec or ticket from the user.

What happens after implementation is complete?

The skill invokes the code-review skill on the finished work. Throughout implementation it also uses ponytail to reuse as much existing code as possible.