@event4u/agent-config 2.7.0 → 2.8.0

package/docs/catalog.md

@@ -1,17 +1,18 @@
 # agent-config — Public Catalog
 
-Consumer-facing catalog of all **408 public artefacts** shipped by
+Consumer-facing catalog of all **424 public artefacts** shipped by
 this package. Internal package-maintenance rules and deprecation shims
 are excluded.
 
 > **Regenerate:** `python3 scripts/generate_index.py`
 > Auto-generated — do not edit manually.
 
-## Skills (174)
+## Skills (189)
 
 | kind | name | extra | description |
 |---|---|---|---|
 | skill | [`accessibility-auditor`](../.agent-src/skills/accessibility-auditor/SKILL.md) |  | Use when reviewing UI for accessibility — WCAG 2.2 AA, keyboard nav, focus, ARIA, contrast, screen-reader semantics — even on 'is this a11y-OK?' or 'mach das barrierefrei'. |
+| skill | [`activation-design`](../.agent-src/skills/activation-design/SKILL.md) |  | Use when defining or auditing the activation event — aha-moment selection, retention correlation, falsifiable definition. Triggers on 'what is our aha moment', 'redefine activation'. |
 | skill | [`adr-create`](../.agent-src/skills/adr-create/SKILL.md) |  | Use when capturing an architectural decision — naming the file, picking the next ADR number, filling Status / Context / Decision / Consequences, and regenerating the index — even without saying 'ADR'. |
 | skill | [`adversarial-review`](../.agent-src/skills/adversarial-review/SKILL.md) |  | ONLY when user explicitly requests adversarial review, devil's advocate analysis, stress-testing a plan, or 'poke holes in this' — NOT for regular code review or design feedback. |
 | skill | [`agent-docs-writing`](../.agent-src/skills/agent-docs-writing/SKILL.md) |  | Use when reading, creating, or updating agent documentation, module docs, roadmaps, or AGENTS.md. Understands the full .augment/, agents/, and copilot-instructions structure. |
@@ -31,12 +32,14 @@ are excluded.
 | skill | [`blast-radius-analyzer`](../.agent-src/skills/blast-radius-analyzer/SKILL.md) |  | Use BEFORE editing shared code — enumerates every call site, event consumer, queue worker, API client, migration, and test that a planned change will touch, with a file:line citation per dependency. |
 | skill | [`bug-analyzer`](../.agent-src/skills/bug-analyzer/SKILL.md) |  | Use when the user shares a Sentry error, Jira bug ticket, or error description and wants root cause analysis. Also for proactive bug hunting and code audits for hidden bugs. |
 | skill | [`check-refs`](../.agent-src/skills/check-refs/SKILL.md) |  | Use when verifying cross-references between skills, rules, commands, guidelines, and context documents are not broken after edits, renames, or deletions. |
+| skill | [`churn-prevention`](../.agent-src/skills/churn-prevention/SKILL.md) |  | Use when designing churn defence — health-score signals, churn-cause split (involuntary / value / relationship / fit), early-warning loop. Triggers on 'why are accounts leaving'. |
 | skill | [`code-refactoring`](../.agent-src/skills/code-refactoring/SKILL.md) |  | Use when the user says "refactor this", "rename class", or "move method". Safely refactors PHP code — finds all callers, updates downstream dependencies, and verifies with quality tools. |
 | skill | [`code-review`](../.agent-src/skills/code-review/SKILL.md) |  | Use when the user says "review this", "check my code", or wants feedback on changes. Reviews for correctness, quality, security, and coding standards. |
 | skill | [`command-routing`](../.agent-src/skills/command-routing/SKILL.md) |  | Use when the user invokes a slash command like /create-pr, /commit, /fix-ci, or pastes command file content — routes to the right command with context inference and GitHub API patterns. |
 | skill | [`command-writing`](../.agent-src/skills/command-writing/SKILL.md) |  | Use when creating or editing a slash command in .agent-src.uncompressed/commands/ — frontmatter, numbered steps, safety gates — even when the user just says 'add a /command for X'. |
 | skill | [`competitive-positioning`](../.agent-src/skills/competitive-positioning/SKILL.md) |  | Use when comparing this package to a peer / competitor — ours-vs-theirs verdict table, axis selection, adoption queue. Triggers on 'how do we compare to X', 'should we adopt their pattern'. |
 | skill | [`composer-packages`](../.agent-src/skills/composer-packages/SKILL.md) |  | Use when building or maintaining a Composer library — versioning, Laravel integration, autoloading, publishing to private registries — even when the user says 'release a new version'. |
+| skill | [`content-funnel-design`](../.agent-src/skills/content-funnel-design/SKILL.md) |  | Use when mapping funnel-stage to content shape — conversion-pathway, content-as-system, leverage-point selection. Triggers on 'design our content funnel', 'why does mid-funnel leak'. |
 | skill | [`context-authoring`](../.agent-src/skills/context-authoring/SKILL.md) |  | Use when filling in knowledge-layer context files — auth-model, tenant-boundaries, data-sensitivity, deployment-order, observability — interactive walkthrough that turns templates into reviewer fuel. |
 | skill | [`context-document`](../.agent-src/skills/context-document/SKILL.md) |  | Use when the user says "create context", "document this area", or wants a structured snapshot of a codebase area for agent orientation. |
 | skill | [`conventional-commits-writing`](../.agent-src/skills/conventional-commits-writing/SKILL.md) |  | Use when writing commit messages or squash-merge titles — `feat:`, `fix:`, `chore:`, scopes, breaking changes — even when the user just says 'commit this' without naming Conventional Commits. |
@@ -47,6 +50,7 @@ are excluded.
 | skill | [`data-flow-mapper`](../.agent-src/skills/data-flow-mapper/SKILL.md) |  | Use BEFORE editing code that touches user data — traces the value from entry → validation → transformation → storage → egress, every hop cited with file:line. |
 | skill | [`database`](../.agent-src/skills/database/SKILL.md) |  | Use when working with database architecture, MariaDB/MySQL tuning, indexing strategies, slow queries, or multi-connection patterns — even when the user just says 'this query is slow'. |
 | skill | [`dcf-modeling`](../.agent-src/skills/dcf-modeling/SKILL.md) |  | Wing-4 valuation cognition for a CFO / finance-partner. Use when a deal, internal investment, or board ask names DCF, intrinsic value, WACC, terminal value, or 'what's it worth on a 5-year hold'. |
+| skill | [`deal-qualification-meddic`](../.agent-src/skills/deal-qualification-meddic/SKILL.md) |  | Use when qualifying or disqualifying a single deal — MEDDIC slots with evidence, inversion test, disqualification heuristic. Triggers on 'is this deal real', 'should we walk away'. |
 | skill | [`decision-record`](../.agent-src/skills/decision-record/SKILL.md) |  | Use when locking a trade-off, structuring an ADR draft, or wiring supersession chains — frames options · trade-offs · consequences before the file is written by `adr-create`. |
 | skill | [`deep-reading-analyst`](../.agent-src/skills/deep-reading-analyst/SKILL.md) |  | Deep analysis of articles/long-form via thinking frameworks (SCQA, mental models, inversion) — 'analyze article', 'deep dive', 'extract insights', URL/text wanting depth not summary. |
 | skill | [`defense-in-depth`](../.agent-src/skills/defense-in-depth/SKILL.md) |  | Use when validation needs entry, business-logic, environment, and instrumentation guards so a bad value cannot reach the failure point — turns a local bug fix into a structural one. |
@@ -58,20 +62,25 @@ are excluded.
 | skill | [`discovery-interview`](../.agent-src/skills/discovery-interview/SKILL.md) |  | Use when running discovery interviews — question-bank build, bias audit, insight extraction. Triggers on 'audit my guide', 'extract insights from transcript', 'is my hypothesis falsifiable'. |
 | skill | [`docker`](../.agent-src/skills/docker/SKILL.md) |  | Use when working with Docker — Dockerfile edits, docker-compose services, containers, or the dual-container (fast + Xdebug) setup — even when the user just says 'my container won't start'. |
 | skill | [`dto-creator`](../.agent-src/skills/dto-creator/SKILL.md) |  | Use when the user says "create a DTO", "new data transfer object", or needs to convert request/response data into a typed PHP class. Creates DTOs with SimpleDto base class and attribute mapping. |
+| skill | [`editorial-calendar`](../.agent-src/skills/editorial-calendar/SKILL.md) |  | Use when shaping cadence — evergreen / campaign / reactive split, beat-mapping across channel stages, content-debt management. Triggers on 'plan our content cadence', 'what should we publish'. |
 | skill | [`eloquent`](../.agent-src/skills/eloquent/SKILL.md) |  | Use when writing Eloquent models, relationships, scopes, or queries via Model:: — 'fetch users with their orders'. NOT for PHPStan output, non-Eloquent services, or raw SQL questions. |
 | skill | [`error-handling-patterns`](../.agent-src/skills/error-handling-patterns/SKILL.md) |  | Use when picking a failure-reporting strategy — exceptions vs Result types, recoverable vs not, retry / circuit-breaker / graceful degradation — decision framework only, catalogues externalized. |
 | skill | [`estimate-ticket`](../.agent-src/skills/estimate-ticket/SKILL.md) |  | Estimate a Jira/Linear ticket — 'estimate PROJ-123', 'wie groß ist das?', 'should we split this?' — size + risk + split + uncertainty, sibling of /refine-ticket, close-prompt. |
 | skill | [`existing-ui-audit`](../.agent-src/skills/existing-ui-audit/SKILL.md) |  | Use BEFORE writing or editing any non-trivial UI — inventories components, design tokens, shadcn primitives, and reusable patterns into state.ui_audit. Hard gate for the ui directive set. |
+| skill | [`expansion-playbook`](../.agent-src/skills/expansion-playbook/SKILL.md) |  | Use when designing account-expansion mechanics — upsell vs cross-sell, expansion-trigger signals, NRR cognition. Triggers on 'lift NRR', 'when do we upsell vs cross-sell'. |
 | skill | [`fe-design`](../.agent-src/skills/fe-design/SKILL.md) |  | Reference for frontend-design heuristics — component architecture, layout patterns, form/table design, responsive strategy, a11y, UX principles. Stack-agnostic; cited by directives/ui/design.py. |
 | skill | [`feature-planning`](../.agent-src/skills/feature-planning/SKILL.md) |  | Use when the user says "plan a feature", "brainstorm", "explore this idea", or wants to go from idea to structured plan and roadmap. |
 | skill | [`file-editor`](../.agent-src/skills/file-editor/SKILL.md) |  | Use when opening edited files in the user's IDE. Reads settings from .agent-settings.yml to determine IDE and whether auto-open is enabled. |
 | skill | [`finishing-a-development-branch`](../.agent-src/skills/finishing-a-development-branch/SKILL.md) |  | Use when the feature is implementation-complete and the next step is 'ship it' — verifies, cleans up, and routes to merge/PR/park/discard — even when the user just says 'I'm done, what now?'. |
 | skill | [`flux`](../.agent-src/skills/flux/SKILL.md) |  | Use when the project uses `livewire/flux` — dispatched by `directives/ui/{apply,review,polish}.py`. Covers Flux components, slots, variants, and form primitives. |
+| skill | [`forecast-accuracy`](../.agent-src/skills/forecast-accuracy/SKILL.md) |  | Use when constructing the forecast call — commit / best-case / pipeline categorisation, deal-level evidence test, accuracy retro-loop. Triggers on 'build the forecast', 'why does our commit miss'. |
 | skill | [`form-handler`](../.agent-src/skills/form-handler/SKILL.md) |  | Use when designing or reviewing a form — validation timing, error display, submission lifecycle, optimistic UI, dirty/pristine state, idempotency — even on 'why does submit double-fire?'. |
+| skill | [`fundraising-narrative`](../.agent-src/skills/fundraising-narrative/SKILL.md) |  | Use when shaping a capital-raise pitch — why-now / why-us / why-this framing, market-size reasoning, traction-story construction. Triggers on 'tighten the pitch', 'why-now is weak'. |
 | skill | [`funnel-analysis`](../.agent-src/skills/funnel-analysis/SKILL.md) |  | Use when diagnosing where a SaaS or product funnel leaks — visitor → signup → activation → paid → retained — channel-agnostic, conversion-rate-driven. |
 | skill | [`git-workflow`](../.agent-src/skills/git-workflow/SKILL.md) |  | Use when working with Git — branch naming, commit messages, PR creation, rebasing, or the code review process — even when the user says 'push this' or 'merge the branch' without naming Git. |
 | skill | [`github-ci`](../.agent-src/skills/github-ci/SKILL.md) |  | Use when working with GitHub Actions — workflow YAML, quality gates, test matrices, deployment triggers, reusable workflows — even when the user just says 'my CI is failing' or 'add a check'. |
 | skill | [`grafana`](../.agent-src/skills/grafana/SKILL.md) |  | Use when working with Grafana — dashboards, Loki LogQL queries, alerting rules, monitoring panels — even when the user just says 'build me a dashboard' or 'query the logs' without naming Grafana. |
+| skill | [`gtm-launch`](../.agent-src/skills/gtm-launch/SKILL.md) |  | Use when sequencing a launch — alpha / beta / GA waves, audience-by-wave logic, narrative beats per wave, engineering-readiness gates. Triggers on 'plan the launch', 'sequence GA'. |
 | skill | [`guideline-writing`](../.agent-src/skills/guideline-writing/SKILL.md) |  | Use when creating or editing a guideline in docs/guidelines/ — reference material cited by skills, no auto-triggers — even when the user just says 'write up our naming conventions'. |
 | skill | [`incident-commander`](../.agent-src/skills/incident-commander/SKILL.md) |  | Use during or right after an incident — frames severity, sets comms cadence, drafts the post-mortem skeleton — even when the user just says 'production is down' or 'wir haben einen Vorfall'. |
 | skill | [`jira-integration`](../.agent-src/skills/jira-integration/SKILL.md) |  | Use when the user says "check Jira", "create ticket", "update issue", or needs JQL queries, ticket transitions, or branch-to-ticket linking. |
@@ -102,12 +111,14 @@ are excluded.
 | skill | [`md-language-check`](../.agent-src/skills/md-language-check/SKILL.md) |  | Use BEFORE saving any .md under .augment/, .agent-src*/, or agents/ — scans umlauts, German function words, and quoted German phrases outside DE:/EN: anchor blocks. Hard gate per language-and-tone. |
 | skill | [`memory-consolidation`](../.agent-src/skills/memory-consolidation/SKILL.md) |  | Use when consolidating session signals into curated memory — four-phase loop ORIENT → GATHER → CONSOLIDATE → PRUNE. Triggers on 'mine my sessions', 'consolidate memory', 'review intake signals'. |
 | skill | [`merge-conflicts`](../.agent-src/skills/merge-conflicts/SKILL.md) |  | Use when the user has merge conflicts or says "resolve conflicts". Understands conflict markers, resolution strategies, and verification workflow. |
+| skill | [`messaging-architecture`](../.agent-src/skills/messaging-architecture/SKILL.md) |  | Use when shaping the primary message, supporting proofs, and audience-by-message matrix from a locked positioning frame — before any copy or launch beat. Triggers on 'tighten the message stack'. |
 | skill | [`migration-architect`](../.agent-src/skills/migration-architect/SKILL.md) |  | Use when shaping a non-trivial migration — rollout phases, dual-write windows, cutover sequencing, deprecation cycles — hands off to `migration-creator` for DDL once locked. |
 | skill | [`migration-creator`](../.agent-src/skills/migration-creator/SKILL.md) |  | Use when the user says "create migration", "add column", or "new table". Creates migrations with correct table prefixes, column naming, and multi-tenant awareness. |
 | skill | [`mobile-e2e-strategy`](../.agent-src/skills/mobile-e2e-strategy/SKILL.md) |  | Use when picking a mobile E2E framework — Detox / Appium / Maestro / XCUITest / Espresso — or planning iOS Simulator / Android Emulator coverage in CI for RN, Expo, or native apps. |
 | skill | [`module-management`](../.agent-src/skills/module-management/SKILL.md) |  | Use when the user says "create module", "explore module", or works within app/Modules/. Understands module structure, auto-loading, route registration, and namespace conventions. |
 | skill | [`multi-tenancy`](../.agent-src/skills/multi-tenancy/SKILL.md) |  | Use when working with the multi-tenant architecture — customer DB switching, FQDN routing, tenant isolation, or cross-tenant operations. |
 | skill | [`okr-tree-modeling`](../.agent-src/skills/okr-tree-modeling/SKILL.md) |  | Use when decomposing a company objective into team OKRs, auditing a draft OKR tree, or stress-testing an existing one for measurability and laddering. |
+| skill | [`onboarding-design`](../.agent-src/skills/onboarding-design/SKILL.md) |  | Use when designing customer onboarding — time-to-first-value, milestone design, friction audit, drop-off diagnosis. Triggers on 'fix onboarding', 'why do new accounts churn fast'. |
 | skill | [`openapi`](../.agent-src/skills/openapi/SKILL.md) |  | Use when documenting APIs — OpenAPI/Swagger, PHP attributes, Redocly validation, versioned specs — even when the user just says 'document this endpoint' without naming OpenAPI. |
 | skill | [`override-management`](../.agent-src/skills/override-management/SKILL.md) |  | Creates and manages project-level overrides for shared skills, rules, and commands — extending or replacing originals from .augment/ with project-specific behavior in agents/overrides/. |
 | skill | [`performance`](../.agent-src/skills/performance/SKILL.md) |  | Use when optimizing application performance — caching strategies, eager loading, query optimization, Redis patterns, or background job design. |
@@ -117,9 +128,11 @@ are excluded.
 | skill | [`php-coder`](../.agent-src/skills/php-coder/SKILL.md) |  | Writes or edits PHP code — controllers, classes, type hints, SOLID refactors, modern idioms — even without naming PHP. NOT for writing tests (use pest-testing) or explaining PHP concepts. |
 | skill | [`php-debugging`](../.agent-src/skills/php-debugging/SKILL.md) |  | Use when debugging PHP with Xdebug — breakpoints, step-through, dual-container setup, IDE configuration, header-based routing — even when the user just says 'why does this blow up on request X'. |
 | skill | [`php-service`](../.agent-src/skills/php-service/SKILL.md) |  | Use when the user says 'create service', 'new service class', or needs a PHP service following SOLID principles with proper DI and repository usage. |
+| skill | [`pipeline-strategy`](../.agent-src/skills/pipeline-strategy/SKILL.md) |  | Use when designing or auditing a sales pipeline — stage exit criteria, per-cell conversion, coverage reasoning, leak detection. Triggers on 'tighten our pipeline', 'where is the leak'. |
 | skill | [`playwright-architect`](../.agent-src/skills/playwright-architect/SKILL.md) |  | Use when shaping a Playwright suite — locator strategy, Page Object boundaries, fixture composition, flake-prevention architecture, CI-vs-local split — even on 'design our E2E tests'. |
 | skill | [`playwright-testing`](../.agent-src/skills/playwright-testing/SKILL.md) |  | Use when writing Playwright E2E tests — browser automation, visual regression testing, Page Objects, fixtures, and reliable test patterns. |
 | skill | [`po-discovery`](../.agent-src/skills/po-discovery/SKILL.md) |  | Use when shaping a fuzzy product ask into a refined backlog item — problem framing, user-story rewrite, AC tightening — even if the user just says 'help me write this ticket'. |
+| skill | [`positioning-strategy`](../.agent-src/skills/positioning-strategy/SKILL.md) |  | Use when locking the market frame — category, segment, alternative, point-of-view — before messaging, launch, or pricing rides on it. Triggers on 'who are we for', 'opposable audit'. |
 | skill | [`project-analysis-core`](../.agent-src/skills/project-analysis-core/SKILL.md) |  | Use for the universal deep-analysis workflow: project discovery, version resolution, docs loading, architecture mapping, execution flow, and package research. |
 | skill | [`project-analysis-hypothesis-driven`](../.agent-src/skills/project-analysis-hypothesis-driven/SKILL.md) |  | Use when a bug has multiple plausible causes across layers — competing hypotheses, validation loops, evidence-based conclusions — even when the user just says 'why is this happening?'. |
 | skill | [`project-analysis-laravel`](../.agent-src/skills/project-analysis-laravel/SKILL.md) |  | Use for deep Laravel project analysis: boot flow, request lifecycle, container usage, Eloquent/data flow, async systems, and Laravel-specific failure patterns. |
@@ -144,6 +157,7 @@ are excluded.
 | skill | [`release-comms`](../.agent-src/skills/release-comms/SKILL.md) |  | Use when turning a shipped changelog into a release narrative — value-not-feature framing, audience-segmented surfaces, one source of truth. Triggers on 'announce the release', 'write changelog post'. |
 | skill | [`repomix-packer`](../.agent-src/skills/repomix-packer/SKILL.md) |  | Use when packaging a codebase to a single AI-friendly file for LLM analysis — local or remote, XML/Markdown/JSON, token counting, gitignore filtering, peer-side `repomix` CLI. |
 | skill | [`requesting-code-review`](../.agent-src/skills/requesting-code-review/SKILL.md) |  | Use when asking for a review or creating a PR — self-review first, frame the right context, test plan included — even when the user just says 'open a PR' or 'ready to merge'. |
+| skill | [`retention-loops`](../.agent-src/skills/retention-loops/SKILL.md) |  | Use when designing product-led retention — habit formation, trigger-action-reward, network vs single-user loops. Triggers on 'why don't users come back', 'design a habit loop'. |
 | skill | [`review-routing`](../.agent-src/skills/review-routing/SKILL.md) |  | Use when preparing a PR description, suggesting reviewers, or flagging risk — produces owner-mapped roles plus historical bug-pattern matches from project-local YAML. |
 | skill | [`rice-prioritization`](../.agent-src/skills/rice-prioritization/SKILL.md) |  | Use when ranking competing initiatives for a roadmap, breaking a tie between two features, or auditing a backlog for hidden low-value work via Reach × Impact × Confidence ÷ Effort. |
 | skill | [`risk-officer`](../.agent-src/skills/risk-officer/SKILL.md) |  | Use when surfacing and prioritising risk before commit — blast-radius framing, mitigations, residual-risk verdict — even if the user just says 'what could go wrong here?'. |
@@ -184,6 +198,7 @@ are excluded.
 | skill | [`validate-feature-fit`](../.agent-src/skills/validate-feature-fit/SKILL.md) |  | Validate whether a feature request fits the existing codebase — check for duplicates, contradictions, scope creep, and architectural misfit |
 | skill | [`verify-completion-evidence`](../.agent-src/skills/verify-completion-evidence/SKILL.md) |  | Use when claiming 'done', suggesting a commit, push, or PR — runs the evidence gate so completion claims come from fresh output in this message, not memory or earlier runs. |
 | skill | [`voc-extract`](../.agent-src/skills/voc-extract/SKILL.md) |  | Use when extracting Voice-of-Customer themes from existing artefacts — GH issues, PR threads, Sentry patterns. Triggers on 'what are users saying', 'recurring complaints', 'top themes'. |
+| skill | [`voice-and-tone-design`](../.agent-src/skills/voice-and-tone-design/SKILL.md) |  | Use when shaping brand voice — voice attributes, tone-by-context matrix, consistency review. Triggers on 'define our voice', 'why does our copy sound different on every surface'. |
 | skill | [`websocket`](../.agent-src/skills/websocket/SKILL.md) |  | Use when building real-time features — WebSocket broadcasting, live updates, presence channels, connection state — even when the user just says 'push this to the client live'. |
 
 ## Rules (58)
@@ -360,7 +375,7 @@ are excluded.
 | command | [`upstream-contribute`](../.agent-src/commands/upstream-contribute.md) |  | Contribute a learning, skill, rule, or fix from a consumer project back to the shared agent-config package |
 | command | [`work`](../.agent-src/commands/work.md) |  | Drive a free-form prompt end-to-end through refine → score → plan → implement → test → verify → report — Option-A loop over the `work_engine` Python engine, confidence-band gated, no auto-git. |
 
-## Guidelines (70)
+## Guidelines (71)
 
 | kind | name | category | description |
 |---|---|---|---|
@@ -404,6 +419,7 @@ are excluded.
 | guideline | [`cross-role-handoff`](../docs/guidelines/cross-role-handoff.md) | (root) |  |
 | guideline | [`readme-size-and-splitting`](../docs/guidelines/docs/readme-size-and-splitting.md) | docs |  |
 | guideline | [`playwright`](../docs/guidelines/e2e/playwright.md) | e2e |  |
+| guideline | [`gtm-handoff`](../docs/guidelines/gtm-handoff.md) | (root) |  |
 | guideline | [`api-design`](../docs/guidelines/php/api-design.md) | php |  |
 | guideline | [`artisan-commands`](../docs/guidelines/php/artisan-commands.md) | php |  |
 | guideline | [`blade-ui`](../docs/guidelines/php/blade-ui.md) | php |  |

package/docs/contracts/adr-gtm-context-spine.md

@@ -0,0 +1,115 @@
+---
+stability: beta
+---
+
+# ADR — GTM context-spine: Wing-3 slot extension
+
+> **Status:** Decided · 2026-05-13
+> **Roadmap origin:** `agents/roadmaps/` (Block G — G1, archived after merge)
+> **Builds on:** [`context-spine.md`](context-spine.md) — tri-slot
+> contract (`product`, `team`, `repo`) locked at 3 by council Q1
+> (2026-05-05 KEEP-3, unified-senior-roles iter 1).
+> **Defers to:** [`cross-wing-handoff.md`](cross-wing-handoff.md) — typed
+> handoff contract; orthogonal to slot membership.
+
+## Decision
+
+The context-spine adds **three Wing-3-specific slots** under
+`agents/context-spine/`: `channel-stage`, `funnel-stage`,
+`customer-segment`. The schema enum in
+[`scripts/schemas/skill.schema.json`](../../scripts/schemas/skill.schema.json)
+extends from `{product, team, repo}` to
+`{product, team, repo, channel-stage, funnel-stage, customer-segment}`.
+
+The KEEP-3 lock from council Q1 applies to **cross-wing slots** —
+slabs every senior wing might read. The Wing-3 slots are
+**wing-scoped**: they exist for the GTM cluster (Block H, 16 skills)
+and the GTM personas (Block I, 7 personas). Engineering, Foundation,
+and Money / Strategy / Ops wings do not opt into them.
+
+| Slot | Path | Typical content |
+|---|---|---|
+| `channel-stage` | `agents/context-spine/channel-stage.md` | Which channels the GTM motion uses (awareness · consideration · decision · retention · expansion), per-channel maturity, channel-cost band. Read by H1 (`positioning-strategy`), H2 (`messaging-architecture`), H3 (`gtm-launch`), H6 (`editorial-calendar`). |
+| `funnel-stage` | `agents/context-spine/funnel-stage.md` | Funnel topology (top / mid / bottom / activation / retention), per-stage definition, exit-criteria for each. Read by H8 (`pipeline-strategy`), R1 (`funnel-analysis`), R2 (`activation-design`), R3 (`onboarding-design`). |
+| `customer-segment` | `agents/context-spine/customer-segment.md` | ICP, persona-by-segment, ARR-band-by-segment. Read by H7 (`ICP`), H8 (`pipeline-strategy`), H9 (`MEDDIC`), R4 (`retention-loops`). |
+
+## Why this was a real question
+
+Three options were on the table:
+
+1. **Force-fit into existing slots.** Stuff GTM context into the
+   `product` slab. Rejected: `product` is owned by the discovery wing
+   and a Wing-3 reader gets fuzzy semantics (channel maturity is not
+   product scope), Council Q1 explicitly fences `product` against
+   sprawl.
+2. **Wing-3-only frontmatter key.** Add `gtm_spine: [...]` as a
+   parallel field. Rejected: duplicates the read-discipline
+   mechanism, the lint gate, and the skill-author cognitive load.
+   Two spines is the slot-sprawl failure mode at a different layer.
+3. **Extend the spine, scope the slots.** Accepted: same mechanism,
+   same lint gate, same opt-in discipline; slot names carry the wing
+   scope (`channel-stage`, `funnel-stage`, `customer-segment` are
+   visibly GTM-shaped).
+
+## Citation-evidence gating — prospective
+
+The existing § 5 policy requires ≥ 2 shipped skills citing the new
+slot **before** the slot is added. For Wing-3 the citation chain is
+**prospective**: the roadmap (G1 → H → I) ships citing skills in the
+same iteration, ordered so G1 lands first to unblock H authoring.
+
+The ADR is the gating artefact (not the citations). The Block-H
+authoring procedure MUST cite ≥ 1 of the three new slots per skill
+or carry a one-line ADR-opt-out comment in the skill body. The G2
+linter (council Q7 boundary tests) enforces channel-agnosticism,
+which is orthogonal — a skill can cite `channel-stage` for context
+without prescribing channel-specific tactics.
+
+This relaxation is **wing-bounded**: future wings adding their own
+slots must either accumulate ≥ 2 citations from already-shipped
+skills, **or** write a per-wing ADR that names the citing-skill
+chain in the same iteration (the pattern this ADR establishes).
+
+## Migration plan for the existing senior catalog
+
+- **No retrofitting required.** Existing senior skills
+  (`customer-research`, `funnel-analysis`, `po-discovery`,
+  `refine-ticket`, `rice-prioritization`, etc.) keep their current
+  `context_spine` declarations. They MAY add a Wing-3 slot if their
+  cognition genuinely reads it; they MUST NOT be retrofitted
+  mechanically.
+- **Opt-out for off-wing skills.** Engineering / Foundation / Ops
+  senior skills do not need to mention the Wing-3 slots in any way.
+  The schema accepts subsets — declaring only `[product, team]`
+  remains valid.
+- **Slot-file authoring is consumer-side.** The package ships the
+  contract; consumer projects fill `agents/context-spine/channel-stage.md`
+  etc. when adopting Wing-3 skills. Missing slot file is graceful
+  per § 4 of the contract.
+
+## Counter-evidence the agent should listen for
+
+Three signals that this decision is wrong and the ADR needs revisiting:
+
+1. **Off-wing skills start declaring Wing-3 slots.** If an
+   Engineering skill cites `channel-stage`, the slot is misnamed or
+   the wing boundary is leaking. Re-scope the slot or rename it.
+2. **Wing-3 skills consistently ignore the slot they declared.** If
+   Block H skills declare `funnel-stage` but never quote it in their
+   procedure, the slot is decorative and should be deleted.
+3. **A fourth Wing-3 slot is proposed within the same iteration.**
+   That is slot-sprawl on the same wing — Block G2 boundary tests
+   should reject the addition until a follow-up ADR documents why
+   three slots are insufficient.
+
+## See also
+
+- [`context-spine.md`](context-spine.md) § 2 (slot table — extended),
+  § 5 (slot-add policy — wing-bounded extension clause).
+- [`scripts/schemas/skill.schema.json`](../../scripts/schemas/skill.schema.json)
+  — `context_spine.items.enum` extended in this ADR.
+- `agents/roadmaps/` § Block G — the authorising roadmap (archived
+  after merge; this ADR is the durable record).
+- [`.agent-src.uncompressed/rules/skill-quality.md`](../../.agent-src.uncompressed/rules/skill-quality.md)
+  § Senior-Tier Required Structure — the four blocks every senior
+  skill ships independently of spine opt-in.

package/docs/contracts/command-surface-tiers.md

@@ -1,3 +1,8 @@
+---
+stability: beta
+---
+
+
 # Command Surface Tiers
 
 > **Status:** Active. Defines the tiering contract for the two

package/docs/contracts/context-spine.md

@@ -32,8 +32,11 @@ Three failure modes the spine prevents:
 
 ## § 2 — Slot definitions
 
-The spine has **exactly three slots**. Council Q1 verdict (2026-05-05,
-KEEP-3): slot count is locked; extensions require an ADR (§ 5).
+The spine has **three cross-wing slots** plus **per-wing extension
+slots** authorized via ADR. Council Q1 verdict (2026-05-05, KEEP-3)
+locks the cross-wing slot count at 3. Per-wing extensions follow § 5.
+
+### Cross-wing slots (locked at 3)
 
 | Slot | Path under `agents/context-spine/` | Owner | Typical content |
 |---|---|---|---|
@@ -41,6 +44,14 @@ KEEP-3): slot count is locked; extensions require an ADR (§ 5).
 | `team` | `team.md` | RevOps / maintainer wing | Who **maintains** this codebase, how decisions are made, review-routing conventions, cadence (release rhythm, planning ritual). Read by review-routing, finishing-a-development-branch, persona overrides. |
 | `repo` | `repo.md` | Engineering wing | What the codebase **is** at the file-tree level: stack one-liner, primary languages, top-level module map, deploy target. Read by analysis skills, blast-radius-analyzer, project-analysis-* skills. |
 
+### Wing-3 slots (GTM and Growth — added 2026-05-13 per [`adr-gtm-context-spine.md`](adr-gtm-context-spine.md))
+
+| Slot | Path under `agents/context-spine/` | Owner | Typical content |
+|---|---|---|---|
+| `channel-stage` | `channel-stage.md` | GTM / Marketing wing | Which channels the GTM motion uses (awareness · consideration · decision · retention · expansion), per-channel maturity, channel-cost band. Read by `positioning-strategy`, `messaging-architecture`, `gtm-launch`, `editorial-calendar`. |
+| `funnel-stage` | `funnel-stage.md` | Growth / RevOps wing | Funnel topology (top / mid / bottom / activation / retention), per-stage definition, exit-criteria for each. Read by `pipeline-strategy`, `funnel-analysis`, `activation-design`, `onboarding-design`. |
+| `customer-segment` | `customer-segment.md` | Sales / CS wing | ICP, persona-by-segment, ARR-band-by-segment. Read by `ICP`, `pipeline-strategy`, `MEDDIC`, `retention-loops`. |
+
 Slots are markdown files. Each is **≤ 200 lines**; longer means the
 slot is doing two jobs and the author should split or trim. Empty /
 missing slot is allowed — the citing skill MUST handle absence
@@ -64,9 +75,10 @@ Rules:
 
 - The key is **optional**. Senior skills MAY ship without it; the
   default (`[]`) means the skill does not read the spine.
-- Values are restricted to the literal slot names: `product`, `team`,
-  `repo`. Unknown values fail `task lint-skills` with
-  `unknown_context_spine_slot`.
+- Values are restricted to the slot names in § 2: cross-wing
+  (`product`, `team`, `repo`) plus wing-scoped extensions
+  (`channel-stage`, `funnel-stage`, `customer-segment`). Unknown
+  values fail `task lint-skills` with `unknown_context_spine_slot`.
 - Reads MUST be opt-in and explicit. A skill body that says *"reads
   `agents/context-spine/product.md` if present"* without declaring
   the slot in frontmatter is **incorrect** — it bypasses the lint
@@ -91,8 +103,13 @@ file does not break the skill).
 
 ## § 5 — Slot-add policy
 
-Adding a fourth slot is **structurally allowed but procedurally
-expensive**. Two preconditions:
+Two tracks: **cross-wing** (locked at 3, citations-first) and
+**wing-scoped** (per-wing ADR, citations prospective).
+
+### Cross-wing track — citations-first
+
+Adding a fourth **cross-wing** slot (one every wing might read) is
+**structurally allowed but procedurally expensive**. Two preconditions:
 
 1. **Citation evidence.** ≥ 2 shipped senior skills declare the new
    slot in their frontmatter and cite it in the body, with PRs
@@ -103,21 +120,42 @@ expensive**. Two preconditions:
    the migration plan for the existing senior catalog (do they
    declare the new slot, do they ignore it, do they get retrofitted).
 
+### Wing-scoped track — per-wing ADR, prospective citations
+
+A wing may add **its own slots** for cognition specific to that wing
+(e.g. Wing-3 `channel-stage`, `funnel-stage`, `customer-segment`).
+Preconditions:
+
+1. **Per-wing ADR.** One ADR under `docs/contracts/` named
+   `adr-<wing>-context-spine.md` names the slots, the cognition gap,
+   the citing-skill chain in the same iteration, and the off-wing
+   migration plan (off-wing skills do **not** retrofit).
+2. **Prospective citations.** The ADR-naming iteration must ship
+   ≥ 2 skills citing each new slot before the iteration closes.
+   Drafts and roadmap items inside the same iteration **do** count
+   for prospective gating; cross-iteration citations do not.
+
+Existing wing-3 reference: [`adr-gtm-context-spine.md`](adr-gtm-context-spine.md).
+
+### Schema and changelog rules — both tracks
+
 The ADR ships with the schema bump (`scripts/schemas/skill.schema.json`
 extends the `context_spine` enum) and a CHANGELOG entry under
 `### Breaking` if the new enum value tightens an existing skill's
 declaration.
 
-This policy mitigates the slot-sprawl failure mode: "tri-slot locked
-at 3 + ADR-gated growth" is the brake. The ADR is the single growth
-lever; no consumer-side override exists.
+This policy mitigates the slot-sprawl failure mode: "cross-wing
+locked at 3 + wing-scoped via per-wing ADR" is the brake. ADRs are
+the single growth lever; no consumer-side override exists.
 
 ## § 6 — Author checklist
 
 Before shipping a senior skill that opts into the spine:
 
-- [ ] Frontmatter declares `context_spine:` with values from
-      `{product, team, repo}`.
+- [ ] Frontmatter declares `context_spine:` with values from the
+      cross-wing slots (`product`, `team`, `repo`) and/or wing-scoped
+      slots authorized via per-wing ADR (e.g. Wing-3:
+      `channel-stage`, `funnel-stage`, `customer-segment`).
 - [ ] Skill body cites `agents/context-spine/<slot>.md` near the top
       (one link per declared slot).
 - [ ] Procedure handles missing-slot gracefully — falls back to the

package/docs/contracts/cross-wing-handoff.md

@@ -101,10 +101,10 @@ mirrors `lint_skills` (`file:line:reason`).
 
 Three shipped chains across the suite illustrate the contract:
 
-### W3 launch chain — `positioning` → `messaging-architecture` → `gtm-launch`
+### W3 launch chain — `positioning-strategy` → `messaging-architecture` → `gtm-launch`
 
-- `positioning` (H1) owns category framing.
-- `messaging-architecture` (H2) **composes** `positioning` — primary
+- `positioning-strategy` (H1) owns category framing.
+- `messaging-architecture` (H2) **composes** `positioning-strategy` — primary
   message + supporting proofs derive from H1's point-of-view output.
 - `gtm-launch` (H3) **composes** `messaging-architecture` plus
   `release-comms` (unified-senior-roles Block L) — launch sequencing

package/docs/contracts/persona-schema.md

@@ -22,6 +22,7 @@ tiers, a 5-section spine for Core, and a 7-section spine for Specialist
 | `role` | string | yes | human-readable role name |
 | `description` | string | yes | one sentence, ≤ 160 chars |
 | `tier` | enum | yes | `core` \| `specialist` |
+| `wing` | int | optional | `1`\|`2`\|`3`\|`4` — cognition cluster per [`package-self-orientation § The four wings`](package-self-orientation.md#the-four-wings); raises the specialist size cap for denser wings |
 | `mode` | string | optional | advisory link to a role-contract workflow mode |
 | `version` | string | yes | semver; bump on breaking changes |
 | `source` | enum | yes | `package` \| `project` |
@@ -77,13 +78,28 @@ beyond the global line cap).
 
 ## § 4 — Size budgets
 
+Base caps by tier:
+
 | Tier | Section count | Line cap | Rationale |
 |---|---|---|---|
 | `core` | 5 | ≤ 120 | always-loaded, stay lean |
 | `specialist` | 7 | ≤ 100 | opt-in, denser per section |
 
-The line cap is enforced by `lint-skills` against the full file
-including frontmatter and trailing blank line.
+Wing-scoped overrides for the `specialist` tier (Wings 3 and 4 carry
+denser cognition than Wings 1 and 2 — funnel × channel × lifecycle for
+GTM, finance × org × strategy for Money/Ops — so the seven-section
+spine needs more room to land without amputating Workflows):
+
+| Tier | Wing | Line cap |
+|---|---|---|
+| `specialist` | 1 (Engineering) | ≤ 100 |
+| `specialist` | 2 (Product + Foundation) | ≤ 100 |
+| `specialist` | 3 (GTM + Growth) | ≤ 140 |
+| `specialist` | 4 (Money + Strategy + Ops) | ≤ 140 |
+
+Personas without a `wing:` field fall back to the tier baseline. The
+line cap is enforced by `lint-skills` against the full file including
+frontmatter and trailing blank line.
 
 ## § 5 — Schema enforcement
 
@@ -91,8 +107,9 @@ The linter (A2 work) enforces:
 
 - frontmatter shape (table in § 1)
 - tier enum
+- wing enum (when present)
 - required sections per tier (§ 3)
-- size budget per tier (§ 4)
+- size budget per tier — wing override applied when `wing:` is set (§ 4)
 - ≥ 3 bullets in `Unique Questions`
 - `id` matches filename stem
 - description ≤ 160 chars

package/docs/guidelines/gtm-handoff.md

@@ -0,0 +1,114 @@
+# GTM Handoff
+
+Wing-3-specific prose for the three load-bearing senior-skill chains
+in the GTM + Growth cluster. The mechanical contract — initiator →
+delegated(input) → output-artifact, lint rules, worktree boundary —
+lives in [`docs/contracts/cross-wing-handoff.md`](../contracts/cross-wing-handoff.md).
+The cross-wing routing prose (when to hand off at all, L4 / C8
+boundary, decision tree) lives in
+[`docs/guidelines/cross-role-handoff.md`](cross-role-handoff.md).
+This guideline covers **what crosses each Wing-3 boundary**, **what
+the typed artifact looks like**, and **who owns the failure mode
+when the chain breaks**.
+
+Cycle / dangling / tier-mismatch enforcement is not duplicated here —
+`task lint-handoffs` (per cross-wing-handoff § 4) is the mechanical
+gate.
+
+## Chain 1 — brand → channel
+
+Five-step chain that turns a category point-of-view into a shipped
+funnel of channel artifacts. CMO cluster owns every step.
+
+```
+positioning-strategy (H1)
+  → messaging-architecture (H2)
+    → gtm-launch (H3)
+      → editorial-calendar (H4)
+        → content-funnel-design (H5)
+```
+
+| Step | Hands off when | Typed artifact crossing the boundary | Failure-mode owner |
+|---|---|---|---|
+| H1 → H2 | Category framing + opposable-positioning audit locked. | `positioning-statement.md` — "we are X for Y, not Z" + point-of-view paragraph + opposable-positioning matrix. | H1 owns drift: if H2 cannot derive proofs from the statement, H1's POV is too soft. |
+| H2 → H3 | Primary message + supporting proofs + audience-by-message matrix locked. | `messaging-stack.md` — primary message, three supporting proofs, audience-message matrix, narrative beats. | H2 owns drift: if H3's wave-by-wave narrative drifts, the proofs were the wrong shape. |
+| H3 → H4 | Launch sequencing (alpha → beta → GA) + audience-wave logic locked; engineering-readiness signals attached. | `launch-plan.md` — wave list, narrative beats per wave, dependency map, go / no-go signals. | H3 owns drift: missing engineering-readiness signal = H3 shipped a plan that cannot land. |
+| H4 → H5 | Cadence cognition (evergreen vs campaign vs reactive) + beat-mapping locked. | `editorial-calendar.md` — cadence per audience, beat-to-asset map, content-debt ledger. | H4 owns drift: a calendar that does not map beats to funnel stages cannot be designed against. |
+| H5 self-closes | Funnel-stage-to-content-shape mapping + conversion-pathway design locked. | `content-funnel.md` — per-stage asset shapes, conversion pathways, leading indicators. | H5 owns drift: any stage without a content shape is a broken funnel hand-back to H4. |
+
+H5 also **composes** `funnel-analysis` (H14, Chain 3) — the funnel
+diagnostic feeds the conversion-pathway design without H5 absorbing
+funnel-diagnostic cognition.
+
+## Chain 2 — discovery → pipeline
+
+Five-step chain that turns customer research into a forecast-able
+pipeline. Spans the Discovery → RevOps boundary inside Wing 3 and
+hands the forecast call back to the Wing-4 finance-partner.
+
+```
+customer-research (L1, shipped)
+  → ideal-customer-profile artifact
+    → pipeline-strategy (H8)
+      → deal-qualification-meddic (H9)
+        → forecast-accuracy (H10) → forecasting (Wing-4 O2)
+```
+
+| Step | Hands off when | Typed artifact crossing the boundary | Failure-mode owner |
+|---|---|---|---|
+| `customer-research` → H8 | Switch-event interviews + JTBD framing complete; ICP synthesized from verbatims. | `icp.md` — segment definition, switch events, JTBD frame, anti-ICP. | `customer-research` owns drift: an ICP without anti-ICP boundaries leaks into H8 stage definitions. |
+| H8 → H9 | Stage definitions + conversion-rate targets + coverage reasoning locked. | `pipeline-shape.md` — stage list, per-stage conversion target, coverage ratio, leak map. | H8 owns drift: stages H9 cannot disqualify against = H8 stage definitions were not orthogonal. |
+| H9 → H10 | MEDDIC qualification rubric + disqualification heuristics locked. | `qualification-rubric.md` — MEDDIC fields per stage, disqualification triggers, champion-test. | H9 owns drift: forecasts that ignore disqualification heuristics inflate; H9 owns the rubric. |
+| H10 → Wing-4 O2 | Forecast call constructed (commit / best-case / pipeline) against the `forecast-construction-shape` ADR. | `forecast-band.json` — commit value, best-case value, pipeline value, confidence band, retro signature. | **Interface contract owned by O2** (per cross-wing-handoff § 5 / W4 chain): if the ADR drifts, O2 breaks the contract, not H10. |
+
+H10's parallel-development rule (starts after O2-interface ≥ 100 %,
+runs in parallel with O2 implementation) is recorded in the roadmap
+H10 entry and the contract — not duplicated here.
+
+## Chain 3 — funnel → retention
+
+Six-step chain that turns funnel diagnostics into a retention and
+expansion system. Growth PM cluster owns the first three steps,
+Customer Success cluster owns the last three; the H15 → H12 boundary
+crosses the cluster line inside Wing 3.
+
+```
+funnel-analysis (H14)
+  → activation-design (H16)
+    → onboarding-design (H11)
+      → retention-loops (H15)
+        → churn-prevention (H12)
+          → expansion-playbook (H13)
+```
+
+| Step | Hands off when | Typed artifact crossing the boundary | Failure-mode owner |
+|---|---|---|---|
+| H14 → H16 | Funnel-stage diagnostics + leaky-bucket-vs-growth-loop classification + leading-indicator selection locked. | `funnel-diagnostic.md` — per-stage drop-off, loop classification, leading indicators, cohort behavior. | H14 owns drift: an unselected leading indicator leaves H16 without an aha-moment signal. |
+| H16 → H11 | Aha-moment definition + activation-event selection + activation-funnel construction locked. | `activation-spec.md` — aha-moment, activation event, activation-funnel stages, leading-vs-lagging indicators. | H16 owns drift: an activation event H11 cannot instrument is the wrong event. |
+| H11 → H15 | Time-to-first-value reasoning + milestone design + friction audit locked. | `onboarding-flow.md` — milestone list, time-to-value target, friction-audit findings, drop-off diagnosis. | H11 owns drift: milestones without retention hooks force H15 to re-derive habit cognition. |
+| H15 → H12 | Habit-formation reasoning + trigger-action-reward design + loop classification locked. | `retention-loop.md` — trigger / action / reward triple, loop classification, network-vs-single-user signal. | H15 owns drift: a loop that does not surface a health signal leaves H12 without an early warning. |
+| H12 → H13 | Health-score signal design + churn-cause classification + early-warning loop locked. | `churn-signals.md` — health-score schema, churn-cause buckets, early-warning thresholds. | H12 owns drift: a health signal H13 cannot read against expansion triggers blocks NRR cognition. Also feeds **back to Wing-4 forecasting** per the cross-skill map. |
+| H13 self-closes | Account-expansion patterns + upsell-vs-cross-sell reasoning + NRR cognition locked. | `expansion-playbook.md` — expansion patterns, trigger signals, NRR levers. | H13 owns drift: expansion triggers that ignore churn signals double-count growth. |
+
+## Reading the failure-mode column
+
+The column answers one question: **when a downstream skill cannot
+do its job, which upstream skill rewrites its artifact?** The owner
+is the **upstream** skill, not the consumer — drift is always a
+producer-side fix. This mirrors the W4 / W3 forecasting chain in
+the contract (O2 owns the interface; H10 only consumes it).
+
+## See also
+
+- [`docs/contracts/cross-wing-handoff.md`](../contracts/cross-wing-handoff.md)
+  — typed-handoff mechanical contract; `task lint-handoffs` enforces
+  cycles, dangling references, and tier mismatches over the graph.
+- [`docs/guidelines/cross-role-handoff.md`](cross-role-handoff.md)
+  — when to hand off at all, how to phrase the routing, L4 / C8
+  boundary.
+- [`docs/contracts/context-spine.md`](../contracts/context-spine.md)
+  § Wing-3 slots — `channel-stage`, `funnel-stage`,
+  `customer-segment`; every chain step opts into ≥ 1 slot.
+- `agents/roadmaps/` § Block H (archived after merge) — the
+  sixteen H-skills this guideline maps; pending skills appear here
+  as backtick slugs until shipped.

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@event4u/agent-config",
-    "version": "2.7.0",
+    "version": "2.8.0",
     "description": "Shared agent configuration \u2014 skills, rules, commands, guidelines, and templates for AI coding tools",
     "license": "MIT",
     "private": false,

package/scripts/lint_context_spine_usage.py

@@ -31,7 +31,10 @@ SKILL_GLOBS = (
     ".agent-src.uncompressed/skills/**/SKILL.md",
     ".agent-src/skills/**/SKILL.md",
 )
-VALID_SLOTS = ("product", "team", "repo")
+VALID_SLOTS = (
+    "product", "team", "repo",
+    "channel-stage", "funnel-stage", "customer-segment",
+)
 
 CONTEXT_SPINE_PAT = re.compile(
     r"^context_spine:\s*\[([^\]]*)\]\s*$", re.MULTILINE

package/scripts/schemas/persona.schema.json

@@ -26,6 +26,11 @@
       "type": "string",
       "enum": ["core", "specialist"]
     },
+    "wing": {
+      "type": "integer",
+      "enum": [1, 2, 3, 4],
+      "description": "Cognition wing per docs/contracts/package-self-orientation.md § The four wings. Optional. Raises the specialist size cap (persona-schema § 4)."
+    },
     "mode": {
       "type": "string",
       "enum": ["developer", "reviewer", "tester", "product-owner", "incident", "planner"]

package/scripts/schemas/skill.schema.json

@@ -72,9 +72,9 @@
       "uniqueItems": true,
       "items": {
         "type": "string",
-        "enum": ["product", "team", "repo"]
+        "enum": ["product", "team", "repo", "channel-stage", "funnel-stage", "customer-segment"]
       },
-      "description": "Senior-skill opt-in for the tri-slot context spine. Declares which slots under agents/context-spine/ the skill expects to read (product, team, repo). Council Q1 (KEEP-3) locks the slot count at 3; additions require ≥ 2 citing skills + ADR per docs/contracts/context-spine.md § 5."
+      "description": "Senior-skill opt-in for the context spine. Declares which slots under agents/context-spine/ the skill expects to read. Cross-wing slots (product, team, repo) are locked at 3 by council Q1 (KEEP-3); wing-scoped slots (channel-stage, funnel-stage, customer-segment — Wing-3 GTM) follow the per-wing ADR track in docs/contracts/context-spine.md § 5. Wing-3 slots authorized by docs/contracts/adr-gtm-context-spine.md."
     },
     "execution": {
       "type": "object",