224Sand
UserMCP server that governs an AI coding agent through a delivery lifecycle: each named role must produce a machine-checkable artifact before it may sign off, and the whole build record survives on disk across sessions.
Categories
Indexed Skills (3)
role-council
Assigns and enforces delivery roles for a piece of work — picks the methodology first (Scrum, Kanban, SAFe, Waterfall/stage-gate, CI/CD), derives the role set that methodology actually implies, then names a role before each substantive action and states what a decision requires. Also runs multi-role reviews over a git repository's real history, producing grounded, citation-backed commentary per role on real defects, decisions, commits or PRs — never invented opinions. Use whenever the user asks to work under named roles, wants role/duty/responsibility assignment for a session or project, mentions a methodology (agile, scrum, kanban, SAFe, waterfall, CI/CD) and who should do what, wants a cross-functional or "council" review of a PR/feature/decision/design, wants a project retrospective from multiple perspectives, or asks how different roles (dev/QA/PM/BA/TPM/security) would react to something. Works on any project — not tied to a fixed role list or one codebase.
role-council
Assigns and enforces delivery roles for a piece of work — picks the methodology first (Scrum, Kanban, SAFe, Waterfall/stage-gate, CI/CD), derives the role set that methodology actually implies, then names a role before each substantive action and states what a decision requires. Also runs multi-role reviews over a git repository's real history, producing grounded, citation-backed commentary per role on real defects, decisions, commits or PRs — never invented opinions. Use whenever the user asks to work under named roles, wants role/duty/responsibility assignment for a session or project, mentions a methodology (agile, scrum, kanban, SAFe, waterfall, CI/CD) and who should do what, wants a cross-functional or "council" review of a PR/feature/decision/design, wants a project retrospective from multiple perspectives, or asks how different roles (dev/QA/PM/BA/TPM/security) would react to something. Works on any project — not tied to a fixed role list or one codebase.
charter
Run a build under a governed role charter. Use whenever starting or continuing a project with charter installed - assigns roles by methodology, requires each role to produce a checkable artifact before it may sign off, and keep calling charter_next until the build reports done or escalated.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.