mirror of
https://github.com/magnus919/agent-skills.git
synced 2026-09-11 19:47:12 +03:00
Magnus Hedemarkandfactory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
a315b77bd8
Re-point relative references inside the six non-tailscale/workflow-architect
bundle dirs now that they live one level shallower at the repo root:
- bundle-root SKILL.md/manifest.yaml/README.md: ../../<target> -> ../<target>,
cross-bundle ../../bundles/<x> -> ../<x>
- forward-deployed-engineering references/: ../../../<target> -> ../../<target>
- product-lifecycle references cross-bundle ../../bundles/neckbeard -> ../../neckbeard
- product-lifecycle references/discovery-brief.md prose headings drop bundles/ prefix
- neckbeard eval shell commands bundles/neckbeard/eval -> neckbeard/eval
- production-excellence AGENTS.md depth note updated
- manifest header comments point at ../schemas/bundle-manifest-v1.schema.json
- regenerate docs/lifecycle-capability-matrix.{md,json}
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
184 lines
7.5 KiB
YAML
184 lines
7.5 KiB
YAML
# Bundle manifest (bundle-manifest-v1) — see ../schemas/bundle-manifest-v1.schema.json
|
|
# and docs/bundle-manifest-design.md. Paths are relative to this bundle dir.
|
|
|
|
schema_version: 1
|
|
bundle_name: production-excellence
|
|
|
|
purpose: >-
|
|
Route cross-domain production evidence (readiness, migration, recovery,
|
|
capacity/cost, incident-learning) into a launch or operational decision —
|
|
go, no-go, defer, exception, or escalation — with an accountable owner and a
|
|
post-launch learning path.
|
|
|
|
audience: >-
|
|
Service owners, SRE, release, platform, security, data, and QA teams
|
|
coordinating a production change; agents assembling cross-domain production
|
|
evidence into a defensible launch decision without re-deriving specialist
|
|
runbooks.
|
|
|
|
stages:
|
|
- name: Cross-domain evidence assembly
|
|
skills:
|
|
- ../production-readiness/SKILL.md
|
|
- ../migration-engineering/SKILL.md
|
|
- ../resilience-and-recovery/SKILL.md
|
|
- ../capacity-and-cost-engineering/SKILL.md
|
|
- ../incident-learning/SKILL.md
|
|
- name: Gate evaluation
|
|
skills:
|
|
- ../production-readiness/SKILL.md
|
|
- ../site-reliability-engineering/SKILL.md
|
|
- ../verification-methodology/SKILL.md
|
|
- ../qa-methodology/SKILL.md
|
|
- name: Operational handoff
|
|
skills:
|
|
- ../release-engineering/SKILL.md
|
|
- ../platform-engineering/SKILL.md
|
|
- ../secure-software-engineering/SKILL.md
|
|
- ../data-engineering/SKILL.md
|
|
- name: Post-launch learning
|
|
skills:
|
|
- ../incident-learning/SKILL.md
|
|
|
|
included_skills:
|
|
- ../production-readiness/SKILL.md
|
|
- ../migration-engineering/SKILL.md
|
|
- ../resilience-and-recovery/SKILL.md
|
|
- ../capacity-and-cost-engineering/SKILL.md
|
|
- ../incident-learning/SKILL.md
|
|
- ../site-reliability-engineering/SKILL.md
|
|
- ../release-engineering/SKILL.md
|
|
- ../platform-engineering/SKILL.md
|
|
- ../secure-software-engineering/SKILL.md
|
|
- ../data-engineering/SKILL.md
|
|
- ../qa-methodology/SKILL.md
|
|
- ../verification-methodology/SKILL.md
|
|
|
|
prerequisites:
|
|
- artifact: Readiness review evidence packet (risk-scaled, 11 categories)
|
|
skill: ../production-readiness/SKILL.md
|
|
- artifact: Migration plan, compatibility windows, and reconciliation evidence
|
|
skill: ../migration-engineering/SKILL.md
|
|
- artifact: Resilience and recovery evidence (RTO/RPO, restore tests, game days)
|
|
skill: ../resilience-and-recovery/SKILL.md
|
|
- artifact: Capacity and cost model evidence (demand, scaling, unit cost)
|
|
skill: ../capacity-and-cost-engineering/SKILL.md
|
|
- artifact: Incident history, causal hypotheses, and verified-closure records
|
|
skill: ../incident-learning/SKILL.md
|
|
- artifact: SLO and error-budget status
|
|
skill: ../site-reliability-engineering/SKILL.md
|
|
- artifact: Release plan and rollback strategy
|
|
skill: ../release-engineering/SKILL.md
|
|
|
|
outputs:
|
|
- gate-decision
|
|
- operational-handoff-record
|
|
- accountable-owner-record
|
|
- evidence-gap-register
|
|
|
|
handoffs:
|
|
- to: incident-learning
|
|
artifact: operational-handoff-record
|
|
note: >-
|
|
Post-launch incidents (SLO degradations, unexpected failures, capacity
|
|
breaches) route back to incident-learning with launch context; verified
|
|
closure is required for follow-up items.
|
|
- to: product-lifecycle-learning
|
|
artifact: operational-handoff-record
|
|
note: >-
|
|
Expected outcomes recorded in the handoff (SLO targets, capacity
|
|
assumptions, cost projections) feed expected-vs-observed comparison at
|
|
the handoff review cadence.
|
|
- to: agent-production-operations
|
|
artifact: gate-decision
|
|
note: >-
|
|
Readiness outcomes (go/no-go/defer/exception) gate agent authority
|
|
expansion when the runtime control plane is in use.
|
|
- to: service owner
|
|
artifact: accountable-owner-record
|
|
note: >-
|
|
Every gate outcome names an accountable owner and records the evidence
|
|
supporting it; no gate passes on a bare checklist.
|
|
|
|
conflicts:
|
|
- skill: ../production-readiness/SKILL.md
|
|
with: product-lifecycle
|
|
guidance: >-
|
|
Both bundles include production-readiness. This bundle owns the launch
|
|
gate decision; product-lifecycle routes phase 6 delivery handoff. Load
|
|
the bundle matching the active decision context, never both at once.
|
|
- skill: ../production-readiness/SKILL.md
|
|
with: agent-production-operations
|
|
guidance: >-
|
|
agent-production-operations consumes readiness outcomes as authority-
|
|
gating inputs. Readiness reviews and go/no-go/defer/exception outcomes
|
|
are produced here and consumed there.
|
|
- skill: ../release-engineering/SKILL.md
|
|
with: product-lifecycle
|
|
guidance: >-
|
|
Release engineering is shared. Route by context: gate-entry release
|
|
evidence (this bundle) versus lifecycle delivery handoff
|
|
(product-lifecycle).
|
|
- skill: ../release-engineering/SKILL.md
|
|
with: agent-production-operations
|
|
guidance: >-
|
|
Release engineering is shared. Route by context: launch-gate release
|
|
plans (this bundle) versus agent staged-rollout planning
|
|
(agent-production-operations).
|
|
- skill: ../site-reliability-engineering/SKILL.md
|
|
with: product-lifecycle
|
|
guidance: >-
|
|
SRE is shared. This bundle routes to it for gate-entry SLO/error-budget
|
|
evidence; product-lifecycle routes to it for delivery reliability.
|
|
- skill: ../site-reliability-engineering/SKILL.md
|
|
with: agent-production-operations
|
|
guidance: >-
|
|
SRE is shared. This bundle uses it for gate-entry reliability evidence;
|
|
agent-production-operations uses it for runtime latency/cost budgets
|
|
and incident handoff. Incident command stays with SRE in both cases.
|
|
- skill: ../secure-software-engineering/SKILL.md
|
|
with: product-lifecycle
|
|
guidance: >-
|
|
Security engineering is shared. Route by context: security evidence for
|
|
launch gates (this bundle) versus trust-boundary work in lifecycle
|
|
phases (product-lifecycle).
|
|
- skill: ../secure-software-engineering/SKILL.md
|
|
with: agent-production-operations
|
|
guidance: >-
|
|
Security engineering is shared. Route by context: launch-gate security
|
|
evidence (this bundle) versus agent authority contracts and disablement
|
|
security (agent-production-operations).
|
|
- skill: ../platform-engineering/SKILL.md
|
|
with: product-lifecycle
|
|
guidance: >-
|
|
Platform engineering is shared. Route by context: gate-entry platform
|
|
evidence (this bundle) versus lifecycle delivery handoff
|
|
(product-lifecycle).
|
|
- skill: ../platform-engineering/SKILL.md
|
|
with: agent-production-operations
|
|
guidance: >-
|
|
Platform engineering is shared. Route by context: launch-gate platform
|
|
evidence (this bundle) versus agent sandboxing and tool-execution
|
|
isolation (agent-production-operations).
|
|
- skill: ../incident-learning/SKILL.md
|
|
with: agent-production-operations
|
|
guidance: >-
|
|
Both bundles consume incident-learning records. This bundle uses
|
|
incident history as gate-entry evidence; agent-production-operations
|
|
consumes verified-closure records as escalation and disablement inputs.
|
|
- skill: ../qa-methodology/SKILL.md
|
|
with: product-lifecycle
|
|
guidance: >-
|
|
QA methodology is shared. Route by context: launch verification evidence
|
|
(this bundle) versus lifecycle phase 6 quality gates
|
|
(product-lifecycle).
|
|
- skill: ../verification-methodology/SKILL.md
|
|
with: product-lifecycle
|
|
guidance: >-
|
|
Verification methodology is shared. This bundle uses it for boundary
|
|
labeling of launch evidence; product-lifecycle uses it at every phase
|
|
gate.
|
|
|
|
eval_suite:
|
|
- evals/evals.json
|