---
status: resolved
parent: "[[038-implement-skill-map]]"
claimed-by: "019fbb66-80d0-7a01-8ac9-01255adfc7b2"
claimed-at: "2026-08-01T07:12:41-04:00"
blocked-by:
  - "[[039-implement-skill-old-workflow-research]]"
  - "[[041-implement-skill-wayfinder-contract-research]]"
  - "[[075-implement-skill-matt-implement-research]]"
  - "[[079-implement-skill-matt-wayfinder-research]]"
tags:
  - ticket/grill
---

# Implement skill ticket scope grill

## Question

Should the migrated `implement` skill execute only one explicit actionable Wayfinder implementation task ticket, or should it also accept maps, specs, multiple tickets, or legacy task files?

## Resolution

The `implement` skill should not prescribe what work the agent is allowed to implement.
It defines the execution protocol, not the admissible work-source taxonomy.
The artifact produced by implementation is the working code.

When the selected work has a Wayfinder task artifact, `implement` follows the Wayfinder protocol for claim, blocker awareness, result recording, resolution, and Frontier repair.
When the selected work does not have a Wayfinder artifact, `implement` proceeds with the normal implementation, review, commit, and handoff protocol without creating or requiring a tracking artifact.
The skill should not police whether the work should have been a Wayfinder ticket.
