메뉴
Draft only, not yet implemented. Future companion utility skill for Jira-backed repos, intended to eventually fetch story details, acceptance criteria, links, and workflow metadata through an MCP or CLI interface.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Help a user create, draft, refine, or update the content of a deliverable specification for a bounded feature, component, bug fix, refactor, or milestone slice; use when the user wants to author the specification contract, acceptance criteria, test strategy, review shape, templates, or implementation prompt, not implement the solution. For post-greenlight implementation lifecycle, steering, QA/PR feedback, and change-log protocol, use spec-driven.
Apply or explain the lifecycle after a deliverable specification is greenlit: AC/TDD implementation, Owner steering, in-place spec contract updates, Implementation And Review Change Log entries, run logs, QA/UAT, draft PR feedback, automated review, re-verification, and final human sign-off. Use for questions about how specs, run logs, PRs, reviewers, QA, owners, and implementing agents coordinate around an approved specification.
Create or update platform-neutral handoff documents for agents and developers when work needs to be paused, transferred, resumed in another session, or cataloged as follow-up context; use for ephemeral HANDOFF notes, issue catalogs, continuation notes, next-session briefs, and cross-agent summaries.
CLI-first companion skill for interacting with GitHub Issues via the `gh` CLI under the zazzcode account. Use it to CREATE/log/file a GitHub issue — a bug, follow-up, enhancement, or observation, including when the user hits something while coding and wants to track it for later instead of fixing it now. Use it equally to READ/view/list/search an issue as input to fixing or assessment — including when the user references an issue number or says things like 'read issue #19', 'assess issue N', 'propose a fix for issue N', 'what does issue N say', or 'work on issue N'. Covers the full issue lifecycle (create, view, search, comment, close, reopen), screenshot/attachment handling, methodology-aligned routing of issue-vs-spec-vs-proposal, and the read→assess→propose-fix→feed-back workflow. Operates against GitHub Issues using the active `gh` profile (zazzcode under the zazzcode tree).
CLI-first companion skill for service-assisted repos that use Zazz Board; use it to create and manage deliverables, tasks, relations, notes, statuses, and file locks through zazzctl, with live OpenAPI as the protocol validation and fallback surface.
Help a user create, draft, refine, or update a long-lived feature document for a product capability; use when the user wants to define or improve feature purpose, current state, feature roadmap increments, related project milestone context, and feature-level direction before or alongside deliverable specification.
| name | jira |
| description | Draft only, not yet implemented. Future companion utility skill for Jira-backed repos, intended to eventually fetch story details, acceptance criteria, links, and workflow metadata through an MCP or CLI interface. |
This skill is a draft placeholder for the methodology. It is not implemented yet.
Do not present this skill as live Jira connectivity. Do not claim that Jira lookups, ticket sync, or issue validation have actually occurred through this skill.
If a task needs Jira context today:
AGENTS.md as the source of truth for repo-specific settings such as tracking system, project-code conventions, and Jira workflow rules. Read it if that context is not already available, along with any skill extension that declares Jira conventions.This draft skill is intended for two future usage patterns:
qa-testing skill, that need authoritative Jira issue context to validate acceptance criteria, confirm scope, or anchor reviewer evidence.Today, both modes still rely on repo guidance and user-provided Jira context because live integration is not implemented yet.
The important distinction is that this skill is not only for conversational lookup. It is also meant to inform downstream agents such as an agent running qa-testing, pr-builder, spec-builder, or pr-review.
This skill is expected to become the Jira counterpart to zazz-board for repos that use Jira as the authoritative issue-management system.
Future responsibilities may include:
pr-builderspec-builder, pr-builder, pr-review, and an agent running qa-testing validate that work remains aligned with the governing Jira issueThe methodology expects this to be implemented later through one of these approaches:
The final implementation path is not decided in this draft. Until that exists, this skill is documentation-only.
qa-testing needs Jira context, use repo guidance plus user-provided Jira details as the current fallback input.When this skill is implemented, it should likely follow the same broad methodology pattern as other companion utility skills:
AGENTS.md as the source of truth for repo-specific settings.