What problem does it solve? After implementing work on a branch, the original issue ticket often no longer reflects what the code actually does. This Skill produces or revises a ticket (GitHub issue, Jira issue, or local artifact) so its acceptance criteria accurately describe the branch's implementation, keeping the record of work consistent. ## Core Features & Use Cases - Two operating branches: Generates a full ticket from the implementation when no prior ticket exists, or aligns only the acceptance criteria of an existing ticket while reproducing its problem, context, and proposed solution verbatim. - Ratified-delta and spike modes: Applies a caller-supplied, user-approved delta exactly as given, or reconciles spike investigations against their questions instead of acceptance criteria. - Dual write targets: Writes the ticket of record on its remote platform and saves a local ticket artifact with universal frontmatter, with --write-target=remote|local control. - Use Case: After finishing a bug-fix branch, run the Skill to diff against the default branch, update the linked GitHub issue's acceptance criteria to match what was actually fixed, and save a timestamped local ticket artifact. ## Quick Start Ask the agent to align the current branch's ticket with its implementation, optionally passing --write-target=local to update only the local artifact.
