collisionengineers

Promote and release Pegasus through its authorised terminal route, or perform a promotion-only update without redeploying unchanged application code. Use for Pegasus production promotion, deployment, rollback, or release verification.

Autonomously clear a set of Kanmer tickets — target an area or a group (epic/horizon), and drive every eligible ticket through its profile's pipeline up to a specified point, orchestrating parallel subagents in conflict-free waves and respecting the document…

Author and link the repo's governing documents (PRD/FRD/ADR) under /docs/. Use to create or update a product/functional/architecture doc, to satisfy the "every ticket links or creates a governing doc" rule, or to lay down the /docs/ structure. DO NOT USE for…

Implement a Kanmer ticket — take it in its own git worktree and branch, work through its checklist with live progress notes, write the post-implementation report, and open the PR. Use when the user says "work on", "implement", "take" or "build" a ticket, or…

Groom and triage a Kanmer board by actually fixing it — dedupe near-duplicate tickets, fill in missing areas and profiles, split oversized tickets, archive dead ones, chase stale taken tickets, and repair off-board statuses. Use when the user says "groom the…

Plan a Kanmer ticket — turn its research and files documents into a concrete plan and an executable checklist. Use when the user says "plan", "design the approach for" or "break down" a ticket, or when a researched ticket needs its plan before implementation.…

Research a Kanmer ticket before it gets planned — dig into the codebase, record what you learned in the ticket's research/ folder, and survey what the change touches in files/. Use when the user says "research", "investigate", "dig into" or "scope out" a…

Review a Kanmer ticket's PR — write the review set to scratch, check the post-implementation report and the plan's Governing-docs section against the diff, turn feedback into blocking tickets, then merge and move the ticket to Verifying. Use when the user…

Current Box REST API reference for collisionspike archive integration, including server-side CCG authentication, folders, file requests, shared links, webhook signatures, retry behavior, and least-privilege scopes. Use when building or validating…

EVA Sentry API v1.2 reference for collisionspike, covering authentication, the eight endpoint families, the canonical twelve-field payload, image ordering, idempotency, and server-side submission. Use when changing EVA contracts,…

Distills operator drop-notes and sample emails/documents into new collisionspike tickets under the status-folder system (docs/tickets/backlog|blocked|next|now|verify|done/TKT-NNN folders with frontmatter, evidence/, changes.md, verification.md) and adds them…

Implements and closes collisionspike tickets (TKT-NNN) in the status-folder ticket system — reads the ticket spec/research/plan, verifies live facts against the registry, routes work by area, records changes.md and verification.md, and changes status with…

Orchestrates collisionspike ticket work by dispatching agents — routes a ticket's area to the right specialist (azure-integration-engineer, fluent-spa-designer, box-integration-architect, eva-sentry-integration) or the ticket-implementer fallback, enforces…

Creates and maintains docs/tickets/plans/PLAN-NNN plans that cluster related collisionspike tickets. Use for multi-ticket operator plans, plan lifecycle updates, bidirectional plan/ticket links, and closing plans when all member tickets are done.

UI/UX design intelligence. 67 styles, 96 palettes, 57 font pairings, 25 charts, 13 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize,…

Current Box REST API reference for collisionspike archive integration, including server-side CCG authentication, folders, file requests, shared links, webhook signatures, retry behavior, and least-privilege scopes. Use when building or validating…

Author and link the repo's governing documents (PRD/FRD/ADR) under /docs/. Use to create or update a product/functional/architecture doc, to satisfy the "every ticket links or creates a governing doc" rule, or to lay down the /docs/ structure. DO NOT USE for…

Independently review a Kanmer ticket's PR against its packet, plan, governing docs, current head SHA, checks, and review threads; write the versioned whole-file review attestation, disposition every finding, then merge only with authorization and move one…

Set up or reconcile Kanmer in a project — apply version steps, migrate an older board, refresh the AGENTS.md operating instructions, and ingest whatever the repo already records as work (GitHub issues, plan documents, or commit history). Re-run it after every…

Plan a Kanmer ticket — turn the inputs its live gates require into a concrete plan and executable checklist. Use when the user says "plan", "design the approach for" or "break down" a ticket. DO NOT USE FOR research itself (kanmer-research handles a required…

Research a Kanmer ticket before it gets planned — dig into the codebase, record what you learned in the ticket's research/ folder, and survey what the change touches in files/. Use when the user says "research", "investigate", "dig into" or "scope out" a…

Manage tickets on Kanmer, the file-based kanban shared live with a human's board GUI — orient on the board, create, update, link, order and archive tickets, and keep the board's conventions. Use whenever the user asks to add or update a ticket, manage the…

Autonomously clear one explicit Kanmer group (epic or horizon), preserving a durable, resumable run record on that group while driving eligible tickets through their profile pipelines up to a requested point. Use when the user says "clear HZN-003", "work…

Implement one Kanmer ticket from its read-only execution packet — take its recorded worktree and branch, work only the bounded checklist, write the post-implementation report, and open the PR. Use when the user says "work on", "implement", "take" or "build" a…

Manage tickets on Kanmer, the file-based kanban shared live with a human's board GUI — orient on the board, create, update, link, order and archive tickets, and keep the board's conventions. Use whenever the user asks to add or update a ticket, manage the…

Run a durable goal controller over a frozen roster — one ticket, one explicit Kanmer group, one area, an explicit ticket list, or the prepared board — keeping a resumable run record on the host group while driving each roster ticket through its profile…

Implement one Kanmer ticket from its read-only execution packet — take its recorded worktree and branch, work only the bounded checklist, write the post-implementation report, and open the PR. Use when the user says "work on", "implement", "take" or "build" a…

Plan a Kanmer ticket — turn the inputs its live gates require into a concrete plan and executable checklist. Use when the user says "plan", "design the approach for" or "break down" a ticket. DO NOT USE FOR research itself (kanmer-research handles a required…

Close out a verified Done ticket or an explicitly retired post-merge verification failure — finalize proof and traceability, clean its Git workspace, then release. For a batch, census the immutable roster and remove shared Git while its manifest remains…

Independently review a Kanmer ticket's PR against its packet, plan, governing docs, current head SHA, checks, and review threads; write the versioned whole-file review attestation, disposition every finding, then merge only with authorization and move one…

Verify a reviewed and merged Kanmer ticket at the exact GitHub merge SHA in a disposable detached worktree, write the versioned proof record with every attempt, and move Verifying→Done only for a truthful PASS. Use after kanmer-review has merged a PR and…

Groom and triage a Kanmer board by actually fixing it — dedupe near-duplicate tickets, fill in missing areas and profiles, split oversized tickets, archive dead ones, chase stale taken tickets, and repair off-board statuses. Use when the user says "groom the…

Collision Engineers house style and branded document generation. Use whenever a CE output needs the house visual layout, the house writing tone, or a branded document built. Modes: document-builder generates branded DOCX and PDF (letters, reports, fee notes,…

Shared reference for current UK collision-repair charges from the ABP Club rate book (2026 edition). Use whenever a skill needs labour rates, the repair-plan fee, ADAS calibration charges, EV/hybrid handling, alloy/alignment/air-con/recovery/storage…

Use for UK collision damage estimating work: standalone repair estimates, EVA/Audatex total-loss damage assessments, AZT paint costing, ABP charge review, and estimate challenge support. Modes: repair-estimate, eva-total-loss, paint-costing, charge-review.…

Use to draft Collision Engineers finance documents: fee-note, standard-audatex-invoice, website-invoice, and invoice-email-draft. Produces document drafts only; billing workflow, ledger, payment status, approvals, and chasing remain owned by finance/business.…

Shared reference library of vehicle-manufacturer (OEM) repair position statements - wheel and tyre reconditioning prohibitions, genuine-parts policies, and authoritative repair-procedure sources (erWin, ElsaPro, VIDA). Use whenever a repair estimate,…

Use when drafting a Collision Engineers rebuttal to a diminution-in-value claim (e.g. an EVA / Exclusive Vehicle Assessors diminution report) for an instructing solicitor. Produces a CPR Part 35-style rebuttal report in CE house style. Triggers on…

Use when generating an HS (Hackney Solutions) roadworthy certificate from an engineer's accident-damage report (PDF or docx). Extracts the required fields from the report and fills the roadworthy docx template. Triggers on "roadworthy", "roadworthy…

Determine the ABI salvage category (A / B / S / N) for a damaged vehicle using the ABI Code of Practice, with a reasoned justification and the regulatory notification obligations (MIAFTR, V5C/DVLA, Certificate of Destruction). Use when assessing whether a…

This skill should be used whenever the user asks to "use codex", "ask codex", "delegate to codex", "second opinion from codex/gpt", "have codex review", "run this in codex", "codex workflow", "let gpt implement", or wants OpenAI Codex involved in review,…

Get a read-only second opinion from Codex on a question, design, hypothesis, or diagnosis. Use for "/codex-bridge:consult <question>".

Run a Codex fan-out (review panel, adversarial verify, implement-then-verify) with the native runner, with no Claude agents in the loop. Use for "/codex-bridge:workflow <goal>".

Check that Codex is installed, authenticated, and reachable through app-server; list models, effort tiers, presets, and the shared server state. Use for "/codex-bridge:doctor" and when Codex runs fail.

Continue a previous Codex thread with a follow-up instruction. Use for "/codex-bridge:resume [thread-id|--last] <follow-up>".

Ask Codex to review local git changes (uncommitted, against a base branch, or a commit), optionally with a focus. Use for "/codex-bridge:review".

Hand a task to Codex with a preset (consult, plan, implement, research, quick) and report the envelope. Use for "/codex-bridge:run <task>".

Implement, fix, refactor, document, verify, and remediate one change in an onboarded Azure-oriented repository through a green pull request, with independent exact-head review for standard/high-risk work. Use for feature delivery, bug fixes, requested…

Convert an existing Azure-oriented repository to the Azure Workflow documentation, GitHub, planning, review, testing, and delivery standard without losing material truth. Use for initial adoption, brownfield documentation consolidation, huge feature-list…

Inspect and plan one change in an onboarded Azure-oriented repository, resolve material decisions with the user, persist one decision-complete change record, publish it through a documentation-only pull request when GitHub is in scope, independently review…

Independently and read-only review one existing GitHub pull request in an Azure-oriented or Azure Workflow-onboarded repository against its request, repository authority, linked issue/change record when required, exact base/head, complete diff, real callers,…

Explain an Azure-oriented or Azure Workflow-onboarded repository, feature, architecture, code path, technical term, failure, GitHub issue, pull request, review comment, or check result in plain English without changing anything. Use when a non-coder wants to…

Inspect live Azure state for an Azure-oriented repository and plan, apply, validate, or recover one tightly scoped Azure operation only after explicit approval of the exact mutation. Use for subscription/resource inventory, deployment diagnosis, drift checks,…

Use this skill whenever the user mentions a UK vehicle valuation, pre-accident value, total loss settlement, diminution, import valuation, guide value challenge, CAP / Cazana / Glass's / HPI comparison, no guide value, market-only valuation, evidence pack,…

Use this skill whenever the user mentions a UK vehicle valuation, pre-accident value, total loss settlement, diminution, import valuation, guide value challenge, CAP / Cazana / Glass's / HPI comparison, no guide value, market-only valuation, evidence pack,…

Use this skill whenever the user mentions a UK vehicle valuation, pre-accident value, total loss settlement, diminution, import valuation, guide value challenge, CAP / Cazana / Glass's / HPI comparison, no guide value, market-only valuation, evidence pack,…