BenMakesGames

Research and pressure-test a feature idea before it becomes a ticket — feasibility, implementation options, gotchas, and the hidden assumptions/contradictions behind the request. Discuss with the user until you both agree on the shape, then offer to hand off to /create-ticket. Never writes code or tickets; never invokes /create-ticket itself.

Implement a ticket from docs/tickets/

Holistic review of code architecture, identifying tech debt and ergonomic improvements

Create detailed implementation ticket(s) from a feature description

Holistic review of documentation, skills, and process health

Lead a collaborative character design session for a datable character

Lead a collaborative beat sheet session for one Relationship Level (or Last Date) of a datable character

Lead a collaborative dialogue-writing session for one Relationship Level (or Last Date) of a datable character, producing actual lines and stage directions from an existing beat sheet

Create detailed implementation ticket(s) from a feature description

Implement a ticket from docs/tickets/

Implement a ticket from docs/tickets/, following the full workflow from reading through implementation to documentation updates

Create detailed implementation ticket(s) from a feature description