Menu
Create a JIRA task through user interview, codebase exploration, and module design
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use to create a pull request with detailed summary and description
Create a git worktree for an own or someone else's branch, symlink local-only files (.env, .tmux-sessionizer), optionally install or symlink node_modules, and open it in tmux
How to create and name git branches
Use this when you need to do a full workflow -- create a JIRA ticket, create a branch, create a PR, push changes
Review code changes for quality and best practices. Use when reviewing pull requests, examining code changes, or providing feedback on code quality. Covers security, performance, testing, and design review.
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.
| name | write-jira |
| description | Create a JIRA task through user interview, codebase exploration, and module design |
This skill will be invoked when the user wants to create a JIRA task. You may skip steps if you don't consider them necessary.
Ask the user for a detailed description of the problem they want to solve and any potential ideas for solutions.
Explore the repo to verify their assertions and understand the current state of the codebase.
Interview the user about every aspect of this plan until you reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one.
A deep module (as opposed to a shallow module) is one which encapsulates a lot of functionality in a simple, testable interface which rarely changes.
Check with the user that these modules match their expectations. Check with the user which modules they want tests written for.
Run the CLI script to create the JIRA task. Ask the user everything needed for running the CLI script: project, issue type, labels
If it's a sub-task, run the CLI so that the user selectes the main story/task/bug
Once you have a complete understanding of the problem and solution, use the template below to write the JIRA task. Ask the user if this is a bug, task, sub-task or story. Use the JIRA cli for this (https://github.com/ankitpokhrel/jira-cli), NOT the MCP server.
jira issue create \
-p PEAKONLIGHT \
-t "Sub-task" \
-P "PEAKONLIGHT-XXXX" \
-s "Subtask summary" \
-b "Detailed description" \
-C "No component" \
-l "frontend-only"
-p: Project key (PEAKONLIGHT by default, unless user says otherwise)-t: Issue type ("Sub-task", "Bug", "Story", "Task")-P: Parent ticket number (only required for subtasks)-s: Summary/title-b: Description (can include newlines)-C: Component name. If not provided, "No component"-l: LabelsAs an , I want a , so that
As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spendingThe problem that the user is facing, from the user's perspective.
The solution to the problem, from the user's perspective.
Scenario #
Given
when
then
Given a customer has raised a customer care ticket to opt out of the new bill systemwhen the customer care analyst navigates to the dashboard
then at the bottom of the sign up screen, they will see the bill system modal
Any further notes about the feature.