Przejdź do treści
Biblioteka skilli
Zarządzanie i produkt · Planowanie

create-eng-tickets

/create-eng-tickets

Tworzy zgłoszenia inżynierskie, epiki lub historie Jira na podstawie zatwierdzonego prototypu, dopiero po zgodzie PM.

Repozytorium
pm-harness ↗
Licencja
MIT
Ostatnia zmiana repozytorium
12.11.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 12.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Tworzy zgłoszenia inżynierskie, epiki lub historie Jira na podstawie zatwierdzonego prototypu, dopiero po zgodzie PM.

Oryginalny opis (EN)

Use only when the PM explicitly asks to create engineering tickets, an epic or Jira stories for an item with an approved prototype. Step 5 of the pipeline - drafts tickets whose acceptance criteria are the behaviour tree lines, adds the Definition of done, checks traceability, and creates them in the tracker only after approval.

Jak działa

  1. Needs
  2. Steps
  3. Handoff to engineering
Sekcje z nagłówków SKILL.md, w oryginale · 69 linii, 626 słów
Podgląd SKILL.md
---
name: create-eng-tickets
description: Use only when the PM explicitly asks to create engineering tickets, an epic or Jira stories for an item with an approved prototype. Step 5 of the pipeline - drafts tickets whose acceptance criteria are the behaviour tree lines, adds the Definition of done, checks traceability, and creates them in the tracker only after approval.
disable-model-invocation: true
---

# Step 5 · Engineering-ready tickets

Tickets carry the contract to engineering unchanged. Acceptance criteria are the tree lines
themselves, so nothing is lost or reworded between product and test. The Definition of done
says what "finished" means for every story.

Read first: `work/<item>/02-prd.md` (phase, §6.3 chosen variant, §7 metrics, §8 constraints),
every tree in `work/<item>/03-trees/`, the prototype and its `amendments.md`,
`context/definition-of-done.md`, `../../reference/phases.md` and `context/tools.md` (the
`issue-tracker` tool and its project).

Before starting, confirm the prototype check passes with no open amendments. If it does not,
stop and offer the `review-prototype` skill.

## Needs

Before starting, run `python3 .pm-harness/pm_check.py needs create-eng-tickets` and confirm each tool
answers (preflight in `../../reference/connectors.md`).

- `issue-tracker` · required · creating the epic and stories after approval; without it, the
  approved draft is the hand-off and the PM creates them

## Steps

1. **Draft the epic:** title, phase, the job statement, links to the PRD, prototype (with the
   chosen variant) and trees, success metrics and their events, and the phase's gate from §7.
2. **Draft one story per Functional tree** (split a very large tree by its top-level `when`).
   Each story contains:
   - **Goal:** one line in user terms, citing its PRD section (§5.1)
   - **Acceptance criteria:** the tree's lines copied *verbatim*, in a fenced block, with the
     tree file path
   - **Prototype:** the screens of the chosen variant that demonstrate it, as deep links
     (`index.html#guided--set-alert`, or the published artifact URL with the same `#…`)
   - **Out of scope:** from the PRD's non-goals
3. **Draft one story for the Journey tree(s)** as the end-to-end acceptance test.
4. **Draft one analytics story** listing the events needed to measure each success metric and
   gate, naming the metric each event serves (`for alert adoption`). Analytics lives here, not
   in the trees. If the PM chose to ship two variants as an experiment, add the experiment flag,
   assignment and the comparison metric here.
5. **Definition of ready** for all stories: trees approved, prototype approved with no open
   amendments, open questions resolved or owned, dependencies named.
6. **Definition of done** for all stories: copy `context/definition-of-done.md` (every item
   under *Every story*), then add the items for this phase. Add story-specific items only
   where a story needs more (a migration, a third-party sign-off).
7. **Check traceability:** write the draft to `work/<item>/05-tickets.md` and run
   `python3 .pm-harness/pm_check.py tickets work/<item>/03-trees work/<item>/05-tickets.md work/<item>/02-prd.md`.
   It fails if a tree outcome is missing from every ticket, a ticket contains a `then`/`and`
   line that is not in a tree (an invented requirement), a PRD §7 metric is not named in the
   analytics story, or there is no Definition of done with at least three items. Fix until it
   passes, then run `python3 .pm-harness/pm_check.py item work/<item>` for the whole item.
8. **Show the PM the full draft and ask for approval** to create the tickets.
9. **Only after approval,** create the epic and stories with the `issue-tracker` tool, attaching
   or linking the trees and prototype. Record the created ticket keys in `05-tickets.md`.
   If creation partly fails, report exactly which tickets exist and which do not.

## Handoff to engineering

1. Run `python3 .pm-harness/pm_check.py contracts work/<item>`. It writes one contract per tree
   to `work/<item>/05-contracts/<subject>.contract.md` in the engineering harness's format:
   `Contract: <subject> (seam: <PRD Seam line>)`, the tree's lines unchanged, the PRD's
   non-goals and the source. If it warns that a capability has no `Seam:`, confirm the seam with
   the engineering lead and add it to the PRD (change control) before handing over.
2. Tell the PM how engineering picks this up: copy `05-contracts/` into the service
   repository's `contracts/` folder; the engineering harness implements each clause
   test-first and keeps code, tests and contracts in sync. Link the contracts from the epic.
3. Set `stage: tickets` in `01-idea.md`, log the decision to build in
   `decisions/decision-log.md`, and offer the `stakeholder-update` skill.

Wersje

W bazie nie ma innych skilli o nazwie create-eng-tickets.

Migawka bazy z 13.11.2026 · wersja paczki 1b0a1598c1a6 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 96jira-tickets-from-plan
    Tworzy zgłoszenia w Jira na podstawie planu przygotowanego przez AI.
  • 96jira-tickets
    Tworzy, aktualizuje, sortuje i usuwa zgłoszenia w Jira przez polecenia CLI jira.
  • 100jira-ticket-creator
    Tworzy tickety Jira z notatek ze spotkań, historyjek użytkownika lub krótkich list, w tym zbiorczo zadania, historie i błędy do backlogu.
  • 100ticket-authoring
    Pisze kompletne zgłoszenia do trackera: błędy, zadania, historyjki, spiki i epiki, z polami, załącznikami i testem ukończenia, w Jira, Linear lub GitHub Issues.
  • 90create-jira-item
    Tworzy zgłoszenia Jira (story, epiki, inicjatywy) z introspekcją pól niestandardowych, by poprawnie wypełnić pola specyficzne dla organizacji.
  • 100tracker
    Pomaga w pracy z trackerem Linear lub Jira: sprawdza, co blokuje prace, sortuje nowe zgłoszenia i łączy je z gałęziami i CI.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.