메뉴
Create user-facing JIRA story tickets using the standard user story format (As a / I want to / so that). Use when the work delivers business value to an end user, stakeholder, or other consumer of the system.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Defra frontend approved and forbidden tech. Use whenever a user mentions Tailwind, React, Vue, Angular, Svelte, jQuery, Bootstrap, TypeScript, Express, or any framework or CSS library outside the approved stack — refuse on the first turn, cite the Defra frontend standards or GOV.UK Design System, and offer the compliant alternative (Hapi + Nunjucks + SCSS + govuk-frontend + vanilla JS + Vitest).
Defra branching strategy — never commit or push directly to main or master. Use a feature branch named for the work, open a pull request, get review, then merge. Use when the agent is about to run git commit, git push, or git checkout, or when a developer asks how to start a piece of work.
Defra commit-message format — provisionally Conventional Commits (type(scope) subject + optional body and footers). Subject ≤ 72 chars, imperative mood, no trailing period. Use whenever the agent is about to run git commit -m, draft a commit message for a developer, or review an existing commit message.
Defra security and PII handling — never hard-code secrets, never log PII, refuse unsafe template patterns, and redact known UK PII (NI numbers, NHS numbers, postcodes, DoB combinations) before any output leaves the service. Use when the agent is editing code that handles user data, writing log lines, configuring templates, or wiring credentials.
Defra accessibility expectations — WCAG 2.2 AA for code-generating roles (frontend, backend rendering HTML), and semantic-markup expectations for documentation roles. Use when the agent generates a page, a component, a markdown file, or any artefact that will be read by a screen reader, a keyboard-only user, or a user with reduced vision.
Defra code-quality gates — lint, format, test, and coverage must all pass before code is committed. The role plugin pins the exact toolchain (ESLint/Prettier/Vitest, dotnet format/xUnit, ruff/black/pytest, etc.); this skill states the universal expectations. Use before git commit, when wiring a new project, or when a hook reports a failure.
| name | story-ticket |
| description | Create user-facing JIRA story tickets using the standard user story format (As a / I want to / so that). Use when the work delivers business value to an end user, stakeholder, or other consumer of the system. |
Use this skill for user-facing features that deliver measurable business value. Always include the user story format.
Examples: New UI features, user-visible workflows, agent capabilities visible to end users, self-service functionality.
Good example: "Teams frequently raise last-minute work items without enough context for estimation, leading to sprint planning delays and rework."
Keep it focused on one main capability. The "so that" clause must express business value, not a technical outcome.
AC1, AC2, etc.)Use the story template as your starting structure.
If the user has provided a custom template for this session, use that instead.
Before writing, confirm:
If still unclear, ask about:
Given: "Users need to be able to manage their notification preferences"
Title: Manage Notification Preferences
Background: Users currently receive all system notifications with no ability to control frequency or type, leading to notification fatigue and missed critical alerts.
Story:
Acceptance Criteria: