'tickets' 검색 결과

계획, 명세, 대화를 각각 동작을 확인할 수 있는 작은 개발 티켓으로 나눕니다. 의존 관계와 착수 순서를 명시하고 사용자 확인 후 로컬 파일이나 이슈 관리 도구에 등록합니다.

• 명세를 개발 티켓으로 나누기
• 티켓 의존 관계와 착수 순서 정리
• 광범위한 변경을 단계적으로 진행

명세서와 관련 티켓의 의존 관계를 읽고 여러 에이전트가 구현을 진행합니다. 테스트와 검토를 거쳐 결과를 하나의 통합 브랜치로 모으고 티켓 완료 처리까지 진행합니다.

• 여러 티켓으로 나뉜 명세 구현
• 독립적인 작업의 병렬 구현
• 구현 결과를 통합 브랜치에 모으기

Turn plans, specifications, or conversations into small implementation tickets that each deliver verifiable behavior. Define acceptance criteria and dependencies, review the breakdown together, then publish approved tickets to the configured tracker or local Markdown files.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Break a specification into independently verifiable tickets
• Clarify ticket dependencies and starting order
• Publish approved tickets to a tracker or local files

Turn a specification and its linked tickets into code. Multiple agents work on available tasks in separate worktrees, combine changes on one integration branch, and complete a code review before preparing the result for review or closing tickets.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implementing a specification and its linked tickets
• Working through tasks with blocking dependencies
• Coordinating parallel implementation in separate worktrees

Use when materialising a roadmap into a ticket bundle — 'turn this roadmap into tickets', 'materialise tickets', 'mach Tickets aus der Roadmap', 'emit tickets for this plan'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Orca에 저장된 Jira 연결로 티켓을 읽고 업데이트합니다. Jira로 받은 작업 요청을 확인하고 티켓에 반영하며, 여러 사이트가 해당하면 사이트 ID로 대상을 지정합니다.

• Jira로 받은 작업 요청 확인
• 에이전트에 Jira 티켓 업데이트 맡기기
• 여러 Jira 사이트에서 대상 지정

Orca의 CLI로 Linear 티켓을 검색하고 갱신합니다. 연결된 이슈를 바탕으로 작업하고, PR/MR 링크로 완료를 보고하며 부모 이슈에 연결된 후속 티켓을 만듭니다.

• 연결된 Linear 이슈를 바탕으로 작업
• PR/MR 링크와 댓글로 완료 보고
• 티켓 검색과 진행 상태 갱신

Orca의 명령줄 인터페이스로 Linear 이슈를 검색하고 진행 상태를 변경합니다. 상위 이슈에 연결된 후속 티켓을 만들고 PR/MR 링크와 완료 댓글을 기록합니다.

• Linear 이슈에서 작업 시작
• 티켓의 진행 상태 업데이트
• PR/MR 링크로 완료 보고

Turn ideas, briefs, product requirements, or meeting notes into actionable tickets with Sofia, the Product Owner. Break large initiatives into smaller work items, refine requirements, review board status, validate ticket structure, and replan when requirements change.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turn ideas and notes into ticket requirements
• Break large initiatives into smaller work items
• Refine tickets and review readiness

Guide a development brief through specification, dependent tickets, implementation, review, and verification. Coordinate parallel work while keeping human approval at key decisions and recording agreed vocabulary, business rules, and the reasons behind technical choices.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning a development brief into a specification and tickets
• Coordinating parallel implementation across dependent tickets
• Approving acceptance criteria and testing boundaries

Investigate forged Kerberos authentication tickets in Active Directory by checking Windows logs for unusual encryption, excessive ticket lifetimes, and missing authentication requests. Produce a JSON report of suspicious indicators with risk ratings.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating suspected forged authentication tickets
• Checking for possible krbtgt credential theft
• Building detection rules from authentication logs

Assess whether stolen Kerberos tickets, credentials used for network authentication, can enable access to other systems during authorized testing. Guide ticket extraction and reuse, review detection indicators, and document evidence for security reports.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Authorized testing of access through reused tickets
• Checking detection of Kerberos ticket theft
• Collecting evidence for lateral movement reports

Create Jira tickets from meeting notes, user stories, or quick lists. Use this skill when: - User says "create tickets", "make Jira tickets from", "push to Jira" - User has meeting action items to convert to tickets - User has user stories from a spec to push to the backlog - User wants to batch-create tasks, stories, or bugs

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Personal App-in-Skill customer-support desk (help desk) that triages incoming support tickets from email, WhatsApp, web chat, contact forms, and WeChat, drafts KB-grounded replies, and proposes actions, then holds every send behind a human approval queue with a pre-send quality gate (support-qa) that outputs SHIP/FIX/BLOCK, plus SLA and CSAT tracking. Use when the user invokes $kelly-support or /kelly-support, mentions 客服 / 工单 / 支持台, a support desk, help desk, customer service, support tickets, ticket triage, a knowledge base or canned macros, SLA / first-response time, CSAT, escalations, or refund requests, wants incoming tickets triaged into a needs_review → approved → done pipeline, agent-drafted replies grounded in a knowledge base and reviewed before sending, refunds and commitments gated behind human approval, or breaching-SLA tickets surfaced. This is the OPERATOR desk (agent + human), distinct from a visitor-facing chat bubble.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

인터뷰, 문의, 설문을 정리해 제품과 디자인 결정에 쓸 HTML 화면을 만듭니다. 근거, 주제, 확신 수준, 개선안 비교와 다음 실험을 함께 제시합니다.

• 인터뷰와 고객 문의를 함께 분석합니다
• 초기 설정 개선안을 비교합니다
• 관계자에게 근거와 불확실성을 공유합니다

Review and manage issues, projects, and planning data in Linear. Use it to examine development cycles, find carried-over tickets and release blockers, and update issue status, assignees, priorities, or milestones with the required access.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing sprints and development cycles
• Finding tickets carried over into the next cycle
• Identifying issues blocking a release

Examine Windows credential material in a CTF sandbox, including LSASS memory and Kerberos tickets. Distinguish stored secrets from credentials that actually work, and document the evidence linking their source to successful authentication or resulting privileges.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Examining LSASS secrets and Windows logon sessions
• Checking whether recovered Kerberos tickets are usable
• Tracing DPAPI and SSP credential material

Analyze Windows identity and host evidence in CTF sandboxes. Connect authentication tickets, credentials, mailbox rules, and host activity to explain which services accept access and how movement between hosts occurs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Tracing authentication tickets and tokens
• Investigating mailbox rules alongside identity events
• Building a timeline of Windows host evidence

Trace movement between Windows hosts in a CTF sandbox using credentials and Kerberos tickets, which carry authentication information. Connect recovered artifacts to the service that accepted them and document the resulting access or privileges.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Trace movement between Windows hosts
• Identify services that accept recovered credentials
• Connect Kerberos tickets to resulting access

Write or revise instructions, specifications, tickets, and skill files so an agent can act without prior chat history. Make rules checkable, explain their reasons, define completion criteria, and keep authoritative information in one place.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clarifying instructions in CLAUDE.md
• Making specifications and tickets actionable
• Adding completion criteria to skill procedures

Investigate stolen Kerberos tickets, authentication credentials that can be reused without a password, by correlating Windows security events. Build Splunk or Elastic detection rules for cross-host reuse, weaker encryption, and unusual request volumes, and report risk-scored findings.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating suspected reuse of stolen Kerberos tickets
• Building Splunk or Elastic detection rules
• Finding unusual ticket request volumes

Investigate Active Directory authentication logs with Splunk and KQL queries to find signs of Golden Ticket attacks, which use forged Kerberos authentication tickets. Examine encryption mismatches, missing ticket requests, unusual lifetimes, and account inconsistencies.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Hunting for forged tickets after credential theft
• Investigating encryption mismatches in authentication logs
• Checking for persistent access after incident response

Manage Jira issues through natural language using jira CLI or Atlassian MCP, a tool connection. Search and view tickets, draft new issues, update assignments or status, and check sprints, with review and approval before changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking the details of an issue by its key
• Listing tickets assigned to you
• Drafting and creating a new issue

Turn development tickets, product requirements, or internal changelogs into release notes users can understand. Organize updates into features, improvements, and fixes, explain their benefits, and highlight changes that require users to take action.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating release notes from development tickets
• Turning internal changelogs into user announcements
• Explaining updates that require user action