Aggregate sprint session work into experiments-results.md reports.
npx skills add https://github.com/vitalwarley/hyprdots --skill report-vitalwarley
Please help me install this Agent Skill. Skill: report Source: https://github.com/vitalwarley/hyprdots/tree/main/claude-global/skills/report Command: npx skills add https://github.com/vitalwarley/hyprdots --skill report-vitalwarley
Keeps the running sprint experiments report current by incrementally aggregating session work, results, and audit findings so reports never lag behind ongoing analysis.
Aggregate the current conversation session into the running sprint report and commit the updated experiments-results.md.
High-intent search queries and answers about installing and using this skill.
To aggregate git commits into a weekly sprint report, you append chronology entries, update Status vs Plan tables, and add analysis sections into an experiments-results.md file, then commit the updated documentation to your repository.
Yes, you can update a sprint status table without overwriting verified content by using verification-aware publishing, which only marks items done when backing artifacts and audit Safe Claim sections exist before appending new chronology entries.
To initialize a new weekly sprint experiments report, you use the --init operation mode within a git-accessible repository containing the report/sprints/week-NN directory structure to generate the baseline experiments-results.md file.
The best way to fill gaps in chronological sprint documentation is to run a full gap-fill operation using the --all mode, which aggregates all missing session work, result JSONs, and audit notes into the running report.
Yes, you need a git-accessible repository with a report/sprints/week-NN directory structure and backing artifacts for verified status updates to automate sprint reporting updates properly.
Sprint experiment status updates are not marked as done because verification-aware publishing requires both backing artifacts and audit Safe Claim sections to exist before committing the updated status table to the repository.
atlassianGenerate status reports from Jira issues and publish them to Confluence.
pipemind-comDesign 1–3 experiments to verify or falsify a hypothesis file.
scomofoGenerate categorized release notes from git history for internal and player audiences.
mkalhitti-cloudAutomate documentation updates across changelogs, milestones, and READMEs.