Finds the root cause of a bug, test failure, or unexpected behavior before proposing any fix. Use this whenever something is broken and the cause is not yet proven — a failing test, a production error, intermittent behavior, or a symptom that appeared after a change. Also use when a fix has been attempted and did not work, or when the same bug keeps coming back.
The English summary is being prepared. Showing the original description.
cbrock84/headcount☆ 2.1KUpdated Oct 19, 2026
Designs interfaces that survive their consumers — resource modeling, errors, versioning, pagination, and compatibility. Use this to design a new API, review one before it ships, decide how to version or deprecate, fix an interface consumers keep misusing, or work out whether a change is breaking.
The English summary is being prepared. Showing the original description.
cbrock84/headcount☆ 2.1KUpdated Oct 19, 2026
Writes and revises agent skills so they trigger at the right moments and give usable instruction when they do. Use this when creating a new skill, editing an existing one, diagnosing a skill that fires too often or never fires, or reviewing a set of skills for overlap. Also use before adding to a skill library, to check the capability is not already covered.
The English summary is being prepared. Showing the original description.
cbrock84/headcount☆ 2.1KUpdated Oct 19, 2026
Keeps production assets available — ranking equipment by consequence of failure, setting preventive and predictive intervals, sizing spares, and moving a plant off reactive maintenance. Use this to build or fix a maintenance program, decide what to put on a PM schedule, diagnose repeat failures on one asset, justify spares inventory, or work out why a plant that maintains everything still has unplanned downtime.
The English summary is being prepared. Showing the original description.
cbrock84/headcount☆ 2.1KUpdated Oct 19, 2026
Makes systems debuggable and reliably operable — instrumentation, alerting that is worth waking for, service objectives, and learning from failure. Use this to instrument a service, fix alerting that is ignored, set error budgets or reliability targets, prepare for on-call, or run a blameless post-incident review.
The English summary is being prepared. Showing the original description.
cbrock84/headcount☆ 2.1KUpdated Oct 19, 2026
Judges whether material for children under six is developmentally plausible — what is typical at each age, why pre-K is not a thinner kindergarten, and which frameworks apply where Common Core does not. Use this to design or review pre-K material, decide whether a task is reasonable for an age, choose the right framework for a pre-K alignment claim, or push back on material that pushes school-age expectations downward.
The English summary is being prepared. Showing the original description.
cbrock84/headcount☆ 2.1KUpdated Oct 19, 2026
Runs the loop from discovering a weakness to confirming it is fixed — scanning, triage, prioritization by real exploitability, remediation tracking, and patch policy. Use this to stand up or fix a vulnerability program, triage scanner output, decide what to fix first, set patch SLAs, handle a disclosure from an outside researcher, or report posture to leadership.
The English summary is being prepared. Showing the original description.
cbrock84/headcount☆ 2.1KUpdated Oct 19, 2026
Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting for review.
The English summary is being prepared. Showing the original description.
cbrock84/headcount☆ 2.1KUpdated Oct 19, 2026
Identifies what could go wrong in a system before it is built or changed — the assets worth attacking, the entry points, the trust boundaries, and the controls that actually address the realistic threats. Use this when designing a feature or system, when a change touches authentication, data handling, payments, or external input, before a security review, or when deciding which security work is worth doing at all.
The English summary is being prepared. Showing the original description.
cbrock84/headcount☆ 2.1KUpdated Oct 19, 2026
Designs AI systems, automations, and agent workflows for a business — identifying which manual work is worth automating, how to structure the system, which tools fit, and what could go wrong. Use this to automate part of an operation, design an agent or MCP workflow, reduce repetitive manual work, connect tools into a system, decide which automation to build first, or audit an automation that is not delivering.
The English summary is being prepared. Showing the original description.
cbrock84/headcount☆ 2.1KUpdated Oct 19, 2026
Builds questions and assessments that measure what they claim — matching item type to the thing being assessed, writing distractors that diagnose, and telling a question that measures learning from one that measures reading speed or test-taking. Use this to write or review assessment items, design a unit check or diagnostic, work out why scores do not match classroom performance, or decide how much evidence a claim about mastery actually needs.
The English summary is being prepared. Showing the original description.
cbrock84/headcount☆ 2.1KUpdated Oct 19, 2026
Drives implementation by writing a failing test first, then the smallest code that passes it. Use this before writing implementation code for any feature or bugfix, when a bug needs a regression test, when existing code is hard to change safely, or when someone asks whether a change is covered. Also use to decide what is worth testing and what is not.
The English summary is being prepared. Showing the original description.
cbrock84/headcount☆ 2.1KUpdated Oct 19, 2026
Conducts and responds to code review — reviewing a change for correctness, design, and risk, and evaluating review feedback received on your own work. Use this before merging, when asked to review a diff or pull request, when review feedback has arrived and needs acting on, or when feedback seems wrong and needs a reasoned response rather than compliance.
The English summary is being prepared. Showing the original description.
cbrock84/headcount☆ 2.1KUpdated Oct 19, 2026
Manages the relationship with a represented workforce — administering a collective agreement, handling grievances, understanding what supervisors may and may not say, and preparing for bargaining. Use this for a grievance or arbitration question, a work rule change in a represented unit, supervisor guidance during organizing, contract interpretation and past practice, or preparation for negotiations.
The English summary is being prepared. Showing the original description.
cbrock84/headcount☆ 2.1KUpdated Oct 19, 2026
Turns rough intent or a weak prompt into a reliable one — diagnosing why output is inconsistent, restructuring the instruction, and adapting it across models. Use this when a prompt is not producing what was wanted, when output varies run to run, when writing a prompt for a repeated task, when moving a prompt between models, or when someone describes what they want an AI to do and needs it written properly.
The English summary is being prepared. Showing the original description.
cbrock84/headcount☆ 2.1KUpdated Oct 19, 2026
Runs environment, health and safety on an operating site — hazard controls in order of effectiveness, incident recording and reporting obligations, and safety measurement that does not reward silence. Use this to build or audit a safety program, decide what controls a hazard actually needs, work out whether an injury is recordable or reportable, investigate an incident, or fix safety metrics that have stopped producing reports.
The English summary is being prepared. Showing the original description.
cbrock84/headcount☆ 2.1KUpdated Oct 19, 2026
Verifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was satisfied rather than approximated. Use this before saying something is done, fixed, or passing; before committing or opening a pull request; and whenever a claim of success has not been backed by command output.
The English summary is being prepared. Showing the original description.
cbrock84/headcount☆ 2.1KUpdated Oct 19, 2026
Ships changes safely and often — pipelines, deployment strategies, feature flags, rollback, and database changes. Use this to design a deployment pipeline, reduce release risk, roll out a risky change gradually, plan a schema migration, or work out why releases are infrequent and frightening.
The English summary is being prepared. Showing the original description.
cbrock84/headcount☆ 2.1KUpdated Oct 19, 2026
Designs worksheets, workbooks and practice material that actually teach — sequencing difficulty, managing cognitive load, writing instructions a child can follow unaided, and building answer keys that hold up. Use this to design or fix a worksheet or workbook, decide how much practice a skill needs, structure a page so it can be completed without an adult reading it aloud, or diagnose material that looks right and does not work.
The English summary is being prepared. Showing the original description.
cbrock84/headcount☆ 2.1KUpdated Oct 19, 2026
Moves data from one system to another without losing it or corrupting it — profiling the source before mapping, deciding between big-bang and parallel-run cutover, reconciling counts and values rather than assuming, handling the records that will not map cleanly, and planning a rollback that is actually executable. Use this to plan or run a migration, assess a migration plan someone else wrote, work out why a completed migration is producing wrong numbers, or size how long one will really take.
The English summary is being prepared. Showing the original description.
cbrock84/headcount☆ 2.1KUpdated Oct 19, 2026
Builds capability — skills gaps, career frameworks, training that transfers to the job, and internal mobility. Use this to design a career ladder, close a capability gap, decide whether to build or hire a skill, structure onboarding into a role, or work out why training keeps failing to change anything.
The English summary is being prepared. Showing the original description.
cbrock84/headcount☆ 2.1KUpdated Oct 19, 2026
Gets people to actually use what was delivered — stakeholder analysis, communication, training, resistance, and measuring adoption. Use this to plan a rollout, recover an implementation nobody is using, handle resistance to a change, sequence communications, or work out why a technically successful project changed nothing.
The English summary is being prepared. Showing the original description.
cbrock84/headcount☆ 2.1KUpdated Oct 19, 2026
Designs and improves referral, affiliate, and word-of-mouth programs — incentive structure, mechanics, timing, and fraud control. Use this to build a referral or affiliate program, diagnose one that is not producing, decide what incentive to offer, or judge whether referral is a realistic channel for a product.
The English summary is being prepared. Showing the original description.
cbrock84/headcount☆ 2.1KUpdated Oct 19, 2026
Designs and runs hiring — role definition, sourcing, interview loop design, structured evaluation, and the decision itself. Use this to open a role, write a job description or scorecard, design an interview process, prepare interview questions, calibrate a hiring decision, or diagnose why a hiring process produces poor outcomes.
The English summary is being prepared. Showing the original description.
cbrock84/headcount☆ 2.1KUpdated Oct 19, 2026