메뉴
Sprint management. View current/past sprints, velocity tracking, sprint planning, per-member workload. Usage: /javis-sprint, /javis-sprint list, /javis-sprint velocity, /javis-sprint plan
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
View sprint status, track velocity, and plan sprints.
| Command | Description |
|---|---|
/javis-sprint | Current active sprint status |
/javis-sprint list | Recent sprint list |
/javis-sprint <name> | Specific sprint details |
/javis-sprint velocity | Velocity trend analysis |
/javis-sprint plan [epic] | Next sprint planning |
/javis-sprint burndown | Burndown chart data |
/javis-sprint member <name> | Per-member status |
# Current sprint
python3 .claude/skills/javis-sprint/scripts/sprint.py current
# Velocity trend
python3 .claude/skills/javis-sprint/scripts/sprint.py velocity
# Per-assignee status
python3 .claude/skills/javis-sprint/scripts/sprint.py assignees
| Info | Table |
|---|---|
| Sprints | jira_sprints |
| Boards | jira_boards |
| Issue-Sprint mapping | jira_issue_sprints |
| Issue details | jira_issues |
| Member stats | member_stats |
Deploy the Javis viewer frontend to the remote server with sw-portal.atlascopco.group as the canonical host. Use when the user says "배포해줘", "deploy viewer", or "publish Jarvis".
Initialize a Javis workflow or project context. Use when the user asks to start Javis, initialize Javis for the current repo, bootstrap Javis state, or prepare the project for later Javis story/review work.
Define, refine, or implement a Javis story workflow for the current repository. Use when the user asks to create a story, break down a requirement into a story, prepare acceptance criteria, or execute work for a named Javis story.
Jira/Confluence/Bitbucket/Boards/Sprints/Members data sync. Usage: /javis-sync all, /javis-sync issues, /javis-sync boards, /javis-sync sprints, /javis-sync members, /javis-sync confluence, /javis-sync bitbucket, /javis-sync status
Pulls latest data from Jira/Confluence to the local database and then deploys that data to the remote Javis server (10.182.252.32). Use when the user wants to update the remote server's database with current data.