← Headcount: TechnologyCONTENT HISTORY
WHAT CHANGED
added
Update to Headcount: Technology
Snapshot Oct 27, 2026 · 01:05 UTC · version 1.0.1
Package or technical metadata updated
Package or technical metadata updated
Observed in package metadata. These changes alone do not establish a new customer-facing feature.
Save Headcount: Technology and check future changes in Following.
Up to 10 plugins free · no card required.
All fields and original values.
Is v2 template
Before
Oct 24, 2026 · 13:55 UTC
Not present
After
Oct 27, 2026 · 01:05 UTC
false
Compare saved observations
Download comparison JSONFull technical diff · 1 changed fields
added /is_v2_template
BEFORE
Field was absent
AFTER
false
Full snapshot data
{
"canonical_app_id": null,
"connector_id": null,
"created_at": "2026-10-09T02:16:28.795806Z",
"discoverability": "LISTED",
"id": "plugins_6ac84bac80b081918c305a1574fbd186",
"is_template": false,
"is_template_instance": false,
"is_v2_template": false,
"name": "technology",
"release": {
"app_ids": [],
"app_manifest": null,
"app_templates": [],
"description": "Architecture, engineering delivery, development discipline, debugging, review, and AI and automation systems.",
"display_name": "Headcount: Technology",
"id": "pluginrel_8f3227de88388191ab4e3300f4acd362",
"interface": {
"brand_color": null,
"capabilities": [],
"category": "Productivity",
"composer_icon_dark_url": null,
"composer_icon_url": "https://files.openai.com/content?id=file_0000000058e481f59ad93af87651172d",
"default_prompt": "Review this architecture proposal and explain its risks and alternatives.",
"default_prompts": [
"Review this architecture proposal and explain its risks and alternatives.",
"Turn these requirements into a practical implementation plan.",
"Help me debug this failure and decide what evidence to collect next."
],
"developer_name": "Chris Brock",
"logo_url": "https://files.openai.com/content?id=file_0000000035b481f5a20cec559b069e66",
"logo_url_dark": null,
"long_description": "Plan software projects, review architecture and APIs, debug failures, and improve engineering workflows. Headcount Technology includes nineteen reusable skills covering implementation planning, code review, testing, development practices, and AI automation design. Use it to turn requirements into an actionable plan or identify what evidence to collect when a system fails. Works with information you provide and tools available in ChatGPT. Part of the Headcount department skill collection, created by Chris Brock.",
"plugin_category_id": "productivity",
"privacy_policy_url": "https://chrisbrockllc.com/plugins/privacy",
"screenshot_urls": [],
"short_description": "Your technology department",
"terms_of_service_url": "https://chrisbrockllc.com/plugins/terms",
"website_url": "https://chrisbrockllc.com/plugins/headcount"
},
"keywords": [],
"mcp_servers": [],
"onboarding_skill_name": null,
"requires_local_executor": false,
"skills": [
{
"description": "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.",
"interface": {
"brand_color": null,
"default_prompt": null,
"display_name": "ai-workflow-architect",
"icon_large_url": null,
"icon_small_url": null,
"iconography": "hierarchy",
"short_description": "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."
},
"name": "ai-workflow-architect",
"plugin_release_skill_id": "pluginrsk_6ac84ca1c01c81918c427adbb210bd17"
},
{
"description": "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.",
"interface": {
"brand_color": null,
"default_prompt": null,
"display_name": "api-design",
"icon_large_url": null,
"icon_small_url": null,
"iconography": "code",
"short_description": "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."
},
"name": "api-design",
"plugin_release_skill_id": "pluginrsk_6ac84ca1515c8191b643d9a090c0dd1d"
},
{
"description": "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.",
"interface": {
"brand_color": null,
"default_prompt": null,
"display_name": "branch-and-worktree-workflow",
"icon_large_url": null,
"icon_small_url": null,
"iconography": "hierarchy",
"short_description": "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."
},
"name": "branch-and-worktree-workflow",
"plugin_release_skill_id": "pluginrsk_6ac84c9f40cc8191bce0c87efb34a549"
},
{
"description": "Owns architecture, engineering delivery, infrastructure, data platform, and internal systems. Use this for build-versus-buy calls, technology selection, architectural direction, engineering capacity and delivery risk, technical debt tradeoffs, platform and tooling decisions, or when a technical choice has business consequences that need stating in business terms. Also use to judge whether a technical plan is sound before it is committed to.",
"interface": {
"brand_color": null,
"default_prompt": null,
"display_name": "chief-technology-officer",
"icon_large_url": null,
"icon_small_url": null,
"iconography": "code",
"short_description": "Owns architecture, engineering delivery, infrastructure, data platform, and internal systems. Use this for build-versus-buy calls, technology selection, architectural direction, engineering capacity and delivery risk, technical debt tradeoffs, platform and tooling decisions, or when a technical choice has business consequences that need stating in business terms. Also use to judge whether a technical plan is sound before it is committed to."
},
"name": "chief-technology-officer",
"plugin_release_skill_id": "pluginrsk_6ac84ca08df081919f193469770926a3"
},
{
"description": "Designs and runs cloud infrastructure — environments, infrastructure as code, networking and isolation, scaling, and cost. Use this to design a cloud environment, control infrastructure spend, set up environment separation, plan for scale or region failure, or review infrastructure someone configured by hand.",
"interface": {
"brand_color": null,
"default_prompt": null,
"display_name": "cloud-infrastructure",
"icon_large_url": null,
"icon_small_url": null,
"iconography": "hierarchy",
"short_description": "Designs and runs cloud infrastructure — environments, infrastructure as code, networking and isolation, scaling, and cost. Use this to design a cloud environment, control infrastructure spend, set up environment separation, plan for scale or region failure, or review infrastructure someone configured by hand."
},
"name": "cloud-infrastructure",
"plugin_release_skill_id": "pluginrsk_6ac84ca1a3b881918d2ff124d56b5cac"
},
{
"description": "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.",
"interface": {
"brand_color": null,
"default_prompt": null,
"display_name": "code-review",
"icon_large_url": null,
"icon_small_url": null,
"iconography": "code",
"short_description": "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."
},
"name": "code-review",
"plugin_release_skill_id": "pluginrsk_6ac84c9e68348191bae496968ec3f254"
},
{
"description": "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.",
"interface": {
"brand_color": null,
"default_prompt": null,
"display_name": "completion-verification",
"icon_large_url": null,
"icon_small_url": null,
"iconography": "radar",
"short_description": "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."
},
"name": "completion-verification",
"plugin_release_skill_id": "pluginrsk_6ac84c9eba4c8191bf0454c0da10af54"
},
{
"description": "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.",
"interface": {
"brand_color": null,
"default_prompt": null,
"display_name": "data-migration",
"icon_large_url": null,
"icon_small_url": null,
"iconography": "hierarchy",
"short_description": "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."
},
"name": "data-migration",
"plugin_release_skill_id": "pluginrsk_6ac84c9e6af081918ee5d637886f7d37"
},
{
"description": "Turns a spec or requirement into a written plan a separate session or agent can execute, then drives that plan through review checkpoints. Use this before touching code on any multi-step task, when work needs handing to someone else, when a task keeps sprawling mid-implementation, or when a plan exists and needs executing in order with verification between steps.",
"interface": {
"brand_color": null,
"default_prompt": null,
"display_name": "implementation-planning",
"icon_large_url": null,
"icon_small_url": null,
"iconography": "hierarchy",
"short_description": "Turns a spec or requirement into a written plan a separate session or agent can execute, then drives that plan through review checkpoints. Use this before touching code on any multi-step task, when work needs handing to someone else, when a task keeps sprawling mid-implementation, or when a plan exists and needs executing in order with verification between steps."
},
"name": "implementation-planning",
"plugin_release_skill_id": "pluginrsk_6ac84ca0ed888191a2fc1537f56db6f0"
},
{
"description": "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.",
"interface": {
"brand_color": null,
"default_prompt": null,
"display_name": "observability-and-reliability",
"icon_large_url": null,
"icon_small_url": null,
"iconography": "radar",
"short_description": "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."
},
"name": "observability-and-reliability",
"plugin_release_skill_id": "pluginrsk_6ac84ca0de188191adbb8b54a139b0af"
},
{
"description": "Splits work across multiple agents or sessions running at once, keeping their surfaces disjoint so results merge cleanly. Use this when facing several independent tasks with no shared state, when a plan has parallelizable steps, when a broad search or audit would be faster fanned out, or when deciding whether work can safely be split at all.",
"interface": {
"brand_color": null,
"default_prompt": null,
"display_name": "parallel-agent-delivery",
"icon_large_url": null,
"icon_small_url": null,
"iconography": "hierarchy",
"short_description": "Splits work across multiple agents or sessions running at once, keeping their surfaces disjoint so results merge cleanly. Use this when facing several independent tasks with no shared state, when a plan has parallelizable steps, when a broad search or audit would be faster fanned out, or when deciding whether work can safely be split at all."
},
"name": "parallel-agent-delivery",
"plugin_release_skill_id": "pluginrsk_6ac84ca279408191b21784e23219b5b3"
},
{
"description": "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.",
"interface": {
"brand_color": null,
"default_prompt": null,
"display_name": "prompt-optimizer",
"icon_large_url": null,
"icon_small_url": null,
"iconography": "code",
"short_description": "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."
},
"name": "prompt-optimizer",
"plugin_release_skill_id": "pluginrsk_6ac84c9f883c819199c0bc6e48bbe68f"
},
{
"description": "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.",
"interface": {
"brand_color": null,
"default_prompt": null,
"display_name": "release-and-deployment",
"icon_large_url": null,
"icon_small_url": null,
"iconography": "bolt",
"short_description": "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."
},
"name": "release-and-deployment",
"plugin_release_skill_id": "pluginrsk_6ac84ca02c8881918bcb39b4a05f8bb3"
},
{
"description": "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.",
"interface": {
"brand_color": null,
"default_prompt": null,
"display_name": "skill-authoring",
"icon_large_url": null,
"icon_small_url": null,
"iconography": "code",
"short_description": "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."
},
"name": "skill-authoring",
"plugin_release_skill_id": "pluginrsk_6ac84ca224308191914578136e07c829"
},
{
"description": "Designs system structure and makes architectural decisions defensible — boundaries, coupling, trade-offs, and recording why. Use this to design a new system or major component, choose between architectural options, review an existing design, decide where a boundary belongs, or document an architectural decision so it survives the people who made it.",
"interface": {
"brand_color": null,
"default_prompt": null,
"display_name": "solution-architecture",
"icon_large_url": null,
"icon_small_url": null,
"iconography": "hierarchy",
"short_description": "Designs system structure and makes architectural decisions defensible — boundaries, coupling, trade-offs, and recording why. Use this to design a new system or major component, choose between architectural options, review an existing design, decide where a boundary belongs, or document an architectural decision so it survives the people who made it."
},
"name": "solution-architecture",
"plugin_release_skill_id": "pluginrsk_6ac84ca0040081918c4dd31923e9063d"
},
{
"description": "Explores the problem and the range of possible approaches before any code is written — clarifying what is actually being asked, surfacing options with their tradeoffs, and converging on one. Use this at the start of any feature, component, or behavior change, when a request is ambiguous, when the first idea is the only idea on the table, or when a design decision needs pressure-testing before commitment.",
"interface": {
"brand_color": null,
"default_prompt": null,
"display_name": "solution-exploration",
"icon_large_url": null,
"icon_small_url": null,
"iconography": "hierarchy",
"short_description": "Explores the problem and the range of possible approaches before any code is written — clarifying what is actually being asked, surfacing options with their tradeoffs, and converging on one. Use this at the start of any feature, component, or behavior change, when a request is ambiguous, when the first idea is the only idea on the table, or when a design decision needs pressure-testing before commitment."
},
"name": "solution-exploration",
"plugin_release_skill_id": "pluginrsk_6ac84c9e5f648191ab21c93f047da49d"
},
{
"description": "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.",
"interface": {
"brand_color": null,
"default_prompt": null,
"display_name": "systematic-debugging",
"icon_large_url": null,
"icon_small_url": null,
"iconography": "code",
"short_description": "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."
},
"name": "systematic-debugging",
"plugin_release_skill_id": "pluginrsk_6ac84c9f43888191855950a73b506419"
},
{
"description": "Makes technical debt visible and decidable — distinguishing real debt from mess, quantifying its cost, and arguing for remediation in business terms. Use this to assess and prioritize debt, decide whether to fix or live with something, justify remediation work to non-engineers, or plan a migration off a system nobody wants to touch.",
"interface": {
"brand_color": null,
"default_prompt": null,
"display_name": "technical-debt-management",
"icon_large_url": null,
"icon_small_url": null,
"iconography": "chart",
"short_description": "Makes technical debt visible and decidable — distinguishing real debt from mess, quantifying its cost, and arguing for remediation in business terms. Use this to assess and prioritize debt, decide whether to fix or live with something, justify remediation work to non-engineers, or plan a migration off a system nobody wants to touch."
},
"name": "technical-debt-management",
"plugin_release_skill_id": "pluginrsk_6ac84c9f629c8191be7211e3c237af28"
},
{
"description": "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.",
"interface": {
"brand_color": null,
"default_prompt": null,
"display_name": "test-driven-development",
"icon_large_url": null,
"icon_small_url": null,
"iconography": "code",
"short_description": "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."
},
"name": "test-driven-development",
"plugin_release_skill_id": "pluginrsk_6ac84ca06a4c81918e7b8ba96accdb78"
}
],
"version": "1.0.1"
},
"scope": "GLOBAL",
"share_url": "https://chatgpt.com/plugins/plugins_6ac84bac80b081918c305a1574fbd186?open_in_app",
"status": "ENABLED"
}SHA-256 of public snapshot: 13c4ed6cbd59318b048a4c3bb2bf6dfd9be46923211f25784b9469d4dc4d0ef6