avantmedialtd/start-work
skills/start-work/SKILL.md
Assign a Jira issue to yourself and convert it into an OpenSpec proposal. Use when the user says "start work", "pick up an issue", "take the next ticket", or provides a Jira key and wants to begin work on it. Handles issue selection from the backlog, assignment, transition to In Progress, and scaffolding an OpenSpec change with Jira context embedded in the proposal.
tools
Updated Apr 27, 2026
$ install --global
skillsauthnpx skillsauth add avantmedialtd/skills start-workInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 27, 2026, 6:05 AM42.6s1 file scanned
SKILL.md
- name:
- start-work
- description:
- Assign a Jira issue to yourself and convert it into an OpenSpec proposal. Use when the user says "start work", "pick up an issue", "take the next ticket", or provides a Jira key and wants to begin work on it. Handles issue selection from the backlog, assignment, transition to In Progress, and scaffolding an OpenSpec change with Jira context embedded in the proposal.
Start Work
Assign a Jira issue to yourself and convert it into an OpenSpec proposal. Hands off to the OPSX workflow once the proposal exists.
When to use
- The user wants to start work on a specific Jira issue they've named.
- The user wants to pick up the next available issue from the board ("start work", "next ticket").
- The user is beginning a new unit of work and needs both the Jira and OpenSpec side set up.
Examples:
- "start work" — takes the topmost issue from the board after confirming.
- "start work PROJ-123" — uses the specified issue.
Steps
-
If no issue-key is provided, fetch the topmost issue from the board:
- Detect project key by running
af jira projects --json- If single project: use it
- If multiple projects: ask the user to choose
- Fetch the topmost backlog issue using:
af jira search "project = <PROJECT> AND status = 'Selected for Development' ORDER BY Rank ASC" --limit 1 --json - Display the issue summary and ask the user for confirmation before proceeding
- If no backlog issues found: inform the user the Selected for Development column is empty and stop
- Detect project key by running
-
Fetch the issue details using
af jira get <issue-key>. -
Assign the issue to yourself using
af jira assign <issue-key> --to $(af jira get <issue-key> --json | jq -r '.reporter.emailAddress')— but first check who the current user is by looking at the Jira config or asking. -
Transition the issue to "In Progress" using
af jira transition <issue-key> --to "In Progress". If this fails, runaf jira transitions <issue-key>to find the correct status name. -
Create an OpenSpec change using the OPSX workflow:
- Derive a
change-idfrom the issue key and summary (kebab-case, verb-led) - Invoke the
openspec-new-changeskill (Skill tool) with thechange-id- This scaffolds the change directory, shows artifact status, and provides the first artifact template
- Then invoke the
openspec-continue-changeskill (Skill tool) to create the proposal artifact, enriching with Jira context:- Jira issue link:
**Jira**: [ISSUE-KEY](jira-url) - Why section derived from Jira issue description
- What Changes derived from issue details
- Jira issue link:
- Show the updated status
- Derive a
-
STOP and hand off to OPSX workflow
Suggest: "Proposal created. Run
/opsx:continueto create the next artifact, or/opsx:ffto generate all remaining artifacts."
Project Defaults
If the project instructions specify a default Jira project key (e.g., Jira project: PROJ), use it as the default for --project, list, types, and JQL queries. Explicit user input always overrides the default.
Reference
- See
openspec/AGENTS.mdfor OpenSpec conventions - Run
af jira --helpfor Jira CLI options - See
/opsx:newand/opsx:fffor the full artifact workflow
Related Skills
avantmedialtd/bitbucket
development
VerifiedTrustedCommunity
Manage Bitbucket Cloud pull requests, comments, tasks, and pipelines from the command line. Use when working with PRs, reviewing code, leaving inline comments, creating PR tasks, triggering or inspecting Bitbucket Pipelines, or looking up reviewer account IDs.
SKILL.mdUpdated May 13, 2026
avantmedialtd/typescript-react-standards
development
VerifiedTrustedCommunity
Opinionated TypeScript and React development standards from Avant Media. Use when scaffolding new components, reviewing code, writing TypeScript interfaces or types, setting up project structure, creating React hooks, or working on any TypeScript/React codebase. Also use when the user asks about best practices, patterns, or conventions for TypeScript or React projects, even if they don't explicitly mention "standards."
SKILL.mdUpdated Apr 27, 2026
avantmedialtd/power-stack
development
VerifiedTrustedCommunity
Bun/Elysia/React/MUI monorepo stack blueprint. Use when scaffolding a new project, adding a new app or package to the monorepo, choosing dependencies, or making architectural decisions. Contains the full tech stack, conventions, and wiring patterns.
SKILL.mdUpdated Apr 27, 2026
avantmedialtd/jira
tools
VerifiedTrustedCommunity
Manage Jira issues from the command line. Use when working with Jira issues, creating tasks, updating status, assigning work, linking issues, managing versions, setting or reading custom fields (Story Points, Sprint, Severity, etc.), or searching for issues.
SKILL.mdUpdated Apr 27, 2026