jrmatherly
21 verified skills
new-openspec-proposal-from-roadmap
Scaffold a new OpenSpec change proposal by extracting scope, prereqs, and canonical references from an existing docs/operations/roadmap.md entry. Use when promoting a [Ready] or [Deferred] roadmap item into an active OpenSpec change. Delegates to /opsx:propose after pre-populating the proposal content, which saves ~5 min of manual scope-copying per proposal and eliminates "I forgot to capture the effort estimate" drift.
development
phase-0-progress
Verify Phase 0 hard-gate status for the enterprise self-hosting migration by checking documentation claims against filesystem evidence (regression guards, CI workflow, Drizzle migrations, OpenSpec proposals, GPG verification). Use when the user asks about Phase 0 progress, before committing changes that touch self-hosting migration, or after completing a gate to confirm the status claim is still accurate. User and Claude invocable.
testing
release-and-publish
Bump version, tag, push, wait for CI build, and publish the GitHub release in one step
development
release
Guide the GitHub Actions release flow — version bump, tag push, verify CI, publish draft
testing
session-sync
End-of-task sync — update CLAUDE.md, rebuild code graph, sync Serena memories, check roadmap drift, and commit. Run after completing any significant work to ensure all drift surfaces are current.
development
verify-pin
Background knowledge for safely bumping the pinned versions of Claude CLI binary, Codex CLI binary, Electron, Vite, Tailwind, or Shiki in this repo. Each pin is load-bearing for a different reason — this skill encodes the per-pin rationale and the regression test that must pass before the bump can land. Use proactively whenever editing package.json, scripts/download-claude-binary.mjs, scripts/download-codex-binary.mjs, or any file that mentions these versions. Claude-only (background knowledge, not user-invocable).
tools
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
tools
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
tools
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
tools
openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
testing
openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
development
cluster-handoff
Generate a self-contained handoff prompt for the Talos cluster repo (/Users/jason/dev/ai-k8s/talos-ai-cluster/) when a change in this repo needs matching cluster-side work (Envoy SecurityPolicy, LiteLLM config, Flux sync, deploy/** manifests). Produces a pasteable prompt with current-change context, pinned cluster commit, cluster-side scope, and the "trust-the-edge + LiteLLM OSS only" rules so the cluster-side agent has full context without this session.
development
docs-drift-check
Audit CLAUDE.md, README.md, CONTRIBUTING.md, AGENTS.md, Serena memories, and docs/ pages against the actual codebase for the documented drift points. Run before any release, after touching schema/routers/dependencies, or when starting a doc cleanup pass. User-only — explicit invocation, not a background task.
development
new-regression-guard
Scaffold a new bun:test regression guard under tests/regression/ following the existing file-walking + forbidden-patterns + structured-error-report pattern. Ask the user for the guard name, scan scope, forbidden patterns or assertion type, allowlist files, and the motivating OpenSpec change or Phase 0 gate. User-only — explicit invocation, not a background task.
testing
new-router
Scaffold a new tRPC router with proper types, imports, and registration in the app router
tools
openspec-propose-gate
Scaffold a new OpenSpec change proposal from a Phase 0 hard gate in the 1Code enterprise fork. Use when the user asks to "create the OpenSpec proposal for gate
development
project-orchestrator
Project-native orchestrator for the 1Code enterprise fork. Use this skill IMMEDIATELY whenever a task touches auth / credentials / tokens / env vars / LiteLLM config / upstream boundary (`src/renderer/` calls to `remoteTrpc.*` or `fetch(${apiUrl})`) / OpenSpec workflow / Phase 0 gates / version-pin bumps / `.claude/.tscheck-baseline` / credential-store.ts — the Step 0 hard-rule gate catches dead-end routes before they start. Also use when the task is ambiguous or multi-step, when you're unsure which skill/subagent/MCP to use, when the user mentions "orchestrate", "coordinate", "plan this work", "what's the right approach", "who handles X", "where do I start", "route this task", "what's already done vs. pending", or when the task could intersect with an active OpenSpec change (`upgrade-vite-8-build-stack`, `replace-gray-matter-with-front-matter`) that already covers the work. Understands the fork posture, Phase 0 status (15/15 complete), 10 hard rules, 17 project skills (16 routing targets + this orchestrator itself), 5 project subagents, 8 available MCPs, and canonical docs under `docs/enterprise/` + `docs/conventions/`.
tools
release-smoke
Post-release smoke checklist across the 3-OS matrix (macOS arm64+x64, Linux, Windows). Covers artifact download, Gatekeeper/SmartScreen/AppImage launch checks, auto-update test, notarization verification, and Trivy+Cosign container verification. Run against a draft GitHub Release BEFORE promoting to published. Must be invoked manually by the user — not auto-triggerable.
testing
roadmap-tracker
View, add, or complete items on the centralized project roadmap at docs/operations/roadmap.md. Use when starting a session to see outstanding work, when deferring work to record it, or when completing work to update the tracker. Triggers on "roadmap", "outstanding work", "what's left", "defer", "follow-up".
documentation
upstream-boundary-check
Use when reading or writing any file under src/renderer/ that calls remoteTrpc.* or fetch(${apiUrl}/...). Verifies the call site is documented in docs/enterprise/upstream-features.md and warns if a new upstream-backend dependency is being introduced without a corresponding F-entry. This skill enforces the enterprise-fork posture documented in CLAUDE.md.
development
verify-strategy-compliance
Background knowledge for AI agents before editing any file that handles authentication tokens or spawn environment variables in the 1Code enterprise fork. Triggers when touching src/main/lib/trpc/routers/claude.ts, claude-code.ts, claude/env.ts, feature-flags.ts, or claude-token.ts. Reminds the agent to consult the frozen Envoy Gateway strategy doc (auth-strategy-envoy-gateway.md v2.1) sections that impose hard rules on credential handling.
development