# Generated by scripts/generate_pack_manifests.py — DO NOT EDIT BY HAND

# Core

Core framework-neutral artefacts.

- **id**: `core`
- **version**: `5.10.1`
- **owner**: agent-config-maintainer
- **requires**: —
- **artefacts**: 40

## Contexts (4)

- **`artifact-engagement-flow`** — _(no description)_
- **`command-suggestion-flow`** — _(no description)_
- **`no-consolidate-rationale`** — _(no description)_
- **`persona-voice-rubric`** — _(no description)_

## Ghostwriters (1)

- **`fictional-fixture-v1`** — _(no description)_

## Personas (30)

- **`ai-agent`** — The voice of the coding agent that will execute this plan — automation-readiness, missing context, and steps that fail on a fresh clone.
- **`ai-video-technical-director`** — Provider-tuning specialist — maps a scene blueprint to Veo / Kling / OpenAI / Higgsfield / Sora grammar with token caps, aspect ranges, audio flags.
- **`backend-architect`** — The voice that watches service-layer boundaries — module seams, transaction scope, and the contracts a change widens or breaks.
- **`cmo`** — The senior voice that owns the said and the seen — positioning anchored, messaging stacked, launches sequenced, content debt named before it compounds.
- **`contrarian`** — The voice that argues the strongest possible case AGAINST the proposal — to surface hidden assumptions and avoid groupthink.
- **`critical-challenger`** — The voice that refuses easy answers and drags hidden complexity back into the open.
- **`customer-success-lead`** — The senior voice that owns the post-signature value — time-to-first-value falsifiable, churn cause split four ways, expansion pulled, NRR dilution named.
- **`developer`** — The voice of the person who will actually implement this — grounded in edge cases, null values, and the failure modes prose hides.
- **`discovery-lead`** — The senior voice that owns the who and the problem — switch events named, hypotheses falsifiable, themes ranked by distinct people.
- **`eloquent-tamer`** — The voice that audits Eloquent for N+1, query-shape regressions, and ORM idioms that compile cleanly but melt the database.
- **`engineering-manager`** — The senior voice that owns the engineering team's flow — one-on-one cadence anchored, hiring loop calibrated, throughput-vs-morale held in the same hand.
- **`executor`** — The voice that strips the proposal down to its smallest shippable cut — what can be merged on Monday, what is the smallest reversible step, what is the next concrete decision?
- **`expansionist`** — The voice that asks what the proposal becomes when used 10× more than planned — adjacent use cases, second-order effects, surface that grows under its own gravity.
- **`finance-partner`** — The senior voice that owns the cash and the model — unit economics named, runway sized, scenarios stressed, the next 18 months legible.
- **`first-principles`** — The voice that strips away analogy, precedent, and convention to ask what the problem actually requires from physics, math, and stated constraints.
- **`frontend-engineer`** — The voice that audits component lifecycle, reactive state, and the seam between server-rendered markup and client behavior.
- **`growth-pm`** — The senior voice that owns the funnel and the loops — leaky-bucket vs growth-loop classified, activation correlated not assumed, loops closed not hopeful.
- **`hollywood-director`** — Award-winning live-action director — names lens, lighting, blocking, and the negative constraints that separate cinema from stock footage.
- **`outsider`** — The voice from a completely different field — biology, logistics, urban planning, music — that asks how that field has already solved a problem isomorphic to this one.
- **`people-strategist`** — The senior voice that owns the org and the ladder — team shape diagnosed, comp bands defensible, ramp definitions concrete, feedback craft load-bearing.
- **`persona`** — One sentence — the voice this specialist brings; ≤ 160 chars.
- **`product-owner`** — The senior voice that owns the why and the what — outcomes named, AC unfalsifiable, scope decisions on record, trade-offs surfaced before they harden into code.
- **`qa`** — The voice of the tester — failure scenarios, missing assertions, and the gap between 'the code runs' and 'the feature works'.
- **`revops`** — The senior voice that owns the pipeline and the forecast — stage exit criteria evidence-bound, MEDDIC slots filled, forecast falsifiable, leaks named.
- **`revops-maintainer`** — The senior voice that owns contributor lifecycle and package adoption funnel — triage routing, release readiness, positioning anchored in evidence.
- **`security-engineer`** — The voice that reads every diff for OWASP-shaped failure modes, secret leakage, and trust-boundary crossings.
- **`senior-engineer`** — The voice that thinks in years — architecture impact, coupling, blast radius, and decisions that are hard to undo.
- **`stakeholder`** — The voice that asks why now, why this shape, and who pays the cost of the priority this displaces.
- **`strategist`** — The senior voice that owns the second-order moves — build-vs-buy, market-entry, moat, vision, contracts, privacy, data-handling under regulatory constraint.
- **`tech-writer`** — The senior voice that owns the said and the read — release narratives anchored in value, READMEs survivable by strangers, AGENTS.md thin.

## Templatess (1)

- **`proposal.example`** — _(no description)_

## User-Typess (4)

- **`galabau-field-crew`** — Landscape-build crew on site — gloves, mud, no-signal, billable-photo proofs, bilingual plain-German vocabulary.
- **`metalworking-shop`** — Shop-floor metalworking team — job travelers, material certs, machine-time gates, PPE/noise constraints on UI.
- **`truck-driver`** — Commercial truck driver — voice-first, hours-of-service gated, dead-zone tolerant, photo+GPS proof-of-delivery.
- **`user-type`** — One sentence — who this lens simulates and the operational reality they bring; ≤ 160 chars.
