730 reviewed prompts.
Writes a well-argued literary analysis essay with a clear thesis, close reading, engagement with critical approaches, a counterargument, and citations. Use for model essays, study guides, or developing your own argument.
Diagnoses how a team currently plans and delivers work and builds a phased plan to adopt agile practices that fit, with metrics and risks. Use when starting, resetting, or rescuing an agile rollout.
Extracts the structure and key points of a technical or scientific text into a clean outline you can write or study from. Use it to summarise papers, reports or chapters.
Builds the strongest fair version of the view you disagree with, tests it against your own position, and proposes a balanced synthesis. Use when forming an opinion on a debated topic or preparing for a discussion.
Explains any named algorithm in plain language with the main idea, a worked example, cost and common pitfalls, matched to your experience. Use it when you are learning or need to explain one to a teammate.
Compares an old and new API specification and writes a front-end focused change summary with breaking changes, new fields and migration steps. Use when a backend team ships a new spec version.
Turns rough testing notes into clear, reproducible bug reports with steps, expected and actual results, severity and suggested checks. Use it after a test session so developers can act without follow-up.
Splits a list of players into fair teams using skill ratings, fixed roles and preferences, then explains the balance. Use it for weekly sports games, classroom groups, game nights or workshop teams.
Runs a structured interview that surfaces gaps and trade-offs in a draft spec, then writes the finished specification. Use it when a rough spec needs to become something others can build from.
Converts a task you repeat often into a well-scoped skill: a name, a 'Use when' description that triggers reliably, step-by-step instructions, output shape, and test requests. Use it when building a team skill library.
Plans the smallest throwaway prototype, logic or visual, that settles one open design question, with cases to try and how to judge the result. Use before committing to a design.
Finds the weak spots in a prompt your team reuses, builds a small set of test inputs with pass checks, and proposes a minimal revision. Use when a saved prompt gives inconsistent results.
