Skip to content

feat: follow a companion skill when creating a ticket - #455

Merged
danielhanold merged 3 commits into
mainfrom
feat/follow-the-team-s-own-ticket-skill-for-project-specific-tick
Nov 11, 2026
Merged

danielhanold merged 3 commits into
mainfrom
feat/follow-the-team-s-own-ticket-skill-for-project-specific-tick

Conversation

@danielhanold

@danielhanold danielhanold commented Nov 11, 2026 •

Copy link
Copy Markdown
Owner

↩ Change 0591 — Follow a companion skill when creating a ticket

Summary

When docket-link-ticket creates a ticket from a change, it now finds the person's companion skill (their team's own ticket skill) and follows it for project-specific details: title format, ticket type when the skill states one, sprint and custom fields, labels, after-creation actions, and call pacing. Docket still owns the readiness check, the description body, the approved draft (which now shows everything the companion skill will do), and recording the link only after the connector confirms.

  • New optional key tickets.companion_skill, settable at any config layer with normal precedence (unlike the repository-only tickets.* siblings), documented in docs/reference/config-keys.md and .docket.example.yml.
  • create.md gains a step 4: read the key, warn in one line and fall back to description matching when the named skill is missing, ask when several match, behave as before when none match.
  • The rule that a created ticket's description is never rewritten is removed, along with its contract line; a new change_0591_companion_skill contract pins the new text and forbids the old wording.

Review

Reviewed by docket-review-standard over the whole branch: no findings.

Finding Disposition
(none) -

Testing

Full suite green at the PR head. New TestTicketsCompanionSkillAnyLayer plus the alignment contract, both mutation-tested. A live check against a real ticket system from another repository is listed as an Important human action in the results.

@danielhanold
danielhanold merged commit b3bc2ae into main Nov 11, 2026
1 check passed
@danielhanold
danielhanold deleted the feat/follow-the-team-s-own-ticket-skill-for-project-specific-tick branch November 11, 2026 02:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant