ringmaster

The different roles on development teams exist for a reason. Humans need to look at code from different points of view. LLMS are no different.

Ringmaster leverages 41 of software development experience by structuring your AI assistant to act like a whole development team.

This hygiene ends up making your coding agents smarter, because LLMs "forget".

What it does

• Role-based routing coordinates tasks between Architect, Implementer, Reviewer, and Tester roles based on specific cognitive points of view.
• Surgical file editing prevents accidental regressions by enforcing a strict re-read and partial-edit discipline.
• Hygiene enforcement automates documentation updates and commit standards during development checkpoints before the LLM forgets.
• Workload management implements wait-credit guards for long-running jobs, categorized by duration from instant to overnight. This prevents token burn for long running tasks from the LLM reloading the context for each check.
• Planning-first approach requires a plan mode activation before any wide or sensitive edits to the codebase.

How it works

1. Initialize the session by loading the reference pack and confirming the active project rules.
2. Route the specific task to the appropriate role (Architect for planning, Tester for verification, etc.) after reading core values.
3. Execute edits using strict file discipline, starting with plan mode for significant changes.
4. Audit the changes through the Reviewer role and apply hygiene checkpoints for documentation and commits.

Frameworks & tools

This skill is designed for use with Claude Code, Cursor, or similar agentic IDEs. It relies on a local references/ directory containing the core Markdown rulebooks and integrates with git for worktree management.

Why this beats prompting it yourself

I've been coding for 43 years now, learned stuff. Found problems with AI driven coding, Fixed them based on my experience.

Use cases

• Bootstrap a new project with strict architectural and testing standards.
• Perform sensitive refactoring across multiple files without breaking the build.
• Enforce consistent commit messages and documentation updates across a team.

Known limitations

Requires a specific reference directory structure to function. The wait-credit guard requires manual time tracking if not used within a supported plugin environment.