codingthefuturewithai/teamcraft-jcg:create-issue
plugins/teamcraft-jcg/skills/create-issue/SKILL.md
Create a single well-formed Jira issue at any time — bugs found in production, features requested by stakeholders, technical debt noticed during development, chores that need doing. Follows the same issue standards as plan-sprint, always. Works in Claude Cowork and Claude Code.
development
Updated Apr 20, 2026
$ install --global
skillsauthnpx skillsauth add codingthefuturewithai/claude-code-primitives teamcraft-jcg:create-issueInstall 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 20, 2026, 3:25 AM20.6s4 files scanned
SKILL.md
- name:
- teamcraft-jcg:create-issue
- description:
- Create a single well-formed Jira issue at any time — bugs found in production, features requested by stakeholders, technical debt noticed during development, chores that need doing. Follows the same issue standards as plan-sprint, always. Works in Claude Cowork and Claude Code.
- argument-hint:
- [brief description of the issue]
- disable-model-invocation:
- true
- user-invocable:
- true
Goal
Create one well-formed Jira issue that gives a developer everything they need to pick it up cold. The same standards apply regardless of when or why the issue is created. One issue. Explicit confirmation. No exceptions.
Identify the Project
Use mcp__sooperset-mcp-atlassian__jira_get_all_projects to see what is visible, surface the results, and ask the user which project this issue belongs to. Never ask the user to supply a project key string. Confirm once identified. Record the Jira project key.
Load Context
Ask the user if they can point at the tech decisions and conventions documents in Confluence. If they can point at a page by URL or ID, use mcp__sooperset-mcp-atlassian__confluence_get_page directly. If they cannot, use mcp__sooperset-mcp-atlassian__confluence_search to find relevant pages. If page IDs are available from .teamcraft/project.md, use them directly. These documents inform the technical guidance section of the issue. If nothing is available, proceed without — the user's description carries sufficient context.
Understand the Issue
Use $ARGUMENTS as the starting point if provided. Determine issue type — feature (Story), bug, task, or chore. Ask if not clear from the description.
Standard Jira issue types are Story, Bug, Task, Epic, and Subtask — the mcp__sooperset-mcp-atlassian__jira_create_issue tool accepts the type as a string. If the user describes a non-standard type or you need to discover custom fields, use mcp__sooperset-mcp-atlassian__jira_search_fields to find available fields by keyword.
Draft and Confirm
Before drafting, read the reference file matching the issue type — references/example-feature-issue.md, references/example-bug-issue.md, or references/example-chore-issue.md. These define the required structure. Every issue must include all sections from the reference: Background & Goal, Acceptance Criteria, Technical Guidance, and Testing Requirements (for features and bugs) or Verification (for chores). An issue missing any of these sections is incomplete.
Show the draft. Get explicit confirmation before creating. Never create without approval.
Create
Create the issue in Jira using mcp__sooperset-mcp-atlassian__jira_create_issue. Issues are created in the backlog — sprint assignment is handled by the PM during sprint planning. Report the issue key (e.g., PROJ-42) and URL.
Related Skills
codingthefuturewithai/teamcraft:plan-iteration
development
VerifiedTrustedCommunity
Plan a time-boxed iteration (sprint, cycle, milestone) from the backlog and the PRD/roadmap behind it — gather the goal, the window, and the team's real capacity, then select, sequence, and size a committed set of work items to fit. Writes an `iteration` label onto each chosen work item. Use when the user says 'plan a sprint', 'plan the next iteration', 'plan our cycle', 'sprint planning', 'iteration planning', 'plan the next two weeks', 'set up a milestone', 'what should we take on this sprint', 'plan from the PRD', or otherwise wants to commit a scoped, time-boxed batch of work rather than create issues one at a time. This is the planning layer between requirements and the build loop — distinct from create-issue (one item) and pick-next-issue (pick one to build now).
SKILL.mdUpdated Jun 6, 2026
codingthefuturewithai/teamcraft:improve-teamcraft
tools
VerifiedTrustedCommunity
Capture feedback about Teamcraft itself and turn it into a well-structured GitHub issue on the plugin's repo. Vets whether the problem is really a Teamcraft skill defect (vs. misuse, the harness, or the user's own project) by root-causing against the actual skill source, then helps the developer decide whether to file and publishes via the GitHub CLI. Use when the user says 'improve teamcraft', 'a teamcraft skill did the wrong thing', 'file feedback on teamcraft', 'report a teamcraft bug', 'I have an idea to make teamcraft better', or when a Teamcraft skill clearly misbehaved and the user wants that captured upstream.
SKILL.mdUpdated May 31, 2026
codingthefuturewithai/teamcraft:learn-teamcraft
tools
VerifiedTrustedCommunity
Learn the Teamcraft plugin itself — how its workflow, skills, and artifacts fit together. A guided overview for a human getting started, or a system map for Claude orienting itself to how Teamcraft works before working in a Teamcraft repo. Teaching only; needs no project or environment access. Use when someone wants to understand Teamcraft (the tool, not their specific project), asks "how does Teamcraft work", "explain the workflow", "which skill do I use for X", or when Claude needs the big picture of how the skills hook together.
SKILL.mdUpdated May 29, 2026
codingthefuturewithai/plugins/teamcraft/skills/work-board
tools
VerifiedTrustedCommunity
--- name: teamcraft:work-board description: Launch (or re-launch) the user's live, multi-project work board. The dashboard is a single HTML file copied to a stable user-side location at ~/.claude/teamcraft-board.html and opened in the user's default browser. It has two views via a header toggle — a drag-and-drop Kanban Board and a live Status tab (analytics: work by status, throughput, cycle time, aging, blocked chains, recomputed on every poll). Each project is added via a header dropdown; the
SKILL.mdUpdated May 11, 2026