tutum-pro
UserMeta-rules for running a software project, as a Claude Code plugin: decision records (ADR), open questions (OQ), phases with acceptance criteria, and verification discipline
Categories
Indexed Skills (7)
audit
Audit the architecture documentation for completeness and truthfulness — numbering defects, missing index entries, superseded records still claiming to be current, statuses that reality has overtaken. Use periodically and before any milestone.
bootstrap
Scaffold the architecture documentation set (decision records, open questions, phase register) in a project that does not have one yet. Use when starting a new project or introducing the archirules method into an existing one.
language
Switch a project's architecture documentation from one language to another, end to end - decision records, open questions, phase register, verification register, file names, cross-links and the CLAUDE.md fragment. Use when the working language of the team changes.
verification
Verification discipline — prove a new gate can fail, avoid measuring your own test artifacts, run suites twice. Use when adding a check, a test, or before reporting any measured result.
adr
Write, supersede or amend an architecture decision record (ADR). Use when an architectural decision has been made, reversed, or discovered to be undocumented.
oq
Register a new open question or resolve an existing one in the open-questions register. Use when a doubt has no answer yet, or when a decision closes one.
phases
Manage the phase register — open a phase with its acceptance criterion, or close one with evidence. Use before starting a work phase and when reporting it complete.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.