implement-ticket

Orchestrates the full ticket implementation pipeline from scope through finalize.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/ttnhan18062000/rpg-based-simulation --skill implement-ticket-ttnhan18062000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-ticket
Source: https://github.com/ttnhan18062000/rpg-based-simulation/tree/main/.claude/skills/implement-ticket
Command: npx skills add https://github.com/ttnhan18062000/rpg-based-simulation --skill implement-ticket-ttnhan18062000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating a multi-phase engineering ticket workflow (scope, investigate, plan, review, implement, test, verify, finalize) by hand is error-prone, with gates, monitoring writes, and sidecar bookkeeping easily skipped or done out of order. ## Core Features & Use Cases - Full pipeline orchestration: Executes every phase of the implement-ticket workflow in order, translating the authoritative .claude/workflows/implement-ticket.js into direct tool calls. - Tier support: Handles hotfix (skips Investigate/Plan/Review), standard (full pipeline), and epic (scope only) tiers, plus resuming existing tickets by ID. - Gate integrity enforcement: Hard-blocks on gate failures (DOC_STALENESS_BLOCKED, PARITY_INCOMPLETE, TESTS_FAILED, etc.) and forbids editing artifacts to make checks pass. - Use Case: A developer runs /implement-ticket ticket_id=TCK-20260607-MY-TICKET to resume an in-progress ticket, and the skill drives it through testing, parity ledger updates, security review, and finalization with monitoring recorded at every exit. ## Quick Start Run the implement-ticket skill with a ticket ID like TCK-20260607-MY-TICKET or a natural language request describing the change you want implemented.

Frequently Asked Questions about implement-ticket

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

FAQPage Schema
How do I run the full ticket implementation pipeline?

Invoke the skill with a ticket ID (e.g. ticket_id=TCK-20260607-MY-TICKET) to resume an existing ticket, or with a natural language request to create and implement a new one. The skill executes each phase of implement-ticket.js in order, including gates and monitoring writes.

What is the difference between hotfix, standard, and epic tiers?

Hotfix skips Investigate, Plan, Review, and Architecture-Verify but still runs Document-Update, the doc-staleness gate, Test, Parity, and Finalize. Standard runs the full pipeline, and epic performs scope only. Tier can be passed explicitly or inferred from the ticket.

Can I resume a ticket that is already in progress?

Yes. Pass the existing ticket_id and the Scope phase reloads it from tickets/inprogress/, tickets/done/, or tickets/todos/ instead of creating a new ticket, then continues the pipeline from the appropriate phase.

Why does the pipeline stop with DOC_STALENESS_BLOCKED or PARITY_INCOMPLETE?

These are hard gate failures: the doc-staleness gate fails when behavior-changing src/ or config/ changes ship without any docs/ update, and the parity cross-reference fails when a src/ file maps to a ledger subsystem with no ledger touch. Add the required docs or ledger update and re-run.

When does the security review phase run?

Security-Review fires only when the ticket's tags include security or its suggested_skills include /security-review. It is conditional on those signals, not on the tier, so it can run even for hotfix tickets.