Diagnose a bug systematically instead of guessing — reproduce, isolate, form hypotheses, and test them to root cause. Use when debugging, chasing a defect, an intermittent failure, or 'why is this happening?'. Produces a structured diagnosis: a reliable repro, the narrowed-down location, ranked hypotheses with how to test each, and the root cause + fix once found.
日本語の概要は準備中です。原文の説明を表示しています。
Keep a running brag document of your accomplishments so reviews and promo cases write themselves. Use when asked to start or update a brag doc, log a win, track accomplishments, or prep evidence for a review/promotion. Produces a structured, dated accomplishment log — impact-first entries with metrics, scope, and the evidence link — grouped so it drops straight into a self-review or promo packet.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a folder of accumulated documents into one decision-ready brief — the skim-map pass over the pile, the extraction against the brief's actual questions, the conflict reconciliation when documents disagree, and the provenance trail back to sources. Use when asked read all this and tell me what matters, synthesize this folder for the new lead, turn these 20 docs into a brief, or what does all this material actually say. Produces the pile map, the question-driven extraction, the reconciled brief with per-claim sources, and the didn't-read honesty ledger.
日本語の概要は準備中です。原文の説明を表示しています。
Run the pre-flight checklist before an agent drives a browser — the untrusted-web-content threat (every page is attacker-controllable), the credential and session-cookie exposure, the action-confirmation gates for purchases and posts, and the sandboxing that limits the damage. Use when asked let my agent browse safely, is it safe to give the agent computer/browser use, guardrails before the agent uses my browser, or review my browser agent's setup. Produces the sandbox decision, the content-injection defenses, the action gates, and the credential-isolation rules.
日本語の概要は準備中です。原文の説明を表示しています。
Produce a structured budget variance analysis from actual vs budget figures. Use when asked to analyse budget variances, explain underspend or overspend, write a variance commentary, or investigate why actuals differ from plan. Produces a categorised variance table with root cause analysis and management commentary.
日本語の概要は準備中です。原文の説明を表示しています。
Run a family meeting to make a big care decision together. Use when asked help me run a family meeting about care, we need to decide together about mom's care, my siblings and I disagree about our parent, or facilitate a care decision. Produces an agenda and structure for the meeting, how to prepare (facts, options, everyone's input), ground rules to keep old family dynamics from derailing it, how to include the person being cared for, ways to work through disagreement toward a decision, and clear next steps with owners. Not legal, medical, or financial advice.
日本語の概要は準備中です。原文の説明を表示しています。
Organize care for an aging or ill family member across multiple helpers — the shared care map, a fair rotation with backup rules, the information binder, and family-meeting agendas that prevent the one-sibling-does-everything spiral. Use when asked help me coordinate care for my mom, my siblings and I need to split caregiving, organize care for a sick family member, or set up a care schedule. Produces the care map of needs and coverage, the rotation schedule with escalation rules, the binder outline, and the family meeting agenda.
日本語の概要は準備中です。原文の説明を表示しています。
Draft a firm, professional cease-and-desist letter to stop harassment, defamation, IP misuse, or unwanted contact — clear about what must stop and what happens if it doesn't. Use when asked to write a cease and desist, make someone stop [harassing/using my work/defaming me], or send a formal letter to stop. Produces a structured letter stating the conduct, why it's wrongful, the specific demand and deadline, and the consequence, plus guidance on delivery and records — flagging when the matter needs a real lawyer. Not legal advice.
日本語の概要は準備中です。原文の説明を表示しています。
Write changelogs and release notes readers actually benefit from — changes translated to so-whats, grouped by reader impact (breaking first, gifts second, plumbing last), with the upgrade path stated and the marketing kept honest. Use when asked write the release notes, turn this commit list into a changelog, announce this update to users, or why does nobody read our changelogs. Produces the impact-grouped changelog, the so-what translations, the breaking-changes block with migration steps, and the two-audience split when needed.
日本語の概要は準備中です。原文の説明を表示しています。
Write a human changelog from the REAL commit history — read the actual commit range via the GitHub connector, not a template. Use when asked to write the changelog for this release, what changed since the last tag, draft release notes from my commits, or summarise this range for users in Cowork. Reads commits/PRs between two refs via the GitHub connector, groups them into user-facing changes (features / fixes / breaking), translates commit-speak into human benefit, and produces a changelog artifact ready for the release.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a list of changes, commits, or PRs into clean release notes / a changelog entry. Use when asked to write release notes, a changelog, or a version announcement from raw changes. Produces a Keep-a-Changelog-style entry grouped by type (Added/Changed/Fixed/etc.), written for users — surfacing breaking changes and upgrade notes up top. To go straight from a raw git log use changelog-generator instead.
日本語の概要は準備中です。原文の説明を表示しています。
Get your attention back with a 30-day protocol that assumes you'll break it — a screen-time ledger without moralizing, friction engineering (what to delete, grayscale, where the phone sleeps), planned relapses, and honest replacement activities for the boredom that shows up on day 3. Use when someone says 'my screen time is 7 hours', 'I want a dumbphone', 'digital detox', 'I can't read books anymore', or 'my attention span is gone'. Produces the ledger, a personal friction plan, and the 30-day protocol with expected failure points.
日本語の概要は準備中です。原文の説明を表示しています。
Work out which applicant tracking system a job uses from its application link, and give the formatting rules that system parses safely. Use when asked which ATS does this company use, will my CV get through the ATS, is my CV ATS friendly, or how should I format for Workday, Greenhouse, Lever or Taleo. Produces the detected system with the evidence, a parsing-safe formatting checklist, the file type to upload, and a check of a supplied CV against the rules.
日本語の概要は準備中です。原文の説明を表示しています。
Compile the team's REAL updates into one async standup — pull what people posted in Slack (and moved in Notion/Linear), not a template for running standups. Use when asked to compile today's standup, pull the team's updates into one post, what did the team ship, or run async standup in Cowork. Reads a Slack channel and (optionally) the tracker via connectors, groups updates by person into shipped / in-progress / blocked, surfaces the blockers needing attention, and produces a standup-digest artifact ready to post back.
日本語の概要は準備中です。原文の説明を表示しています。
Extract and risk-rate hidden assumptions in a product brief or PRD. Use when asked to review a product brief for assumptions, audit a PRD for risks, find hidden assumptions, validate product plans, or run an assumption analysis. Produces a prioritised assumption map with confidence and impact scores, recommended validation methods, and critical assumption flags.
日本語の概要は準備中です。原文の説明を表示しています。
Extract every hidden assumption from a plan or document and put a price on each one — what it costs if wrong, what it costs to test. Use when about to commit to anything whose author says 'obviously' or whose spreadsheet has hardcoded cells: the bounty hunt makes the invisible load-bearing beliefs explicit and tells you which three to test this week. Produces the assumption ledger (priced and ranked), the cheapest test for each dangerous one, and the document's honest confidence statement.
日本語の概要は準備中です。原文の説明を表示しています。
Surface the hidden assumptions a plan or belief rests on, then test what happens when each one is wrong. Use when asked what am I assuming here, check my assumptions, what if I'm wrong about, or stress-test my thinking. Produces the unstated assumptions your conclusion depends on (ranked by how load-bearing they are), a flip of each to see which one breaking would change everything, and the cheapest way to check the riskiest ones — because the assumption you didn't know you were making is what sinks plans.
日本語の概要は準備中です。原文の説明を表示しています。
Write a specification section that a contractor can price accurately and a site can build from — performance stated, products defined, workmanship and tolerances given, and the coordination with the drawings made explicit. Use when asked to write a specification, spec a material or system, prepare an NBS-style section, or when a specification produced wildly different tender prices. Produces the scope and interface definition, the performance requirements, the product or system definition, execution and tolerance requirements, and the submittals and testing schedule.
日本語の概要は準備中です。原文の説明を表示しています。
Publish 'how to work with me' as a literal API spec — endpoints (what to ask me for and what you'll get back), rate limits (meeting and interrupt tolerance), error codes (what happens when you surprise me Friday 5pm), auth (how to earn trust), and a changelog. Use when onboarding to a new team, when a new manager or report arrives, for a team working-styles session, or 'write my README/user manual'. Produces a personal API spec that's genuinely funny and secretly the best onboarding doc on the team.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a client's wishes into an architectural brief that can actually be designed against — the accommodation schedule, the adjacencies, the budget reality, and the constraints named before they become change orders. Use when asked to write an architectural brief, prepare a project brief for a building, run a client briefing, or capture requirements for a new build or refurbishment. Produces the accommodation schedule with areas, the adjacency and circulation requirements, the site and statutory constraints, the budget and programme reality check, and the explicit exclusions.
日本語の概要は準備中です。原文の説明を表示しています。
Write an API versioning strategy document for a service or API platform. Use when asked to define versioning policy, plan API deprecation, classify breaking changes, or document version lifecycle. Produces a complete versioning strategy with breaking-change classification table, deprecation timeline, migration guide template, and client communication template.
日本語の概要は準備中です。原文の説明を表示しています。
Write a sincere, effective apology to a customer, group, or the public. Use when asked to write an apology, say sorry to a customer or community, make amends after a mistake, or respond to a complaint with an apology. Produces a genuine apology — acknowledgement, taking responsibility, empathy for the impact, the concrete fix and prevention, and an offer to make it right — in the right tone, without excuses or non-apologies.
日本語の概要は準備中です。原文の説明を表示しています。
Cut through the model soup to buy the right appliance — the features that actually matter for you, the ones that are marketing, and when to buy. Use when asked which [fridge/washer/dishwasher] should I buy, help me choose an appliance, what features do I need, or is this appliance worth it. Produces a needs-based feature shortlist (must-have vs nice-to-have vs marketing fluff), fit and capacity checks, reliability and running-cost considerations, warranty/extended-warranty guidance, and timing tips — flagging to verify current models, prices, and specs before buying.
日本語の概要は準備中です。原文の説明を表示しています。
Present a design to a client so they can make a decision rather than react to a picture — the brief restated, the moves explained against it, the options with their trade-offs, and a specific decision requested. Use when asked to present a design to a client, prepare a design review meeting, present concept options, or when a client keeps changing their mind after sign-off. Produces the presentation structure, the brief-to-design traceability, the options with honest trade-offs, the cost and programme position, and the decision record that makes sign-off stick.
日本語の概要は準備中です。原文の説明を表示しています。