Skip to main content

Scraut — Scrum Automation

What is Scraut?

Scraut (Scrum Automation) is a fully automated Scrum system built on GitHub infrastructure. It replaces Scrum-management apps and reduces ceremony overhead by treating text files as the single source of truth and letting GitHub Actions + an LLM do the rest.

One sentence: Text files in — automation out.


The core idea

Traditional Scrum tools require you to:

  • Log into a separate platform every morning
  • Manually update ticket statuses
  • Copy-paste information between Slack, GitHub, and your PM tool
  • Run stand-up calls even when updates are predictable

Scraut flips this model. Your team edits simple Markdown files directly in GitHub. Every commit triggers the right workflow automatically — summaries are generated, Slack is notified, the board is updated, blockers are escalated.

Your team stays in GitHub. Everything else is handled.


Architecture overview

┌─────────────────────────────────────────────────────┐
│ Your GitHub Repo │
│ │
│ workspace/ ← Human-edited source of truth │
│ ├── sprint/001/ │
│ │ ├── standup/2026-05-24/alice.md ← Alice edits │
│ │ ├── retrospective/alice.md ← Alice edits │
│ │ └── meta.md ← SM edits │
│ ├── milestones/v2.0.md ← PM edits │
│ ├── team/capacity.md ← SM edits │
│ └── okr/okr.md ← PO edits │
│ │
│ .scraut/ ← Bot-generated output │
│ ├── sprint/001/standup/summary/ ← LLM writes │
│ ├── sprint/001/review/ ← LLM writes │
│ ├── insights/ ← LLM writes │
│ └── suggestions/active/ ← LLM writes │
└─────────────────────────────────────────────────────┘
│ git push triggers

┌─────────────────────────────────────────────────────┐
│ GitHub Actions Workflows │
│ │
│ daily-standup.yml → summarise standups → Slack │
│ sprint-planning.yml → generate sprint plan PR │
│ suggestion-detect → detect process patterns │
│ visibility-engine → sync GitHub Projects board │
│ portal-publish.yml → deploy GitHub Pages dashboard │
└─────────────────────────────────────────────────────┘

Key features

FeatureHow it startsWhat it does
Morning Notifications⏱️ 7:55 AM weekdaysDMs each team member their standup link
Daily Standup⚡ Push to standup fileBot summarises all standups and posts to Slack
Issue Triage⚡ New issue openedAuto-labels type and priority with LLM
PR Enrichment⚡ PR openedFills PR description with acceptance criteria
Definition of Done⚡ Issue closedChecks DoD criteria against linked PRs
Backlog Grooming⏱️ Every WednesdayAI prioritises unlabelled issues mid-sprint
Velocity Tracking⚡ After sprint reviewCalculates and tracks story point velocity
Visibility Portal⏱️ Every 30 minutesGitHub Pages dashboard synced from text files
Milestone Planning⚡ Push to milestone fileDecomposes milestones; generates health forecasts
Incident to Backlog⚡ Push action-items.mdConverts incident action items to GitHub issues
Weekly Digest⏱️ Monday 8:00 AMSends stakeholder summary to Slack + email
Suggestions System⚡ After sprint reviewDetects recurring pain points; proposes improvements
Repo Sync⏱️ Daily 8:00 AMPulls code activity from connected repos
Sprint Planning🖱️ SM triggers manuallyAI generates planning PR from backlog + capacity
Sprint Review🖱️ SM triggers manuallyReview document from closed issues
Retrospective🖱️ SM triggers manuallyAI synthesises per-person retros into team themes
Agent Mode⏱️ Every 4 hoursFully autonomous AI agents that implement tasks

Key: ⏱️ Scheduled  ·  ⚡ Triggered by a GitHub event  ·  🖱️ SM triggers from Actions tab


Who is Scraut for?

  • Small to medium engineering teams (2–20 developers) using GitHub
  • Teams that want Scrum ceremonies without ceremony overhead
  • Teams that dislike switching between GitHub and a separate PM tool
  • Teams open to using an LLM as their "Scrum Master assistant"

File zones

Scraut enforces a strict separation between human-written and bot-written content:

ZonePathWho writesRule
Human inputworkspace/Team membersNever overwritten by bot
Agent inputworkspace/sprint/NN/standup/DATE/agent-*.mdAI agentsSame format as humans
Bot-generated.scraut/GitHub Actions<!-- BOT-GENERATED --> header

This means you can always trust what's in workspace/ — Scraut never modifies files a human has written.


Ready to start?

New to Scrum? Read the Scrum Primer → first — it covers ceremonies, artifacts, roles, and the hard rules that make Scrum work.

Already know Scrum? Head straight to Prerequisites →