Manages a file-based sprint board by reading, moving, and creating Markdown task files.
npx skills add https://github.com/gmolike/Claude-Template --skill scrum-gmolike
Please help me install this Agent Skill. Skill: scrum Source: https://github.com/gmolike/Claude-Template/tree/main/template-orchestrator/.claude/skills/scrum Command: npx skills add https://github.com/gmolike/Claude-Template --skill scrum-gmolike
.scrum/ directory, so task status, priorities, and assignments stay versioned alongside the code. ## Core Features & Use Cases - Board Overview: Reads all task files across backlog, in-progress, review, and done folders and renders a status table with priorities, assignees, and linked GitHub issues. - Task Lifecycle Management: Moves tasks between status folders, updates the YAML frontmatter, and verifies acceptance criteria before marking tasks done. - Task Creation: Generates new task files with sequential FEAT-XXX IDs, structured frontmatter, descriptions, and acceptance criteria. - Use Case: A developer starts the day by asking for the current sprint status, sees three tasks in progress and one blocked, then creates a new high-priority bugfix task directly in the backlog without leaving the editor. ## Quick Start Ask the assistant to show the current sprint board status from the .scrum directory.High-intent search queries and answers about installing and using this skill.
Store tasks as Markdown files with YAML frontmatter in status-based folders like backlog, in-progress, review, and done. This Skill reads those files, renders a board overview, and moves tasks between folders as work progresses.
Run the create command with a task title. The Skill assigns the next sequential FEAT-XXX ID, prompts for priority and acceptance criteria, and writes a structured Markdown file into the backlog folder.
Yes, each task file includes a github_issues field in its YAML frontmatter. The board overview displays linked issue numbers next to each task, and the status summary reports on their state.
The Skill moves the file into the done folder, updates the status field in the frontmatter, and checks whether all acceptance criteria checkboxes are marked complete before finalizing the transition.
File-based boards lack real-time collaboration, notifications, and burndown charts found in dedicated tools. They work best for small teams already working in a shared repository who want tasks versioned with code.
Thomas-FitzInitialize a project feature directory with Auto-Scrum subfolders and configuration.
alessioroberto82Audit GitHub pull requests for bugs and security vulnerabilities.
coreyhulenAutomate GitHub issue tracking, project board synchronization, and sprint planning.
aydinsenturkkCollect project status from Markdown files and GitHub issues into daily standup reports.