start
/start
Zakłada zgłoszenie w Jira z szablonem typu pracy, priorytetem i powiązaniami; zmiany robi tylko w backlogu.
- Autor
- dedujeong ↗
- Repozytorium
- gemba ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 12.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 8
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 12.11.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
Co robi i kiedy
Zakłada zgłoszenie w Jira z szablonem typu pracy, priorytetem i powiązaniami; zmiany robi tylko w backlogu.
Wyzwalacze z opisu
Oryginalny opis (EN)
Declare one Jira issue with the template of its work type and its priority, component, fix version and blocking links, and handle every change to an existing issue, which is only edited in Backlog. Use when someone says "declara", "hay un bug", "nueva tarea", "registra un spike" or describes work to track; when someone asks to change, edit or add a criterion to an issue ("cambia la descripción de", "agrégale un criterio a"); and when Gemba Product's `version-start` declares a release card.
Jak działa
- 1. Find the project
- 2. Choose the work type
- 3. Fill the fields
- 4. Write the description
- 5. Show it, then create it
- 6. Edit only in Backlog
- 7. Report
Podgląd SKILL.md
---
name: start
description: Declare one Jira issue with the template of its work type and its priority, component, fix version and blocking links, and handle every change to an existing issue, which is only edited in Backlog. Use when someone says "declara", "hay un bug", "nueva tarea", "registra un spike" or describes work to track; when someone asks to change, edit or add a criterion to an issue ("cambia la descripción de", "agrégale un criterio a"); and when Gemba Product's `version-start` declares a release card.
---
# Start an issue
You declare one unit of work in Jira so it can be built: the right work type, a description from its template, and every field filled. Declaring is the whole job; you do not implement anything. A card that Gemba Product's `version-start` hands over is declared exactly the same way.
## 1. Find the project
Read the `## Gemba` section of the project's `CLAUDE.md`: `Jira Project`, `Confluence Space` and `Language`. If it is missing, propose running `setup` first and stop. Use its `Jira Site` as the `cloudId` of every call; only when the block has none, get it once with `getAccessibleAtlassianResources` and propose running `setup` to add it. Every call to Jira is the one written in `../../references/jira-calls.md`, with its `fields` and `responseFields`.
Read the Product Brief in the Confluence space for its actors and business rules. The issue content is written in `Language`.
## 2. Choose the work type
Declare one issue per request. The exceptions are the whole release that Gemba Product's `version-start` hands over in one request, and a Story Map card with two or more stories: the Epic and one Story per story are declared together, as one request. A card with one story is a Story with no Epic.
| Work type | Use it when |
| --- | --- |
| Epic | A Story Map card with two or more stories: a goal done through its children, never by itself, inside one version |
| Story | Something a user can do that they could not before |
| Task | Technical work no user sees but other issues need: repo, stack, deploy, roles |
| Bug | Something already delivered does not do what it should, and the issue that delivered it is Done. If that issue is not Done yet, it is not a bug: say so and propose adding the case to that issue's criteria while it is in Backlog |
| Spike | A question a decision depends on, answered in a fixed timebox |
## 3. Fill the fields
| Field | Rule |
| --- | --- |
| Summary | English, understandable on its own, no parentheses. The branch comes from the key and the summary |
| Priority | Highest, High, Medium or Low, by how much other work waits on it |
| Component | The part of the repository the change touches, in lowercase; it is also the commit scope. Read the existing ones with List the components (`listJiraProjectComponents`) and reuse one when it fits. When none fits, propose a new one and say that it is new; naming it in the create call creates it. In a project with no components yet, take the part from the structure and stack that the Product Brief and the `CLAUDE.md` describe, or from what the issue itself names (`api`, `web`, `db`, `ci`). Prefer few broad components to one per issue. An Epic has no component |
| Fix version | The one named by the person or by Gemba Product's `version-start`. Otherwise the earliest unreleased version, with List the versions (`getJiraProjectVersions`). If there is none, stop and say that Gemba Product's `version-start` has to create it. Never create a version here |
| Original estimate | Story, Task and Bug: the expected hours of one person working with Claude. Spike: its timebox in hours. Epic: none. Follow `references/estimation.md` |
| Due date | Epic only, set by the maintainer. Ask for it if they did not give it |
| Blocks / is blocked by | Ask what must exist first. Search the version's open issues with Search issues (`fixVersion = "<version>" AND statusCategory != Done`) and propose the blockers you find, only the direct ones: if A blocks B and B blocks C, C is blocked by B and never by A, because Jira already shows the chain. When the person names both, create the link only to the direct one and say that the other is covered through it; never create the link of the second. The release Task has none: it waits for the other issues of the version to be Done or Cancelled |
Ask for anything above you cannot read or infer from what the person said, in one message.
## 4. Write the description
Use the template of the work type in `assets/`: `epic.md`, `story.md`, `task.md`, `bug.md` or `spike.md`. Write it in HTML from the first version, so block cards and other rich content are right: `<p>`, `<h3>`, `<ul><li>`, `<ol><li>`, `<code>`.
- Content in `Language`; section headings in English, as H3. The opening paragraph has no heading.
- Every list is bulleted, with no checkboxes. Only Steps to reproduce is numbered.
- Code (field names, routes, commands, error messages) goes in code style.
- No bold. Never mention Gemba Code or where the issue came from.
- Only the sections of the template; omit a section when there is nothing to put in it.
- Business rules and out-of-scope items come only from the Product Brief and the Story Map, in their words. When something needed is missing, ask.
- Every Story has acceptance criteria in the form "Dado <contexto>, cuando <acción>, entonces <resultado>": at least the observable result the story promises. A Story that touches money or permissions also covers the rule that protects it, and each of its criteria states a result an automated test can check as true or false. Write only criteria that the request, the brief or the card state: when the rule that protects money or permissions is not stated, ask for it instead of inferring a criterion.
- The issue is the request, not the specification: generic referents, no invented sample data, and only what the person observes, never how it is achieved. Before showing the declaration, reread every line and remove what the Product Brief does not state.
| Instead of | Write |
| --- | --- |
| Dado un pedido de 3 productos a $35, cuando se confirma, entonces el total es $105 | Dado un pedido con varios productos, cuando se confirma, entonces el total es la suma del precio de cada producto por su cantidad |
| Dado el cliente «Juan» | Dado un cliente |
| Entonces se calcula en el servidor y se muestra en un modal | Entonces se ve el total |
### Check the edge cases of a Story
Only for a Story. Once the happy-path criteria are written and before showing them, read `references/criteria-heuristics.md` and pass every criterion through every heuristic of its table. Each heuristic that applies to a criterion ends in one of three places:
- A criterion more, only when the Product Brief, the Story Map or the card decides the case.
- A line of Out of scope, only when the brief or the Story Map leave it out, in their words.
- A question to the maintainer, for everything else. Never infer a criterion to close a gap.
Ask all the questions of the Story in one single round, in the project's `Language`, each one starting with both labels, with no exception: «Criterio: <the criterion it comes from>. Heurística: <the heuristic that found it>. ¿...?» (for example: «Criterio: el dueño aplica un descuento. Heurística: límite. ¿...?»). A question that cannot name a criterion and a heuristic is not asked. Do not ask them one by one. While a question has no answer, do not create the Story: say that nothing was created and which question is missing. The criteria already decided may be shown as a draft that waits for the answers.
When a rule depends on two or more conditions, build its decision table inside, with the method of `references/criteria-heuristics.md`, with every combination, and write one criterion per distinct result: every combination with the same result is one single criterion, even when its combinations differ in more than one condition, and that criterion names them all. The table is a working tool and never goes in the issue.
An Epic, a Task, a Bug and a Spike skip this check. The declared Story shows only the resulting criteria, rules and Out of scope: it never mentions the heuristics, the decision table or the questions.
### Check the edge cases of a whole version
When Gemba Product's `version-start` hands over the whole release in one request, pass the Stories of every card through the heuristics as above, the Stories of an Epic too, before creating any issue. Ask one single round for the entire version, in the project's `Language`, grouped by Story, each question in the format above. A Story that raises no question does not appear in the round. While any question of the round has no answer, create no issue of the version, not even those of the Stories already answered or the release Task: say that nothing was created and name the questions still missing. When every question is answered, or the round had none, create the whole version without asking for another confirmation.
## 5. Show it, then create it
Show the declaration in one compact block: work type, summary, priority, component, fix version, original estimate, due date, blockers and the description. The maintainer can change any of them, the estimate included, before it is created. Wait for the person's OK. When Gemba Product's `version-start` hands over a card, the maintainer already confirmed the whole version: create it without asking again, not even to review a part of it. Write only what the card, the brief and the Story Map support; never add criteria you infer, since they would need a review the maintainer already gave.
Then:
1. Create the issue with Create an issue (`createJiraIssue`): `contentFormat: "html"`, the description, `priority`, and in `additional_fields` `fixVersions` (`[{"name": "<version>"}]`), `components` (`[{"name": "<component>"}]`, never for an Epic), `timetracking` (`{"originalEstimate": "<n>h"}`, never for an Epic) and `duedate` for an Epic. New issues land in Backlog.
2. For an Epic, create it first, with the Story Map as a block card in its Source, and then each of its Stories with `parent` set to the Epic's key. Show the Epic with all its Stories in the block before creating. Never add a Story to an Epic that is already declared.
3. Create each blocking link with Link two issues (`createJiraIssueLink`): `linkType: "Blocks"`, `inwardIssue` the blocker, `outwardIssue` the blocked issue.
Declaring a Spike creates only the issue; its findings page is created when the test ends.
Without a connection to Jira, write in the reply the exact create call and links you would send, and say that nothing was created.
## 6. Edit only in Backlog
When someone asks to change an issue, read its status first. In Backlog, edit it with Edit an issue (`editJiraIssue`, `contentFormat: "html"`), following the same template. In Implement, Review or Done, do not edit it: say that an issue is edited only while it is in Backlog, and stop there. Do not move it back to Backlog and do not propose another path.
## 7. Report
Reply with the keys as links, one line each, and anything you decided for the person (a work type, a priority, a blocker). Nothing else.
Pliki w paczce (8)
- SKILL.md 11 KB
- assets/bug.md 1 KB
- assets/epic.md 1 KB
- assets/spike.md 1 KB
- assets/story.md 1 KB
- assets/task.md 1 KB
- references/criteria-heuristics.md 2 KB
- references/estimation.md 2 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · dedujeong/gemba | 100 | Apache-2.0 |
| tilnoteio/tilnote-blog | 100 | MIT |
| nextwork-projects/ai-video-editor-cooked | 100 | MIT |
| wrg32786/aigent-os | 100 | MIT |
| T-X-R/codex-game-studio | 100 | MIT |
| alienfast/claude | 100 | MIT |
| ratomirjovanovic/pandaward | 100 | AGPL-3.0 |
| darioabc/massimo | 100 | MIT |
| khadinakbarlabs/citebase | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki f341d58ded09 (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
- 100create-jira-issue
Tworzy zgłoszenie Jira z właściwymi powiązaniami, kontekstem z semantycznego wyszukiwania w kodzie i powiadomieniem zespołu. - 90session-start
Rozpoczyna sesję od przekazania zostawionego w .gemba/sessions, sprawdza je z Jira i kodem oraz proponuje jeden następny krok. - 100clone-jira-issue
Klonuje zgłoszenie Jira do podobnej pracy, łączy je z oryginałem i przypisuje do bieżącego użytkownika. - 100github-flow
Prowadzi pracę w repozytorium przez GitHub Issues, Projects i Milestones, od pomysłu w backlogu do wydania wersji. - 95file-issue
Zamienia prośbę lub odkryty błąd w zgłoszenie GitHub w formacie repozytorium: dopytuje o intencję, sprawdza duplikaty i zakłada zgłoszenie. - 98edit-description
Edytuje opisy zgłoszeń JIRA przez CLI jira, także przygotowując szczegółową dokumentację do ticketów.