// 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.
| name | javis-story |
| description | 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. |
Use this skill when the user is working on a Javis story.
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.
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
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.