Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →shafthq/work-item
Use when opening or rewriting a work item on any git-based SCM. Source-control agnostic; GitHub, GitLab, and Azure Boards are adapters only.
Passed 22 of 23 test cases with the skill, and 6 of 23 without it.
and 21 more in the full report
16 fixed6 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
We want to adopt Spec Kit for our issue tracking in this repository. Please generate the .specify directory structure and vendor the Spec Kit runner scripts into our codebase.
| Checked | Without skill | With skill |
|---|---|---|
| The output declines to create a .specify directory. | Missed | Passed |
| The output declines to vendor Spec Kit files into the repository. | Missed | Passed |
The instructions your model reads when the skill loads.
Load this skill when the deliverable is open or rewrite a work item. Do not
vendor Spec Kit or create .specify/. Keep GitHub PR delivery on
work-github-playbook.md. One GitHub issue tracks the full plan. When the owner names a currently active PR, deliver the plan and the user-issue fix in that same PR.
Contract and adapters: work-item.md.
One work item owns one actionable problem. Trackers list children; they do not absorb them. Preserve existing acceptance when rewriting.
Every body must include:
Keep adopter template headings (for example bug or feature fields) so existing validators still match.
When rewriting an existing item for Spec Kit hygiene, specialize User Story,
FR-*, and SC-* from that issue's own acceptance (see
scripts.agents.issue_filing.rewrite_body_spec_kit). Keep the shared heading
checklist; never paste the generic stamp Deliver the stated acceptance onto
unrelated tickets. Trackers may keep a campaign-level story.
Exactly one primary type, exactly one lifecycle, at least one subsystem or module. Missing taxonomy fails closed with a named reason. Ready needs a proof plan; blocked needs at least one https dependency URL.
test cases passed, vs 6 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.