Autoscrum

Use this skill to make a repo's development loop explicit, traceable, and provable through docs: idea capture, sprint planning, implementation, validation, changelog and release contracts, PR or review, merge, release prep, publish.

Mode Dispatch

Classify the request first, then route:

• Establish: the repo lacks the workflow or doc hierarchy, or the user asks to set up/standardize it. Follow the Planning-First Gate and First Pass below, then install adapted templates.
• Operate: the workflow exists and the user asks to run a step of it (capture an idea, plan a sprint, log work, update the changelog or a release contract, prep a release). Read references/operations.md and run only that step.
• Repair/Audit: the workflow exists but has drifted (stale docs, missing entries, version mismatches) or the user asks for a health check. Run the drift audit in references/operations.md and propose fixes before applying them.

Document Hierarchy

The workflow is anchored to a canonical doc hierarchy. Each file has a role and a boundary: