claude

devex-charter

Shared delivery practices for human–AI teams: planning, tickets, model selection, testing, independent review and release readiness. Install for a project or user; adopt project-owned authority and checks.

13 on GitHubby Jaroslav Pantsjohav0.6.1Apache-2.0updated 4 days ago
/

Plugin devex-charter from marketplace join-the-team-marketplace in jpantsjoha/ai-native-developer-experience. Commands read from the repo's manifest — 4 days ago.

This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.

What it installs

Skills (26)

  • adk-expert

    Google ADK (Agent Development Kit) orchestration patterns — boundaries, agent composition, and tool seams. Trigger when designing or reviewing multi-agent systems built on ADK. Authoritative source: adk.dev.

  • adversarial-gate

    JP's signature red-team pass — "how would I break this?" Argue against your own approach before proceeding. Trigger on any high-stakes decision, architecture choice, or before marking work complete.

  • cloud-checkup

    Read-only SRE checkup of any GCP project: deterministic probes of the edge, Cloud Run services, 7-day error logs, Cloud Scheduler, alert policies and uptime checks, Secret Manager and IAM, the data stores and the machine's own scheduled jobs, audited into one fixed status table (LIVE / WARNING / RED

  • cloud-expert

    Cloud guardrails for any vendor workload — Google Cloud (GCP, Vertex AI, GKE), AWS (IAM, EKS, Bedrock), Azure (Entra ID, Policy, AKS), Alibaba Cloud (RAM, mainland/international residency). Enforces identity least-privilege, mechanical policy, data boundaries, residency, cost caps, network egress an

  • cost-guardrail

    LLM and cloud cost awareness — model tiering, token budgets, right-sizing, and when a cheaper model suffices. Trigger before finalising any architecture that calls LLMs, before scaling a workload, or when a cost estimate is needed.

  • cxo-oversight

    Challenge vision alignment, value, cost, risk and operating ownership at material scope or release decisions.

  • delivery-orchestrator

    Decompose an epic into atomic parallelizable tasks, route each to the right skill, and keep the four delivery records straight — issues, STATUS, ROADMAP, CHANGELOG. Use as a meta-router when several skills could apply, and as the baseline for how delivery state is recorded. Trigger at the start of a

  • domain-validator

    Validate agent output against declared domain rules and ground truth before trusting it downstream. Trigger after any agent produces output that will be used in a decision, stored persistently, or passed to another agent.

  • frontend-performance-audit

    Measure real frontend performance — Core Web Vitals (LCP, CLS, INP), page-load traces, CPU and network throttling, Lighthouse accessibility/SEO scores, and heap growth — using chrome-devtools-mcp against a live browser. Trigger when asked "is the page fast enough", "measure Core Web Vitals", "why is

  • get-it-done

    Pursue an agreed goal to a working outcome without waiting: decompose it, re-prioritise as evidence arrives, branch, gate, get an independent review (a different model or a fresh reviewer subagent — the writer never approves), merge, prune, and bank the operator's decisions in STATUS.md instead of b

  • github-manager

    Use when configuring or optimising GitHub repositories for cost-effective, consistent operations — CI triggers, Actions billing, issue tracking, labelling, branch protection, or release workflow.

  • governance-guardrail

    Check proposed stack, data flows, cloud choices, and delivery controls against declared enterprise policies, compliance frameworks, and security controls. Trigger at R2/R3 risk classification, before locking architecture decisions, or when the operating profile names a governance pointer.

  • mcp-server-scaffold

    Scaffold and govern an MCP server as a bounded tool seam. Defines which tools the agent may call, enforces the principle that agents call tools and tools call infrastructure. Trigger when adding or reviewing an MCP server in an agent system.

  • operating-model-bootstrap

    Bootstrap or harden a project's operating model for mixed human and AI delivery teams. Use when starting a repository, adopting an agent harness, defining authority and risk tiers, coordinating parallel agents safely, binding evidence and review to an exact candidate, or correcting fragmented rules

  • plugin-submission

    Govern discovery, eligibility, and submission of a plugin or skill to official directories, registries, marketplaces, and curated GitHub lists. Use when preparing or sending plugin listings, marketplace forms, directory PRs, or repository recommendations; require current policy evidence and a final

  • pr-reviewer

    Review gate for correctness, reuse, and simplification. Produces a structured verdict with actionable findings. Trigger on any PR before merge, or on any agent-generated code before it is committed.

  • product-owner

    Maintain vision, user journeys, evolving requirements and roadmap outcomes when intent or acceptance changes.

  • release-manager

    Govern the SemVer release process — versioning discipline, tag-based GitHub releases, changelog hygiene, and the ADR that confirms the release strategy is agreed. Trigger when setting up a release process, before a first public release, or when release practice has become inconsistent. Owned by deli

  • release-readiness

    Go / no-go gate before any deployment. Checks failure modes, rollback plan, cost, production bar, and definition of done. Trigger before releasing to any environment that carries real consequences.

  • sitrep

    Synthesise a status, standup, or situation-report from current work state. Trigger when a team member needs a concise summary of where things stand, what is blocked, and what is next.

  • spec-first-delivery

    Force plan, HLD, ADRs, and constraints to exist BEFORE any code is generated. Trigger when starting a new feature, epic, or significant change.

  • system-performance-guardrail

    Measure, root-cause, fix, verify and record performance contention on a developer machine: cloud-sync daemons (iCloud Drive, OneDrive, Dropbox, Google Drive), file indexers, AI-tool MCP server fleets, and automation browsers left behind by tests and browser skills. Trigger when the machine is slow,

  • test-strategy

    Map requirement acceptance to proportionate executable checks and real user journeys before implementation and completion.

  • the-architect

    Architecture decisions, trade-off analysis, and ADR authoring. Trigger when a significant technical decision needs to be made, documented, and owned — not when an implementation detail needs a choice.

  • using-the-harness

    Session-start orientation for this team harness. Load first, before any work. Explains the operating contract, when each skill triggers, and how installed companion plugins supply agent-craft capabilities while this harness supplies the team contract. Trigger at the start of every session and whenev

  • wrap-it-up

    End a long engineering session cleanly under token and attention pressure: freeze the in-flight set, delegate execution to subagents and judgement to an independent reviewer, and drive every item to one of three exits — merged, deferred with a record, or operator-blocked with a decision brief — then

Slash commands (6)

  • /devex-charter:bootstrap

    Bootstrap the operating model and minimal delivery-planning seed (dry-run first, never overwrites)

  • /devex-charter:get-it-done

    Pursue an agreed goal to a working outcome without waiting, using the get-it-done skill

  • /devex-charter:init

    Initialise the planning seed and record the human team, roles, and escalation channels

  • /devex-charter:sitrep

    Situation report: what landed, what is in flight, what is blocked, and the decisions waiting on the operator

  • /devex-charter:validate

    Validate the operating-model seed — manual binding, adapter drift, adoption state, checkpoint/evidence

  • /devex-charter:wrap-it-up

    Close out the in-flight work: drive each item to merged, deferred or operator-blocked, then a clean baseline

Hooks (1)

  • SessionStart

    "${CLAUDE_PLUGIN_ROOT}/hooks/session-start"

View source on GitHub jpantsjoha.com

More from jpantsjoha/ai-native-developer-experience

All 2 plugins →

Legacy name of devex-charter, kept so pre-0.5.0 install commands keep working. Same plugin; install devex-charter, not both.

26 skills · 6 commands · hooks

13

Similar plugins

harness

claude

에이전트 팀 & 스킬 아키텍트 v2. 도메인/프로젝트에 맞는 하네스를 구성하고, 전문 에이전트를 정의하며, 에이전트가 사용할 스킬을 생성하는 메타 스킬. 워크플로우 오케스트레이션 · 퍼시스턴트 에이전트 협업 · 서브에이전트 위임 3중 실행 모드 지원.

2 skills

revfactory/harness 9,355

Natural language team builder for Claude Code — choose Agent Teams or Workflows and select Fable (default), Opus, Sonnet, or per-role models. Preserves approved model assignments; Haiku is opt-in.

fivetaku/gptaku_plugins 1,298

Dynamically assemble expert agent teams for complex tasks using Claude Code's agent teams feature

1 skill

team-attention/plugins-for-claude-natives 831

hello2cc

claude

Thin Claude Code plugin for third-party models, focused on host state, protocol adaptation, and repeated-failure debounce.

1 agent · hooks

hellowind777/hello2cc 690

cozempic

claude

2x the effective context with smart weight-loss for Claude Code — prune bloated sessions, protect agent teams from compaction, monitor token usage with MCP tools

5 skills · 1 MCP server · hooks

Ruya-AI/cozempic 430

Two-agent optimization team: researcher proposes, critic challenges, lead presents synthesized result

2 agents

NTCoding/claude-skillz 364

Maintain devex-charter?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins2 plugins