mirror of
https://github.com/magnus919/agent-skills.git
synced 2026-09-11 19:47:12 +03:00
feat(flatten): repoint lifecycle capability matrix tooling to flat layout
Update gen-lifecycle-matrix.rb and validate-lifecycle-matrix.rb to drop all
hardcoded bundles/ path references after the directory flatten:
- CANONICAL_BUNDLES now selects canonical bundles via */manifest.yaml (the
8 bundle dirs) instead of */SKILL.md (which would match every top-level
skill); keeps the 8-bundle invariant required by the validation contract.
- source strings, manifest paths, fallback frontmatter, and base dirs use
<name>/... at the repo root; the top-level JSON key stays "bundles".
- validate-lifecycle-matrix.rb re-anchors NESTED_HELPER_PATTERN to
%r{(?:^|/)skills/} so nested helpers (tailscale/skills/*,
workflow-architect/skills/*) are still detected in the catalogs, and
canonical_bundles matches the generator's */manifest.yaml glob.
- align the two matrix tests in test-validate-bundles.rb: canonical bundles
are manifest-having dirs (a manifest-less top-level skill is not a row),
and the missing-row rejection targets the demo manifest bundle.
- regenerate docs/lifecycle-capability-matrix.{md,json}.
gen check mode: "is current (8 bundles)"; validate:
"Validated lifecycle capability matrix (8 bundle(s)): complete, traceable, and current."
test-validate-bundles.rb: 14 runs, 307 assertions, 0 failures.
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
This commit is contained in:
Magnus Hedemark
co-authored by
factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
parent
7b6f26f077
commit
42447b23eb
@@ -5,15 +5,15 @@
|
||||
{
|
||||
"name": "agent-production-operations",
|
||||
"derivation": "manifest",
|
||||
"source": "bundles/agent-production-operations/manifest.yaml",
|
||||
"source": "agent-production-operations/manifest.yaml",
|
||||
"fields": {
|
||||
"purpose": {
|
||||
"value": "Operate an evaluated agent with tools and authority in production through a runtime control plane covering versioning, staged rollout, fallback, cost and latency budgets, tool health, human escalation, disablement, and trace-to-eval feedback.",
|
||||
"source": "bundles/agent-production-operations/manifest.yaml#/purpose"
|
||||
"source": "agent-production-operations/manifest.yaml#/purpose"
|
||||
},
|
||||
"audience": {
|
||||
"value": "Agent operators and platform teams running evaluated agents with tools and delegated authority in production; agents that need the runtime control decisions between evaluation, release, SRE, security, and platform specialists.",
|
||||
"source": "bundles/agent-production-operations/manifest.yaml#/audience"
|
||||
"source": "agent-production-operations/manifest.yaml#/audience"
|
||||
},
|
||||
"stages": {
|
||||
"value": [
|
||||
@@ -61,7 +61,7 @@
|
||||
]
|
||||
}
|
||||
],
|
||||
"source": "bundles/agent-production-operations/manifest.yaml#/stages"
|
||||
"source": "agent-production-operations/manifest.yaml#/stages"
|
||||
},
|
||||
"included_skills": {
|
||||
"value": [
|
||||
@@ -74,7 +74,7 @@
|
||||
"../../incident-learning/SKILL.md",
|
||||
"../../privacy-engineering/SKILL.md"
|
||||
],
|
||||
"source": "bundles/agent-production-operations/manifest.yaml#/included_skills"
|
||||
"source": "agent-production-operations/manifest.yaml#/included_skills"
|
||||
},
|
||||
"prerequisites": {
|
||||
"value": [
|
||||
@@ -95,7 +95,7 @@
|
||||
"skill": "../../release-engineering/SKILL.md"
|
||||
}
|
||||
],
|
||||
"source": "bundles/agent-production-operations/manifest.yaml#/prerequisites"
|
||||
"source": "agent-production-operations/manifest.yaml#/prerequisites"
|
||||
},
|
||||
"outputs": {
|
||||
"value": [
|
||||
@@ -106,7 +106,7 @@
|
||||
"trace-to-eval-feedback-loop",
|
||||
"disablement-record"
|
||||
],
|
||||
"source": "bundles/agent-production-operations/manifest.yaml#/outputs"
|
||||
"source": "agent-production-operations/manifest.yaml#/outputs"
|
||||
},
|
||||
"handoffs": {
|
||||
"value": [
|
||||
@@ -131,7 +131,7 @@
|
||||
"note": "Disablement revokes credentials, removes the agent from routing/load-balancing, and records the reason, timestamp, and authorizing evidence."
|
||||
}
|
||||
],
|
||||
"source": "bundles/agent-production-operations/manifest.yaml#/handoffs"
|
||||
"source": "agent-production-operations/manifest.yaml#/handoffs"
|
||||
},
|
||||
"conflicts": {
|
||||
"value": [
|
||||
@@ -196,28 +196,28 @@
|
||||
"guidance": "Privacy engineering is shared. This bundle routes to it for trace scrubbing and user-data-access grants; product-lifecycle routes to it for PII, consent, retention, and data flows in any phase."
|
||||
}
|
||||
],
|
||||
"source": "bundles/agent-production-operations/manifest.yaml#/conflicts"
|
||||
"source": "agent-production-operations/manifest.yaml#/conflicts"
|
||||
},
|
||||
"eval_suite": {
|
||||
"value": [
|
||||
"evals/evals.json"
|
||||
],
|
||||
"source": "bundles/agent-production-operations/manifest.yaml#/eval_suite"
|
||||
"source": "agent-production-operations/manifest.yaml#/eval_suite"
|
||||
}
|
||||
}
|
||||
},
|
||||
{
|
||||
"name": "forward-deployed-engineering",
|
||||
"derivation": "manifest",
|
||||
"source": "bundles/forward-deployed-engineering/manifest.yaml",
|
||||
"source": "forward-deployed-engineering/manifest.yaml",
|
||||
"fields": {
|
||||
"purpose": {
|
||||
"value": "Carry an embedded technical engagement from ambiguous stakeholder need through discovery, framing, hypothesis, build, evaluation, deployment, adoption, measurement, and generalization while preserving decision rights, evidence, handoffs, and reusable field learning.",
|
||||
"source": "bundles/forward-deployed-engineering/manifest.yaml#/purpose"
|
||||
"source": "forward-deployed-engineering/manifest.yaml#/purpose"
|
||||
},
|
||||
"audience": {
|
||||
"value": "Technical leads and agents embedded across stakeholder discovery, implementation, production fit, adoption, and measurable workflow outcomes; this is a continuity layer that routes specialist methods rather than replacing them.",
|
||||
"source": "bundles/forward-deployed-engineering/manifest.yaml#/audience"
|
||||
"source": "forward-deployed-engineering/manifest.yaml#/audience"
|
||||
},
|
||||
"stages": {
|
||||
"value": [
|
||||
@@ -293,7 +293,7 @@
|
||||
]
|
||||
}
|
||||
],
|
||||
"source": "bundles/forward-deployed-engineering/manifest.yaml#/stages"
|
||||
"source": "forward-deployed-engineering/manifest.yaml#/stages"
|
||||
},
|
||||
"included_skills": {
|
||||
"value": [
|
||||
@@ -319,7 +319,7 @@
|
||||
"../../privacy-engineering/SKILL.md",
|
||||
"../../secure-software-engineering/SKILL.md"
|
||||
],
|
||||
"source": "bundles/forward-deployed-engineering/manifest.yaml#/included_skills"
|
||||
"source": "forward-deployed-engineering/manifest.yaml#/included_skills"
|
||||
},
|
||||
"prerequisites": {
|
||||
"value": [
|
||||
@@ -330,7 +330,7 @@
|
||||
"artifact": "Authority to conduct non-destructive discovery with access to relevant stakeholders or workflow evidence"
|
||||
}
|
||||
],
|
||||
"source": "bundles/forward-deployed-engineering/manifest.yaml#/prerequisites"
|
||||
"source": "forward-deployed-engineering/manifest.yaml#/prerequisites"
|
||||
},
|
||||
"outputs": {
|
||||
"value": [
|
||||
@@ -345,7 +345,7 @@
|
||||
"productization-record",
|
||||
"field-learning-record"
|
||||
],
|
||||
"source": "bundles/forward-deployed-engineering/manifest.yaml#/outputs"
|
||||
"source": "forward-deployed-engineering/manifest.yaml#/outputs"
|
||||
},
|
||||
"handoffs": {
|
||||
"value": [
|
||||
@@ -375,7 +375,7 @@
|
||||
"note": "The engagement closes with observed outcomes, unresolved uncertainty, and a durable transfer or follow-up path."
|
||||
}
|
||||
],
|
||||
"source": "bundles/forward-deployed-engineering/manifest.yaml#/handoffs"
|
||||
"source": "forward-deployed-engineering/manifest.yaml#/handoffs"
|
||||
},
|
||||
"conflicts": {
|
||||
"value": [
|
||||
@@ -575,28 +575,28 @@
|
||||
"guidance": "This bundle uses prioritization only to support engagement generalization; product-lifecycle owns product prioritization and portfolio methods."
|
||||
}
|
||||
],
|
||||
"source": "bundles/forward-deployed-engineering/manifest.yaml#/conflicts"
|
||||
"source": "forward-deployed-engineering/manifest.yaml#/conflicts"
|
||||
},
|
||||
"eval_suite": {
|
||||
"value": [
|
||||
"evals/evals.json"
|
||||
],
|
||||
"source": "bundles/forward-deployed-engineering/manifest.yaml#/eval_suite"
|
||||
"source": "forward-deployed-engineering/manifest.yaml#/eval_suite"
|
||||
}
|
||||
}
|
||||
},
|
||||
{
|
||||
"name": "neckbeard",
|
||||
"derivation": "manifest",
|
||||
"source": "bundles/neckbeard/manifest.yaml",
|
||||
"source": "neckbeard/manifest.yaml",
|
||||
"fields": {
|
||||
"purpose": {
|
||||
"value": "A disciplined SDLC delivery operating model for non-trivial software change — fix, build, refactor, review, verify, or release — that routes the work through framing, discovery, design, implementation, review, verification, delivery, and learning, choosing the smallest *safe* intervention, proving it at the real delivery boundary, and leaving an inspectable evidence ledger.",
|
||||
"source": "bundles/neckbeard/manifest.yaml#/purpose"
|
||||
"source": "neckbeard/manifest.yaml#/purpose"
|
||||
},
|
||||
"audience": {
|
||||
"value": "Software engineers and agents delivering non-trivial software changes (bug fixes, features, refactors, reviews, releases) that need a bounded, stage-aware path to a defensible 'done' with recorded evidence; teams running issue-to-PR change-request journeys with gates and an authorized release.",
|
||||
"source": "bundles/neckbeard/manifest.yaml#/audience"
|
||||
"source": "neckbeard/manifest.yaml#/audience"
|
||||
},
|
||||
"stages": {
|
||||
"value": [
|
||||
@@ -654,7 +654,7 @@
|
||||
]
|
||||
}
|
||||
],
|
||||
"source": "bundles/neckbeard/manifest.yaml#/stages"
|
||||
"source": "neckbeard/manifest.yaml#/stages"
|
||||
},
|
||||
"included_skills": {
|
||||
"value": [
|
||||
@@ -672,7 +672,7 @@
|
||||
"../../release-engineering/SKILL.md",
|
||||
"../../site-reliability-engineering/SKILL.md"
|
||||
],
|
||||
"source": "bundles/neckbeard/manifest.yaml#/included_skills"
|
||||
"source": "neckbeard/manifest.yaml#/included_skills"
|
||||
},
|
||||
"prerequisites": {
|
||||
"value": [
|
||||
@@ -688,7 +688,7 @@
|
||||
"skill": "../../verification-methodology/SKILL.md"
|
||||
}
|
||||
],
|
||||
"source": "bundles/neckbeard/manifest.yaml#/prerequisites"
|
||||
"source": "neckbeard/manifest.yaml#/prerequisites"
|
||||
},
|
||||
"outputs": {
|
||||
"value": [
|
||||
@@ -699,7 +699,7 @@
|
||||
"verification-report",
|
||||
"release-record"
|
||||
],
|
||||
"source": "bundles/neckbeard/manifest.yaml#/outputs"
|
||||
"source": "neckbeard/manifest.yaml#/outputs"
|
||||
},
|
||||
"handoffs": {
|
||||
"value": [
|
||||
@@ -724,7 +724,7 @@
|
||||
"note": "Each run emits a compact evidence record (intent, inspected artifacts, assumptions, rejected alternatives, checks run, observed outputs, unverified boundaries) that carries learning into the next change."
|
||||
}
|
||||
],
|
||||
"source": "bundles/neckbeard/manifest.yaml#/handoffs"
|
||||
"source": "neckbeard/manifest.yaml#/handoffs"
|
||||
},
|
||||
"conflicts": {
|
||||
"value": [
|
||||
@@ -809,28 +809,28 @@
|
||||
"guidance": "SRE is shared. Route by context: change-level reliability (neckbeard) versus agent runtime latency/cost budgets and incident handoff (agent-production-operations)."
|
||||
}
|
||||
],
|
||||
"source": "bundles/neckbeard/manifest.yaml#/conflicts"
|
||||
"source": "neckbeard/manifest.yaml#/conflicts"
|
||||
},
|
||||
"eval_suite": {
|
||||
"value": [
|
||||
"evals/evals.json"
|
||||
],
|
||||
"source": "bundles/neckbeard/manifest.yaml#/eval_suite"
|
||||
"source": "neckbeard/manifest.yaml#/eval_suite"
|
||||
}
|
||||
}
|
||||
},
|
||||
{
|
||||
"name": "product-lifecycle",
|
||||
"derivation": "manifest",
|
||||
"source": "bundles/product-lifecycle/manifest.yaml",
|
||||
"source": "product-lifecycle/manifest.yaml",
|
||||
"fields": {
|
||||
"purpose": {
|
||||
"value": "Route a product through its full lifecycle — discovery, strategy and portfolio choice, roadmap, UX and requirements, experimentation, delivery handoff, adoption, success, and lifecycle review — by composing existing specialist product skills with phase-entry evidence, handoff artifacts, and escalation rules.",
|
||||
"source": "bundles/product-lifecycle/manifest.yaml#/purpose"
|
||||
"source": "product-lifecycle/manifest.yaml#/purpose"
|
||||
},
|
||||
"audience": {
|
||||
"value": "Product managers, product operations, and portfolio teams navigating a product across multiple lifecycle phases; agents that need to know which specialist skill to load at each phase and what evidence to hand off to the next phase.",
|
||||
"source": "bundles/product-lifecycle/manifest.yaml#/audience"
|
||||
"source": "product-lifecycle/manifest.yaml#/audience"
|
||||
},
|
||||
"stages": {
|
||||
"value": [
|
||||
@@ -893,7 +893,7 @@
|
||||
]
|
||||
}
|
||||
],
|
||||
"source": "bundles/product-lifecycle/manifest.yaml#/stages"
|
||||
"source": "product-lifecycle/manifest.yaml#/stages"
|
||||
},
|
||||
"included_skills": {
|
||||
"value": [
|
||||
@@ -924,7 +924,7 @@
|
||||
"../../platform-engineering/SKILL.md",
|
||||
"../../bundles/neckbeard/SKILL.md"
|
||||
],
|
||||
"source": "bundles/product-lifecycle/manifest.yaml#/included_skills"
|
||||
"source": "product-lifecycle/manifest.yaml#/included_skills"
|
||||
},
|
||||
"prerequisites": {
|
||||
"value": [
|
||||
@@ -952,7 +952,7 @@
|
||||
"skill": "../../product-experimentation/SKILL.md"
|
||||
}
|
||||
],
|
||||
"source": "bundles/product-lifecycle/manifest.yaml#/prerequisites"
|
||||
"source": "product-lifecycle/manifest.yaml#/prerequisites"
|
||||
},
|
||||
"outputs": {
|
||||
"value": [
|
||||
@@ -970,7 +970,7 @@
|
||||
"outcome-review",
|
||||
"lifecycle-decision"
|
||||
],
|
||||
"source": "bundles/product-lifecycle/manifest.yaml#/outputs"
|
||||
"source": "product-lifecycle/manifest.yaml#/outputs"
|
||||
},
|
||||
"handoffs": {
|
||||
"value": [
|
||||
@@ -995,7 +995,7 @@
|
||||
"note": "Phase 9 records the continue/improve/harvest/pivot/pause/retire decision and retained learning in the learning loop."
|
||||
}
|
||||
],
|
||||
"source": "bundles/product-lifecycle/manifest.yaml#/handoffs"
|
||||
"source": "product-lifecycle/manifest.yaml#/handoffs"
|
||||
},
|
||||
"conflicts": {
|
||||
"value": [
|
||||
@@ -1065,28 +1065,28 @@
|
||||
"guidance": "Verification methodology is shared. This bundle uses it at every phase gate for evidence; production-excellence uses it for boundary labeling of launch evidence."
|
||||
}
|
||||
],
|
||||
"source": "bundles/product-lifecycle/manifest.yaml#/conflicts"
|
||||
"source": "product-lifecycle/manifest.yaml#/conflicts"
|
||||
},
|
||||
"eval_suite": {
|
||||
"value": [
|
||||
"evals/evals.json"
|
||||
],
|
||||
"source": "bundles/product-lifecycle/manifest.yaml#/eval_suite"
|
||||
"source": "product-lifecycle/manifest.yaml#/eval_suite"
|
||||
}
|
||||
}
|
||||
},
|
||||
{
|
||||
"name": "production-excellence",
|
||||
"derivation": "manifest",
|
||||
"source": "bundles/production-excellence/manifest.yaml",
|
||||
"source": "production-excellence/manifest.yaml",
|
||||
"fields": {
|
||||
"purpose": {
|
||||
"value": "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.",
|
||||
"source": "bundles/production-excellence/manifest.yaml#/purpose"
|
||||
"source": "production-excellence/manifest.yaml#/purpose"
|
||||
},
|
||||
"audience": {
|
||||
"value": "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.",
|
||||
"source": "bundles/production-excellence/manifest.yaml#/audience"
|
||||
"source": "production-excellence/manifest.yaml#/audience"
|
||||
},
|
||||
"stages": {
|
||||
"value": [
|
||||
@@ -1125,7 +1125,7 @@
|
||||
]
|
||||
}
|
||||
],
|
||||
"source": "bundles/production-excellence/manifest.yaml#/stages"
|
||||
"source": "production-excellence/manifest.yaml#/stages"
|
||||
},
|
||||
"included_skills": {
|
||||
"value": [
|
||||
@@ -1142,7 +1142,7 @@
|
||||
"../../qa-methodology/SKILL.md",
|
||||
"../../verification-methodology/SKILL.md"
|
||||
],
|
||||
"source": "bundles/production-excellence/manifest.yaml#/included_skills"
|
||||
"source": "production-excellence/manifest.yaml#/included_skills"
|
||||
},
|
||||
"prerequisites": {
|
||||
"value": [
|
||||
@@ -1175,7 +1175,7 @@
|
||||
"skill": "../../release-engineering/SKILL.md"
|
||||
}
|
||||
],
|
||||
"source": "bundles/production-excellence/manifest.yaml#/prerequisites"
|
||||
"source": "production-excellence/manifest.yaml#/prerequisites"
|
||||
},
|
||||
"outputs": {
|
||||
"value": [
|
||||
@@ -1184,7 +1184,7 @@
|
||||
"accountable-owner-record",
|
||||
"evidence-gap-register"
|
||||
],
|
||||
"source": "bundles/production-excellence/manifest.yaml#/outputs"
|
||||
"source": "production-excellence/manifest.yaml#/outputs"
|
||||
},
|
||||
"handoffs": {
|
||||
"value": [
|
||||
@@ -1209,7 +1209,7 @@
|
||||
"note": "Every gate outcome names an accountable owner and records the evidence supporting it; no gate passes on a bare checklist."
|
||||
}
|
||||
],
|
||||
"source": "bundles/production-excellence/manifest.yaml#/handoffs"
|
||||
"source": "production-excellence/manifest.yaml#/handoffs"
|
||||
},
|
||||
"conflicts": {
|
||||
"value": [
|
||||
@@ -1279,28 +1279,28 @@
|
||||
"guidance": "Verification methodology is shared. This bundle uses it for boundary labeling of launch evidence; product-lifecycle uses it at every phase gate."
|
||||
}
|
||||
],
|
||||
"source": "bundles/production-excellence/manifest.yaml#/conflicts"
|
||||
"source": "production-excellence/manifest.yaml#/conflicts"
|
||||
},
|
||||
"eval_suite": {
|
||||
"value": [
|
||||
"evals/evals.json"
|
||||
],
|
||||
"source": "bundles/production-excellence/manifest.yaml#/eval_suite"
|
||||
"source": "production-excellence/manifest.yaml#/eval_suite"
|
||||
}
|
||||
}
|
||||
},
|
||||
{
|
||||
"name": "research-and-vault",
|
||||
"derivation": "manifest",
|
||||
"source": "bundles/research-and-vault/manifest.yaml",
|
||||
"source": "research-and-vault/manifest.yaml",
|
||||
"fields": {
|
||||
"purpose": {
|
||||
"value": "Chain web research, atomic extraction, and durable knowledge capture into a repeatable research-to-note workflow: capture source URLs and dates before interpretation, extract independent atomic claims before synthesis, and write the durable note only after source coverage and gaps are explicit.",
|
||||
"source": "bundles/research-and-vault/manifest.yaml#/purpose"
|
||||
"source": "research-and-vault/manifest.yaml#/purpose"
|
||||
},
|
||||
"audience": {
|
||||
"value": "Agents and knowledge workers that repeatedly need the full research-to-note sequence (web research, atomic extraction, durable capture) and want a stable order of operations with a clear handoff artifact instead of ad-hoc steps; not for single lookups or single notes, which route to the domain skill directly.",
|
||||
"source": "bundles/research-and-vault/manifest.yaml#/audience"
|
||||
"source": "research-and-vault/manifest.yaml#/audience"
|
||||
},
|
||||
"stages": {
|
||||
"value": [
|
||||
@@ -1329,13 +1329,13 @@
|
||||
]
|
||||
}
|
||||
],
|
||||
"source": "bundles/research-and-vault/manifest.yaml#/stages"
|
||||
"source": "research-and-vault/manifest.yaml#/stages"
|
||||
},
|
||||
"included_skills": {
|
||||
"value": [
|
||||
"../../research-methodology/SKILL.md"
|
||||
],
|
||||
"source": "bundles/research-and-vault/manifest.yaml#/included_skills"
|
||||
"source": "research-and-vault/manifest.yaml#/included_skills"
|
||||
},
|
||||
"prerequisites": {
|
||||
"value": [
|
||||
@@ -1344,7 +1344,7 @@
|
||||
"skill": "../../research-methodology/SKILL.md"
|
||||
}
|
||||
],
|
||||
"source": "bundles/research-and-vault/manifest.yaml#/prerequisites"
|
||||
"source": "research-and-vault/manifest.yaml#/prerequisites"
|
||||
},
|
||||
"outputs": {
|
||||
"value": [
|
||||
@@ -1352,7 +1352,7 @@
|
||||
"atomic-claim-extract",
|
||||
"durable-note"
|
||||
],
|
||||
"source": "bundles/research-and-vault/manifest.yaml#/outputs"
|
||||
"source": "research-and-vault/manifest.yaml#/outputs"
|
||||
},
|
||||
"handoffs": {
|
||||
"value": [
|
||||
@@ -1372,34 +1372,34 @@
|
||||
"note": "The finished durable note reports its output path and any unresolved gaps in source coverage."
|
||||
}
|
||||
],
|
||||
"source": "bundles/research-and-vault/manifest.yaml#/handoffs"
|
||||
"source": "research-and-vault/manifest.yaml#/handoffs"
|
||||
},
|
||||
"conflicts": {
|
||||
"value": [
|
||||
|
||||
],
|
||||
"source": "bundles/research-and-vault/manifest.yaml#/conflicts"
|
||||
"source": "research-and-vault/manifest.yaml#/conflicts"
|
||||
},
|
||||
"eval_suite": {
|
||||
"value": [
|
||||
"evals/evals.json"
|
||||
],
|
||||
"source": "bundles/research-and-vault/manifest.yaml#/eval_suite"
|
||||
"source": "research-and-vault/manifest.yaml#/eval_suite"
|
||||
}
|
||||
}
|
||||
},
|
||||
{
|
||||
"name": "tailscale",
|
||||
"derivation": "manifest",
|
||||
"source": "bundles/tailscale/manifest.yaml",
|
||||
"source": "tailscale/manifest.yaml",
|
||||
"fields": {
|
||||
"purpose": {
|
||||
"value": "Operate a self-hosted Tailscale/Headscale ecosystem end to end: deploy and manage a Headscale control server, configure Tailscale clients, define ACL policy, manage node lifecycle, advertise subnet routes and exit nodes, operate DERP relays, and back up, restore, or migrate the control plane.",
|
||||
"source": "bundles/tailscale/manifest.yaml#/purpose"
|
||||
"source": "tailscale/manifest.yaml#/purpose"
|
||||
},
|
||||
"audience": {
|
||||
"value": "Platform and homelab operators running self-hosted Tailscale/Headscale infrastructure; agents that need to know which sub-skill to load for deploy, policy, client, node, routing, DERP, or backup tasks in a WireGuard mesh.",
|
||||
"source": "bundles/tailscale/manifest.yaml#/audience"
|
||||
"source": "tailscale/manifest.yaml#/audience"
|
||||
},
|
||||
"stages": {
|
||||
"value": [
|
||||
@@ -1446,7 +1446,7 @@
|
||||
]
|
||||
}
|
||||
],
|
||||
"source": "bundles/tailscale/manifest.yaml#/stages"
|
||||
"source": "tailscale/manifest.yaml#/stages"
|
||||
},
|
||||
"included_skills": {
|
||||
"value": [
|
||||
@@ -1458,7 +1458,7 @@
|
||||
"skills/headscale-derp/SKILL.md",
|
||||
"skills/headscale-backup/SKILL.md"
|
||||
],
|
||||
"source": "bundles/tailscale/manifest.yaml#/included_skills"
|
||||
"source": "tailscale/manifest.yaml#/included_skills"
|
||||
},
|
||||
"prerequisites": {
|
||||
"value": [
|
||||
@@ -1475,7 +1475,7 @@
|
||||
"skill": "skills/headscale-deploy/SKILL.md"
|
||||
}
|
||||
],
|
||||
"source": "bundles/tailscale/manifest.yaml#/prerequisites"
|
||||
"source": "tailscale/manifest.yaml#/prerequisites"
|
||||
},
|
||||
"outputs": {
|
||||
"value": [
|
||||
@@ -1487,7 +1487,7 @@
|
||||
"backup-archive",
|
||||
"restored-instance"
|
||||
],
|
||||
"source": "bundles/tailscale/manifest.yaml#/outputs"
|
||||
"source": "tailscale/manifest.yaml#/outputs"
|
||||
},
|
||||
"handoffs": {
|
||||
"value": [
|
||||
@@ -1512,34 +1512,34 @@
|
||||
"note": "The backup archive is the disaster-recovery artifact for the tailnet; keep it off the control server host."
|
||||
}
|
||||
],
|
||||
"source": "bundles/tailscale/manifest.yaml#/handoffs"
|
||||
"source": "tailscale/manifest.yaml#/handoffs"
|
||||
},
|
||||
"conflicts": {
|
||||
"value": [
|
||||
|
||||
],
|
||||
"source": "bundles/tailscale/manifest.yaml#/conflicts"
|
||||
"source": "tailscale/manifest.yaml#/conflicts"
|
||||
},
|
||||
"eval_suite": {
|
||||
"value": [
|
||||
"evals/evals.json"
|
||||
],
|
||||
"source": "bundles/tailscale/manifest.yaml#/eval_suite"
|
||||
"source": "tailscale/manifest.yaml#/eval_suite"
|
||||
}
|
||||
}
|
||||
},
|
||||
{
|
||||
"name": "workflow-architect",
|
||||
"derivation": "manifest",
|
||||
"source": "bundles/workflow-architect/manifest.yaml",
|
||||
"source": "workflow-architect/manifest.yaml",
|
||||
"fields": {
|
||||
"purpose": {
|
||||
"value": "Discover a user's actual workflow through active interrogation or passive observation, then generate a tailored Agent Skills bundle that encodes it as loadable skills with trigger conditions, a decision map, a manifest, and an optional kanban board — turning a session that feels aimless into structure.",
|
||||
"source": "bundles/workflow-architect/manifest.yaml#/purpose"
|
||||
"source": "workflow-architect/manifest.yaml#/purpose"
|
||||
},
|
||||
"audience": {
|
||||
"value": "Users and agents that want to formalize how they work — understand their own process, encode it as trigger-driven skills they can reuse, or share it with collaborators. Not for single factual questions or tasks already owned by a more specific skill.",
|
||||
"source": "bundles/workflow-architect/manifest.yaml#/audience"
|
||||
"source": "workflow-architect/manifest.yaml#/audience"
|
||||
},
|
||||
"stages": {
|
||||
"value": [
|
||||
@@ -1562,7 +1562,7 @@
|
||||
]
|
||||
}
|
||||
],
|
||||
"source": "bundles/workflow-architect/manifest.yaml#/stages"
|
||||
"source": "workflow-architect/manifest.yaml#/stages"
|
||||
},
|
||||
"included_skills": {
|
||||
"value": [
|
||||
@@ -1570,7 +1570,7 @@
|
||||
"skills/observer/SKILL.md",
|
||||
"skills/bundle-builder/SKILL.md"
|
||||
],
|
||||
"source": "bundles/workflow-architect/manifest.yaml#/included_skills"
|
||||
"source": "workflow-architect/manifest.yaml#/included_skills"
|
||||
},
|
||||
"prerequisites": {
|
||||
"value": [
|
||||
@@ -1583,7 +1583,7 @@
|
||||
"skill": "skills/interviewer/SKILL.md"
|
||||
}
|
||||
],
|
||||
"source": "bundles/workflow-architect/manifest.yaml#/prerequisites"
|
||||
"source": "workflow-architect/manifest.yaml#/prerequisites"
|
||||
},
|
||||
"outputs": {
|
||||
"value": [
|
||||
@@ -1592,7 +1592,7 @@
|
||||
"manifest",
|
||||
"kanban-board"
|
||||
],
|
||||
"source": "bundles/workflow-architect/manifest.yaml#/outputs"
|
||||
"source": "workflow-architect/manifest.yaml#/outputs"
|
||||
},
|
||||
"handoffs": {
|
||||
"value": [
|
||||
@@ -1617,19 +1617,19 @@
|
||||
"note": "The kanban board is included only when the workflow follows a predictable linear path where WIP limits and lane transitions add value."
|
||||
}
|
||||
],
|
||||
"source": "bundles/workflow-architect/manifest.yaml#/handoffs"
|
||||
"source": "workflow-architect/manifest.yaml#/handoffs"
|
||||
},
|
||||
"conflicts": {
|
||||
"value": [
|
||||
|
||||
],
|
||||
"source": "bundles/workflow-architect/manifest.yaml#/conflicts"
|
||||
"source": "workflow-architect/manifest.yaml#/conflicts"
|
||||
},
|
||||
"eval_suite": {
|
||||
"value": [
|
||||
"evals/evals.json"
|
||||
],
|
||||
"source": "bundles/workflow-architect/manifest.yaml#/eval_suite"
|
||||
"source": "workflow-architect/manifest.yaml#/eval_suite"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
+247
-247
@@ -10,12 +10,12 @@ the migration path, and the field definitions. Regenerate with
|
||||
|
||||
| Bundle | Purpose | Audience | Lifecycle stages | Included skills | Prerequisites | Outputs | Handoffs | Conflicts | Eval suite |
|
||||
|---|---|---|---|---|---|---|---|---|---|
|
||||
| agent-production-operations | Operate an evaluated agent with tools and authority in production through a runtime control plane covering versioning, staged rollout, fallback, cost and latency budgets, tool health, human escalation, disablement, and trace-to-eval feedback. | Agent operators and platform teams running evaluated agents with tools and delegated authority in production; agents that need the runtime control decisions between evaluation, release, SRE, security, and platform specialists. | Contract definition → Versioning and rollout planning → Staged rollout → Runtime monitoring → Trace-to-eval feedback → Learning and disablement | agent-evals-and-observability, release-engineering, site-reliability-engineering, secure-software-engineering, platform-engineering, production-readiness, incident-learning, privacy-engineering | Agent evaluation results and observability instrumentation(agent-evals-and-observability); Production-readiness evidence (go/no-go/defer/exception outcomes)(production-readiness); Incident-learning records (verified closure, follow-up work map)(incident-learning); Release pipeline and artifact promotion baseline(release-engineering) | agent-production-contract, runtime-control-plan, staged-rollout-plan, tool-authority-health-record, trace-to-eval-feedback-loop, disablement-record | staged-rollout-plan → release-engineering; trace-to-eval-feedback-loop → agent-evals-and-observability; tool-authority-health-record → incident-learning; disablement-record → human operator | production-readiness (with production-excellence); production-readiness (with product-lifecycle); release-engineering (with production-excellence); release-engineering (with product-lifecycle); site-reliability-engineering (with production-excellence); site-reliability-engineering (with product-lifecycle); secure-software-engineering (with production-excellence); secure-software-engineering (with product-lifecycle); platform-engineering (with production-excellence); platform-engineering (with product-lifecycle); incident-learning (with production-excellence); privacy-engineering (with product-lifecycle) | evals/evals.json |
|
||||
| forward-deployed-engineering | Carry an embedded technical engagement from ambiguous stakeholder need through discovery, framing, hypothesis, build, evaluation, deployment, adoption, measurement, and generalization while preserving decision rights, evidence, handoffs, and reusable field learning. | Technical leads and agents embedded across stakeholder discovery, implementation, production fit, adoption, and measurable workflow outcomes; this is a continuity layer that routes specialist methods rather than replacing them. | Discover → Frame → Hypothesize → Build → Evaluate → Deploy → Adopt → Measure → Generalize | product-discovery, product-design-and-ux, product-experimentation, agent-evals-and-observability, implementation-planning, backend-engineering, frontend-engineering, data-engineering, qa-methodology, verification-methodology, production-readiness, release-engineering, platform-engineering, remote-systems-administration, product-adoption, product-analytics-and-measurement, site-reliability-engineering, product-lifecycle-learning, product-methodology, privacy-engineering, secure-software-engineering | Stakeholder request or observed workflow opportunity and a named accountable lead; Authority to conduct non-destructive discovery with access to relevant stakeholders or workflow evidence | engagement-charter, stakeholder-workflow-map, assumptions-decisions-risks-ledger, engagement-status, stage-handoff-record, evaluation-and-release-decision, adoption-scorecard, outcome-measurement-record, productization-record, field-learning-record | stage-handoff-record → next lifecycle stage; evaluation-and-release-decision → production-readiness and release specialists; adoption-scorecard → adoption and measurement specialists; productization-record → product, platform, or receiving delivery owner; field-learning-record → engagement sponsor | product-discovery (with product-lifecycle); product-discovery (with research-and-vault); product-experimentation (with product-lifecycle); implementation-planning (with product-lifecycle); production-readiness (with production-excellence); production-readiness (with product-lifecycle); release-engineering (with production-excellence); release-engineering (with product-lifecycle); platform-engineering (with production-excellence); platform-engineering (with product-lifecycle); platform-engineering (with agent-production-operations); secure-software-engineering (with production-excellence); secure-software-engineering (with product-lifecycle); secure-software-engineering (with agent-production-operations); privacy-engineering (with product-lifecycle); privacy-engineering (with agent-production-operations); qa-methodology (with production-excellence); qa-methodology (with product-lifecycle); verification-methodology (with production-excellence); verification-methodology (with product-lifecycle); site-reliability-engineering (with production-excellence); site-reliability-engineering (with product-lifecycle); site-reliability-engineering (with agent-production-operations); data-engineering (with production-excellence); product-adoption (with product-lifecycle); product-analytics-and-measurement (with product-lifecycle); product-lifecycle-learning (with product-lifecycle); agent-evals-and-observability (with agent-production-operations); production-readiness (with agent-production-operations); release-engineering (with agent-production-operations); product-design-and-ux (with neckbeard); product-discovery (with neckbeard); qa-methodology (with neckbeard); release-engineering (with neckbeard); secure-software-engineering (with neckbeard); site-reliability-engineering (with neckbeard); verification-methodology (with neckbeard); product-design-and-ux (with product-lifecycle); product-methodology (with product-lifecycle) | evals/evals.json |
|
||||
| neckbeard | A disciplined SDLC delivery operating model for non-trivial software change — fix, build, refactor, review, verify, or release — that routes the work through framing, discovery, design, implementation, review, verification, delivery, and learning, choosing the smallest *safe* intervention, proving it at the real delivery boundary, and leaving an inspectable evidence ledger. | Software engineers and agents delivering non-trivial software changes (bug fixes, features, refactors, reviews, releases) that need a bounded, stage-aware path to a defensible 'done' with recorded evidence; teams running issue-to-PR change-request journeys with gates and an authorized release. | Intake and framing → Current-state discovery → Design → Specification → Test planning → Implementation → Review and verification → Readiness and release | product-discovery, software-architecture-analysis, systematic-debugging, api-design-and-evolution, product-design-and-ux, spec-driven-development, qa-methodology, secure-software-engineering, web-accessibility, verification-methodology, technical-documentation, release-engineering, site-reliability-engineering | A non-trivial change request, issue, or task with a verifiable contract; Current-state evidence (repository, tests, config, recent history)(software-architecture-analysis); Change contract and evidence ledger entries(verification-methodology) | change-contract, evidence-ledger, delivery-packet, implementation-plan, verification-report, release-record | verification-report → verification-methodology; release-record → release-engineering; delivery-packet → human reviewer; evidence-ledger → next change (via evidence ledger) | product-discovery (with product-lifecycle); product-design-and-ux (with product-lifecycle); spec-driven-development (with product-lifecycle); qa-methodology (with product-lifecycle); qa-methodology (with production-excellence); secure-software-engineering (with product-lifecycle); secure-software-engineering (with production-excellence); secure-software-engineering (with agent-production-operations); verification-methodology (with product-lifecycle); verification-methodology (with production-excellence); release-engineering (with product-lifecycle); release-engineering (with production-excellence); release-engineering (with agent-production-operations); site-reliability-engineering (with product-lifecycle); site-reliability-engineering (with production-excellence); site-reliability-engineering (with agent-production-operations) | evals/evals.json |
|
||||
| product-lifecycle | Route a product through its full lifecycle — discovery, strategy and portfolio choice, roadmap, UX and requirements, experimentation, delivery handoff, adoption, success, and lifecycle review — by composing existing specialist product skills with phase-entry evidence, handoff artifacts, and escalation rules. | Product managers, product operations, and portfolio teams navigating a product across multiple lifecycle phases; agents that need to know which specialist skill to load at each phase and what evidence to hand off to the next phase. | Discovery → Strategy and portfolio choice → Roadmap → UX and requirements → Experimentation → Delivery handoff → Adoption → Success → Lifecycle review | product-discovery, product-strategy, strategy-frameworks, product-roadmapping-and-portfolio, product-design-and-ux, product-experimentation, implementation-planning, production-readiness, release-engineering, product-adoption, product-analytics-and-measurement, conditional-customer-success, product-lifecycle-learning, product-methodology, product-operations-and-governance, financial-modeling, go-to-market, data-scientist, spec-driven-development, privacy-engineering, secure-software-engineering, verification-methodology, qa-methodology, site-reliability-engineering, platform-engineering, neckbeard | Product idea, market signal, or stakeholder request; Problem statement and discovery log(product-discovery); Strategic assessment and portfolio decision(product-strategy); Roadmap entry and bet record(product-roadmapping-and-portfolio); UX contracts and acceptance criteria(product-design-and-ux); Experiment readout and assumptions register(product-experimentation) | lifecycle-evidence-ledger, problem-statement, strategic-assessment, roadmap-entry, interface-contracts, experiment-brief, implementation-plan, readiness-verdict, release-plan, adoption-plan, outcome-measurement, outcome-review, lifecycle-decision | readiness-verdict → production-excellence bundle; implementation-plan → delivery team; lifecycle-evidence-ledger → next phase (via evidence ledger); lifecycle-decision → product-lifecycle-learning | production-readiness (with production-excellence); production-readiness (with agent-production-operations); release-engineering (with production-excellence); release-engineering (with agent-production-operations); site-reliability-engineering (with production-excellence); site-reliability-engineering (with agent-production-operations); secure-software-engineering (with production-excellence); secure-software-engineering (with agent-production-operations); platform-engineering (with production-excellence); platform-engineering (with agent-production-operations); privacy-engineering (with agent-production-operations); qa-methodology (with production-excellence); verification-methodology (with production-excellence) | evals/evals.json |
|
||||
| production-excellence | 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. | 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. | Cross-domain evidence assembly → Gate evaluation → Operational handoff → Post-launch learning | production-readiness, migration-engineering, resilience-and-recovery, capacity-and-cost-engineering, incident-learning, site-reliability-engineering, release-engineering, platform-engineering, secure-software-engineering, data-engineering, qa-methodology, verification-methodology | Readiness review evidence packet (risk-scaled, 11 categories)(production-readiness); Migration plan, compatibility windows, and reconciliation evidence(migration-engineering); Resilience and recovery evidence (RTO/RPO, restore tests, game days)(resilience-and-recovery); Capacity and cost model evidence (demand, scaling, unit cost)(capacity-and-cost-engineering); Incident history, causal hypotheses, and verified-closure records(incident-learning); SLO and error-budget status(site-reliability-engineering); Release plan and rollback strategy(release-engineering) | gate-decision, operational-handoff-record, accountable-owner-record, evidence-gap-register | operational-handoff-record → incident-learning; operational-handoff-record → product-lifecycle-learning; gate-decision → agent-production-operations; accountable-owner-record → service owner | production-readiness (with product-lifecycle); production-readiness (with agent-production-operations); release-engineering (with product-lifecycle); release-engineering (with agent-production-operations); site-reliability-engineering (with product-lifecycle); site-reliability-engineering (with agent-production-operations); secure-software-engineering (with product-lifecycle); secure-software-engineering (with agent-production-operations); platform-engineering (with product-lifecycle); platform-engineering (with agent-production-operations); incident-learning (with agent-production-operations); qa-methodology (with product-lifecycle); verification-methodology (with product-lifecycle) | evals/evals.json |
|
||||
| research-and-vault | Chain web research, atomic extraction, and durable knowledge capture into a repeatable research-to-note workflow: capture source URLs and dates before interpretation, extract independent atomic claims before synthesis, and write the durable note only after source coverage and gaps are explicit. | Agents and knowledge workers that repeatedly need the full research-to-note sequence (web research, atomic extraction, durable capture) and want a stable order of operations with a clear handoff artifact instead of ad-hoc steps; not for single lookups or single notes, which route to the domain skill directly. | Web research → Source capture → Atomic extraction → Synthesis and durable capture | research-methodology | A research question or topic and access to web-research tooling(research-methodology) | source-capture-record, atomic-claim-extract, durable-note | source-capture-record → research-methodology; atomic-claim-extract → research-methodology; durable-note → user | none declared | evals/evals.json |
|
||||
| agent-production-operations | Operate an evaluated agent with tools and authority in production through a runtime control plane covering versioning, staged rollout, fallback, cost and latency budgets, tool health, human escalation, disablement, and trace-to-eval feedback. | Agent operators and platform teams running evaluated agents with tools and delegated authority in production; agents that need the runtime control decisions between evaluation, release, SRE, security, and platform specialists. | Contract definition → Versioning and rollout planning → Staged rollout → Runtime monitoring → Trace-to-eval feedback → Learning and disablement | ../../agent-evals-and-observability/SKILL.md, ../../release-engineering/SKILL.md, ../../site-reliability-engineering/SKILL.md, ../../secure-software-engineering/SKILL.md, ../../platform-engineering/SKILL.md, ../../production-readiness/SKILL.md, ../../incident-learning/SKILL.md, ../../privacy-engineering/SKILL.md | Agent evaluation results and observability instrumentation(../../agent-evals-and-observability/SKILL.md); Production-readiness evidence (go/no-go/defer/exception outcomes)(../../production-readiness/SKILL.md); Incident-learning records (verified closure, follow-up work map)(../../incident-learning/SKILL.md); Release pipeline and artifact promotion baseline(../../release-engineering/SKILL.md) | agent-production-contract, runtime-control-plan, staged-rollout-plan, tool-authority-health-record, trace-to-eval-feedback-loop, disablement-record | staged-rollout-plan → release-engineering; trace-to-eval-feedback-loop → agent-evals-and-observability; tool-authority-health-record → incident-learning; disablement-record → human operator | ../../production-readiness/SKILL.md (with production-excellence); ../../production-readiness/SKILL.md (with product-lifecycle); ../../release-engineering/SKILL.md (with production-excellence); ../../release-engineering/SKILL.md (with product-lifecycle); ../../site-reliability-engineering/SKILL.md (with production-excellence); ../../site-reliability-engineering/SKILL.md (with product-lifecycle); ../../secure-software-engineering/SKILL.md (with production-excellence); ../../secure-software-engineering/SKILL.md (with product-lifecycle); ../../platform-engineering/SKILL.md (with production-excellence); ../../platform-engineering/SKILL.md (with product-lifecycle); ../../incident-learning/SKILL.md (with production-excellence); ../../privacy-engineering/SKILL.md (with product-lifecycle) | evals/evals.json |
|
||||
| forward-deployed-engineering | Carry an embedded technical engagement from ambiguous stakeholder need through discovery, framing, hypothesis, build, evaluation, deployment, adoption, measurement, and generalization while preserving decision rights, evidence, handoffs, and reusable field learning. | Technical leads and agents embedded across stakeholder discovery, implementation, production fit, adoption, and measurable workflow outcomes; this is a continuity layer that routes specialist methods rather than replacing them. | Discover → Frame → Hypothesize → Build → Evaluate → Deploy → Adopt → Measure → Generalize | ../../product-discovery/SKILL.md, ../../product-design-and-ux/SKILL.md, ../../product-experimentation/SKILL.md, ../../agent-evals-and-observability/SKILL.md, ../../implementation-planning/SKILL.md, ../../backend-engineering/SKILL.md, ../../frontend-engineering/SKILL.md, ../../data-engineering/SKILL.md, ../../qa-methodology/SKILL.md, ../../verification-methodology/SKILL.md, ../../production-readiness/SKILL.md, ../../release-engineering/SKILL.md, ../../platform-engineering/SKILL.md, ../../remote-systems-administration/SKILL.md, ../../product-adoption/SKILL.md, ../../product-analytics-and-measurement/SKILL.md, ../../site-reliability-engineering/SKILL.md, ../../product-lifecycle-learning/SKILL.md, ../../product-methodology/SKILL.md, ../../privacy-engineering/SKILL.md, ../../secure-software-engineering/SKILL.md | Stakeholder request or observed workflow opportunity and a named accountable lead; Authority to conduct non-destructive discovery with access to relevant stakeholders or workflow evidence | engagement-charter, stakeholder-workflow-map, assumptions-decisions-risks-ledger, engagement-status, stage-handoff-record, evaluation-and-release-decision, adoption-scorecard, outcome-measurement-record, productization-record, field-learning-record | stage-handoff-record → next lifecycle stage; evaluation-and-release-decision → production-readiness and release specialists; adoption-scorecard → adoption and measurement specialists; productization-record → product, platform, or receiving delivery owner; field-learning-record → engagement sponsor | ../../product-discovery/SKILL.md (with product-lifecycle); ../../product-discovery/SKILL.md (with research-and-vault); ../../product-experimentation/SKILL.md (with product-lifecycle); ../../implementation-planning/SKILL.md (with product-lifecycle); ../../production-readiness/SKILL.md (with production-excellence); ../../production-readiness/SKILL.md (with product-lifecycle); ../../release-engineering/SKILL.md (with production-excellence); ../../release-engineering/SKILL.md (with product-lifecycle); ../../platform-engineering/SKILL.md (with production-excellence); ../../platform-engineering/SKILL.md (with product-lifecycle); ../../platform-engineering/SKILL.md (with agent-production-operations); ../../secure-software-engineering/SKILL.md (with production-excellence); ../../secure-software-engineering/SKILL.md (with product-lifecycle); ../../secure-software-engineering/SKILL.md (with agent-production-operations); ../../privacy-engineering/SKILL.md (with product-lifecycle); ../../privacy-engineering/SKILL.md (with agent-production-operations); ../../qa-methodology/SKILL.md (with production-excellence); ../../qa-methodology/SKILL.md (with product-lifecycle); ../../verification-methodology/SKILL.md (with production-excellence); ../../verification-methodology/SKILL.md (with product-lifecycle); ../../site-reliability-engineering/SKILL.md (with production-excellence); ../../site-reliability-engineering/SKILL.md (with product-lifecycle); ../../site-reliability-engineering/SKILL.md (with agent-production-operations); ../../data-engineering/SKILL.md (with production-excellence); ../../product-adoption/SKILL.md (with product-lifecycle); ../../product-analytics-and-measurement/SKILL.md (with product-lifecycle); ../../product-lifecycle-learning/SKILL.md (with product-lifecycle); ../../agent-evals-and-observability/SKILL.md (with agent-production-operations); ../../production-readiness/SKILL.md (with agent-production-operations); ../../release-engineering/SKILL.md (with agent-production-operations); ../../product-design-and-ux/SKILL.md (with neckbeard); ../../product-discovery/SKILL.md (with neckbeard); ../../qa-methodology/SKILL.md (with neckbeard); ../../release-engineering/SKILL.md (with neckbeard); ../../secure-software-engineering/SKILL.md (with neckbeard); ../../site-reliability-engineering/SKILL.md (with neckbeard); ../../verification-methodology/SKILL.md (with neckbeard); ../../product-design-and-ux/SKILL.md (with product-lifecycle); ../../product-methodology/SKILL.md (with product-lifecycle) | evals/evals.json |
|
||||
| neckbeard | A disciplined SDLC delivery operating model for non-trivial software change — fix, build, refactor, review, verify, or release — that routes the work through framing, discovery, design, implementation, review, verification, delivery, and learning, choosing the smallest *safe* intervention, proving it at the real delivery boundary, and leaving an inspectable evidence ledger. | Software engineers and agents delivering non-trivial software changes (bug fixes, features, refactors, reviews, releases) that need a bounded, stage-aware path to a defensible 'done' with recorded evidence; teams running issue-to-PR change-request journeys with gates and an authorized release. | Intake and framing → Current-state discovery → Design → Specification → Test planning → Implementation → Review and verification → Readiness and release | ../../product-discovery/SKILL.md, ../../software-architecture-analysis/SKILL.md, ../../systematic-debugging/SKILL.md, ../../api-design-and-evolution/SKILL.md, ../../product-design-and-ux/SKILL.md, ../../spec-driven-development/SKILL.md, ../../qa-methodology/SKILL.md, ../../secure-software-engineering/SKILL.md, ../../web-accessibility/SKILL.md, ../../verification-methodology/SKILL.md, ../../technical-documentation/SKILL.md, ../../release-engineering/SKILL.md, ../../site-reliability-engineering/SKILL.md | A non-trivial change request, issue, or task with a verifiable contract; Current-state evidence (repository, tests, config, recent history)(../../software-architecture-analysis/SKILL.md); Change contract and evidence ledger entries(../../verification-methodology/SKILL.md) | change-contract, evidence-ledger, delivery-packet, implementation-plan, verification-report, release-record | verification-report → verification-methodology; release-record → release-engineering; delivery-packet → human reviewer; evidence-ledger → next change (via evidence ledger) | ../../product-discovery/SKILL.md (with product-lifecycle); ../../product-design-and-ux/SKILL.md (with product-lifecycle); ../../spec-driven-development/SKILL.md (with product-lifecycle); ../../qa-methodology/SKILL.md (with product-lifecycle); ../../qa-methodology/SKILL.md (with production-excellence); ../../secure-software-engineering/SKILL.md (with product-lifecycle); ../../secure-software-engineering/SKILL.md (with production-excellence); ../../secure-software-engineering/SKILL.md (with agent-production-operations); ../../verification-methodology/SKILL.md (with product-lifecycle); ../../verification-methodology/SKILL.md (with production-excellence); ../../release-engineering/SKILL.md (with product-lifecycle); ../../release-engineering/SKILL.md (with production-excellence); ../../release-engineering/SKILL.md (with agent-production-operations); ../../site-reliability-engineering/SKILL.md (with product-lifecycle); ../../site-reliability-engineering/SKILL.md (with production-excellence); ../../site-reliability-engineering/SKILL.md (with agent-production-operations) | evals/evals.json |
|
||||
| product-lifecycle | Route a product through its full lifecycle — discovery, strategy and portfolio choice, roadmap, UX and requirements, experimentation, delivery handoff, adoption, success, and lifecycle review — by composing existing specialist product skills with phase-entry evidence, handoff artifacts, and escalation rules. | Product managers, product operations, and portfolio teams navigating a product across multiple lifecycle phases; agents that need to know which specialist skill to load at each phase and what evidence to hand off to the next phase. | Discovery → Strategy and portfolio choice → Roadmap → UX and requirements → Experimentation → Delivery handoff → Adoption → Success → Lifecycle review | ../../product-discovery/SKILL.md, ../../product-strategy/SKILL.md, ../../strategy-frameworks/SKILL.md, ../../product-roadmapping-and-portfolio/SKILL.md, ../../product-design-and-ux/SKILL.md, ../../product-experimentation/SKILL.md, ../../implementation-planning/SKILL.md, ../../production-readiness/SKILL.md, ../../release-engineering/SKILL.md, ../../product-adoption/SKILL.md, ../../product-analytics-and-measurement/SKILL.md, ../../conditional-customer-success/SKILL.md, ../../product-lifecycle-learning/SKILL.md, ../../product-methodology/SKILL.md, ../../product-operations-and-governance/SKILL.md, ../../financial-modeling/SKILL.md, ../../go-to-market/SKILL.md, ../../data-scientist/SKILL.md, ../../spec-driven-development/SKILL.md, ../../privacy-engineering/SKILL.md, ../../secure-software-engineering/SKILL.md, ../../verification-methodology/SKILL.md, ../../qa-methodology/SKILL.md, ../../site-reliability-engineering/SKILL.md, ../../platform-engineering/SKILL.md, ../../bundles/neckbeard/SKILL.md | Product idea, market signal, or stakeholder request; Problem statement and discovery log(../../product-discovery/SKILL.md); Strategic assessment and portfolio decision(../../product-strategy/SKILL.md); Roadmap entry and bet record(../../product-roadmapping-and-portfolio/SKILL.md); UX contracts and acceptance criteria(../../product-design-and-ux/SKILL.md); Experiment readout and assumptions register(../../product-experimentation/SKILL.md) | lifecycle-evidence-ledger, problem-statement, strategic-assessment, roadmap-entry, interface-contracts, experiment-brief, implementation-plan, readiness-verdict, release-plan, adoption-plan, outcome-measurement, outcome-review, lifecycle-decision | readiness-verdict → production-excellence bundle; implementation-plan → delivery team; lifecycle-evidence-ledger → next phase (via evidence ledger); lifecycle-decision → product-lifecycle-learning | ../../production-readiness/SKILL.md (with production-excellence); ../../production-readiness/SKILL.md (with agent-production-operations); ../../release-engineering/SKILL.md (with production-excellence); ../../release-engineering/SKILL.md (with agent-production-operations); ../../site-reliability-engineering/SKILL.md (with production-excellence); ../../site-reliability-engineering/SKILL.md (with agent-production-operations); ../../secure-software-engineering/SKILL.md (with production-excellence); ../../secure-software-engineering/SKILL.md (with agent-production-operations); ../../platform-engineering/SKILL.md (with production-excellence); ../../platform-engineering/SKILL.md (with agent-production-operations); ../../privacy-engineering/SKILL.md (with agent-production-operations); ../../qa-methodology/SKILL.md (with production-excellence); ../../verification-methodology/SKILL.md (with production-excellence) | evals/evals.json |
|
||||
| production-excellence | 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. | 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. | Cross-domain evidence assembly → Gate evaluation → Operational handoff → Post-launch learning | ../../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 | Readiness review evidence packet (risk-scaled, 11 categories)(../../production-readiness/SKILL.md); Migration plan, compatibility windows, and reconciliation evidence(../../migration-engineering/SKILL.md); Resilience and recovery evidence (RTO/RPO, restore tests, game days)(../../resilience-and-recovery/SKILL.md); Capacity and cost model evidence (demand, scaling, unit cost)(../../capacity-and-cost-engineering/SKILL.md); Incident history, causal hypotheses, and verified-closure records(../../incident-learning/SKILL.md); SLO and error-budget status(../../site-reliability-engineering/SKILL.md); Release plan and rollback strategy(../../release-engineering/SKILL.md) | gate-decision, operational-handoff-record, accountable-owner-record, evidence-gap-register | operational-handoff-record → incident-learning; operational-handoff-record → product-lifecycle-learning; gate-decision → agent-production-operations; accountable-owner-record → service owner | ../../production-readiness/SKILL.md (with product-lifecycle); ../../production-readiness/SKILL.md (with agent-production-operations); ../../release-engineering/SKILL.md (with product-lifecycle); ../../release-engineering/SKILL.md (with agent-production-operations); ../../site-reliability-engineering/SKILL.md (with product-lifecycle); ../../site-reliability-engineering/SKILL.md (with agent-production-operations); ../../secure-software-engineering/SKILL.md (with product-lifecycle); ../../secure-software-engineering/SKILL.md (with agent-production-operations); ../../platform-engineering/SKILL.md (with product-lifecycle); ../../platform-engineering/SKILL.md (with agent-production-operations); ../../incident-learning/SKILL.md (with agent-production-operations); ../../qa-methodology/SKILL.md (with product-lifecycle); ../../verification-methodology/SKILL.md (with product-lifecycle) | evals/evals.json |
|
||||
| research-and-vault | Chain web research, atomic extraction, and durable knowledge capture into a repeatable research-to-note workflow: capture source URLs and dates before interpretation, extract independent atomic claims before synthesis, and write the durable note only after source coverage and gaps are explicit. | Agents and knowledge workers that repeatedly need the full research-to-note sequence (web research, atomic extraction, durable capture) and want a stable order of operations with a clear handoff artifact instead of ad-hoc steps; not for single lookups or single notes, which route to the domain skill directly. | Web research → Source capture → Atomic extraction → Synthesis and durable capture | ../../research-methodology/SKILL.md | A research question or topic and access to web-research tooling(../../research-methodology/SKILL.md) | source-capture-record, atomic-claim-extract, durable-note | source-capture-record → research-methodology; atomic-claim-extract → research-methodology; durable-note → user | none declared | evals/evals.json |
|
||||
| tailscale | Operate a self-hosted Tailscale/Headscale ecosystem end to end: deploy and manage a Headscale control server, configure Tailscale clients, define ACL policy, manage node lifecycle, advertise subnet routes and exit nodes, operate DERP relays, and back up, restore, or migrate the control plane. | Platform and homelab operators running self-hosted Tailscale/Headscale infrastructure; agents that need to know which sub-skill to load for deploy, policy, client, node, routing, DERP, or backup tasks in a WireGuard mesh. | Deploy control server → Policy → Client connectivity → Node lifecycle → Routing → DERP relays → Backup and restore | headscale-deploy, tailnet-policy, tailscale-client, headscale-node-lifecycle, headscale-routing, headscale-derp, headscale-backup | A Linux host and install target for the Headscale control server(headscale-deploy); HEADSCALE_URL and HEADSCALE_API_KEY credentials(headscale-deploy); A running Headscale instance with the headscale CLI available(headscale-deploy) | headscale-server, tailnet-policy, registered-nodes, routed-networks, derp-map, backup-archive, restored-instance | headscale-server → tailnet-policy; headscale-server → headscale-node-lifecycle; headscale-server → headscale-backup; backup-archive → user | none declared | evals/evals.json |
|
||||
| workflow-architect | Discover a user's actual workflow through active interrogation or passive observation, then generate a tailored Agent Skills bundle that encodes it as loadable skills with trigger conditions, a decision map, a manifest, and an optional kanban board — turning a session that feels aimless into structure. | Users and agents that want to formalize how they work — understand their own process, encode it as trigger-driven skills they can reuse, or share it with collaborators. Not for single factual questions or tasks already owned by a more specific skill. | Active interview → Passive observation → Synthesis and generation | interviewer, observer, bundle-builder | Session context with enough turns for observation (or user answers for interview)(observer); Convergence on workflow phases, branching signals, and tool preferences(interviewer) | skills-bundle, decision-map, manifest, kanban-board | skills-bundle → user; decision-map → user; manifest → user; kanban-board → user | none declared | evals/evals.json |
|
||||
|
||||
@@ -23,30 +23,30 @@ the migration path, and the field definitions. Regenerate with
|
||||
|
||||
### agent-production-operations
|
||||
|
||||
- Derivation: `manifest` — source: `bundles/agent-production-operations/manifest.yaml`
|
||||
- Derivation: `manifest` — source: `agent-production-operations/manifest.yaml`
|
||||
- **Purpose:** Operate an evaluated agent with tools and authority in production through a runtime control plane covering versioning, staged rollout, fallback, cost and latency budgets, tool health, human escalation, disablement, and trace-to-eval feedback.
|
||||
- **Audience:** Agent operators and platform teams running evaluated agents with tools and delegated authority in production; agents that need the runtime control decisions between evaluation, release, SRE, security, and platform specialists.
|
||||
- **Stages (ordered):**
|
||||
1. Contract definition — agent-evals-and-observability (`../../agent-evals-and-observability/SKILL.md`), production-readiness (`../../production-readiness/SKILL.md`), incident-learning (`../../incident-learning/SKILL.md`)
|
||||
2. Versioning and rollout planning — release-engineering (`../../release-engineering/SKILL.md`), platform-engineering (`../../platform-engineering/SKILL.md`)
|
||||
3. Staged rollout — platform-engineering (`../../platform-engineering/SKILL.md`), site-reliability-engineering (`../../site-reliability-engineering/SKILL.md`)
|
||||
4. Runtime monitoring — site-reliability-engineering (`../../site-reliability-engineering/SKILL.md`), secure-software-engineering (`../../secure-software-engineering/SKILL.md`)
|
||||
5. Trace-to-eval feedback — agent-evals-and-observability (`../../agent-evals-and-observability/SKILL.md`)
|
||||
6. Learning and disablement — incident-learning (`../../incident-learning/SKILL.md`), production-readiness (`../../production-readiness/SKILL.md`), privacy-engineering (`../../privacy-engineering/SKILL.md`)
|
||||
1. Contract definition — ../../agent-evals-and-observability/SKILL.md (`../../agent-evals-and-observability/SKILL.md`), ../../production-readiness/SKILL.md (`../../production-readiness/SKILL.md`), ../../incident-learning/SKILL.md (`../../incident-learning/SKILL.md`)
|
||||
2. Versioning and rollout planning — ../../release-engineering/SKILL.md (`../../release-engineering/SKILL.md`), ../../platform-engineering/SKILL.md (`../../platform-engineering/SKILL.md`)
|
||||
3. Staged rollout — ../../platform-engineering/SKILL.md (`../../platform-engineering/SKILL.md`), ../../site-reliability-engineering/SKILL.md (`../../site-reliability-engineering/SKILL.md`)
|
||||
4. Runtime monitoring — ../../site-reliability-engineering/SKILL.md (`../../site-reliability-engineering/SKILL.md`), ../../secure-software-engineering/SKILL.md (`../../secure-software-engineering/SKILL.md`)
|
||||
5. Trace-to-eval feedback — ../../agent-evals-and-observability/SKILL.md (`../../agent-evals-and-observability/SKILL.md`)
|
||||
6. Learning and disablement — ../../incident-learning/SKILL.md (`../../incident-learning/SKILL.md`), ../../production-readiness/SKILL.md (`../../production-readiness/SKILL.md`), ../../privacy-engineering/SKILL.md (`../../privacy-engineering/SKILL.md`)
|
||||
- **Included skills:**
|
||||
- agent-evals-and-observability (`../../agent-evals-and-observability/SKILL.md`)
|
||||
- release-engineering (`../../release-engineering/SKILL.md`)
|
||||
- site-reliability-engineering (`../../site-reliability-engineering/SKILL.md`)
|
||||
- secure-software-engineering (`../../secure-software-engineering/SKILL.md`)
|
||||
- platform-engineering (`../../platform-engineering/SKILL.md`)
|
||||
- production-readiness (`../../production-readiness/SKILL.md`)
|
||||
- incident-learning (`../../incident-learning/SKILL.md`)
|
||||
- privacy-engineering (`../../privacy-engineering/SKILL.md`)
|
||||
- ../../agent-evals-and-observability/SKILL.md (`../../agent-evals-and-observability/SKILL.md`)
|
||||
- ../../release-engineering/SKILL.md (`../../release-engineering/SKILL.md`)
|
||||
- ../../site-reliability-engineering/SKILL.md (`../../site-reliability-engineering/SKILL.md`)
|
||||
- ../../secure-software-engineering/SKILL.md (`../../secure-software-engineering/SKILL.md`)
|
||||
- ../../platform-engineering/SKILL.md (`../../platform-engineering/SKILL.md`)
|
||||
- ../../production-readiness/SKILL.md (`../../production-readiness/SKILL.md`)
|
||||
- ../../incident-learning/SKILL.md (`../../incident-learning/SKILL.md`)
|
||||
- ../../privacy-engineering/SKILL.md (`../../privacy-engineering/SKILL.md`)
|
||||
- **Prerequisites:**
|
||||
- Agent evaluation results and observability instrumentation — via agent-evals-and-observability (`../../agent-evals-and-observability/SKILL.md`)
|
||||
- Production-readiness evidence (go/no-go/defer/exception outcomes) — via production-readiness (`../../production-readiness/SKILL.md`)
|
||||
- Incident-learning records (verified closure, follow-up work map) — via incident-learning (`../../incident-learning/SKILL.md`)
|
||||
- Release pipeline and artifact promotion baseline — via release-engineering (`../../release-engineering/SKILL.md`)
|
||||
- Agent evaluation results and observability instrumentation — via ../../agent-evals-and-observability/SKILL.md (`../../agent-evals-and-observability/SKILL.md`)
|
||||
- Production-readiness evidence (go/no-go/defer/exception outcomes) — via ../../production-readiness/SKILL.md (`../../production-readiness/SKILL.md`)
|
||||
- Incident-learning records (verified closure, follow-up work map) — via ../../incident-learning/SKILL.md (`../../incident-learning/SKILL.md`)
|
||||
- Release pipeline and artifact promotion baseline — via ../../release-engineering/SKILL.md (`../../release-engineering/SKILL.md`)
|
||||
- **Outputs:** agent-production-contract, runtime-control-plan, staged-rollout-plan, tool-authority-health-record, trace-to-eval-feedback-loop, disablement-record
|
||||
- **Handoffs:**
|
||||
- staged-rollout-plan → release-engineering — Rollout stages and promotion gates integrate with the release pipeline; rollback triggers tie agent health to release mechanics.
|
||||
@@ -54,57 +54,57 @@ the migration path, and the field definitions. Regenerate with
|
||||
- tool-authority-health-record → incident-learning — Tool-failure and authority-breach records feed post-incident analysis and verified-closure tracking.
|
||||
- disablement-record → human operator — Disablement revokes credentials, removes the agent from routing/load-balancing, and records the reason, timestamp, and authorizing evidence.
|
||||
- **Conflicts:**
|
||||
- production-readiness (`../../production-readiness/SKILL.md`) with production-excellence — Both bundles include production-readiness. This bundle consumes readiness outcomes as authority-gating inputs; production-excellence produces the go/no-go/defer/exception decisions.
|
||||
- production-readiness (`../../production-readiness/SKILL.md`) with product-lifecycle — Both bundles include production-readiness. Route phase 6 delivery readiness reviews to product-lifecycle; runtime authority decisions for an agent in production go to this bundle.
|
||||
- release-engineering (`../../release-engineering/SKILL.md`) with production-excellence — Release engineering is shared. Route by context: agent staged-rollout planning (this bundle) versus launch-gate release plans (production-excellence).
|
||||
- release-engineering (`../../release-engineering/SKILL.md`) with product-lifecycle — Release engineering is shared. Route by context: agent staged-rollout planning (this bundle) versus lifecycle delivery handoff (product-lifecycle).
|
||||
- site-reliability-engineering (`../../site-reliability-engineering/SKILL.md`) with production-excellence — SRE is shared. This bundle uses it for runtime latency/cost budgets and incident handoff; production-excellence uses it for gate-entry reliability evidence. Incident command stays with SRE in both cases.
|
||||
- site-reliability-engineering (`../../site-reliability-engineering/SKILL.md`) with product-lifecycle — SRE is shared. This bundle uses it for agent runtime budgets; product-lifecycle routes to it for delivery reliability.
|
||||
- secure-software-engineering (`../../secure-software-engineering/SKILL.md`) with production-excellence — Security engineering is shared. Route by context: agent authority contracts and disablement security (this bundle) versus launch-gate security evidence (production-excellence).
|
||||
- secure-software-engineering (`../../secure-software-engineering/SKILL.md`) with product-lifecycle — Security engineering is shared. Route by context: agent trust-boundary and disablement security (this bundle) versus lifecycle-phase security needs (product-lifecycle).
|
||||
- platform-engineering (`../../platform-engineering/SKILL.md`) with production-excellence — Platform engineering is shared. Route by context: agent sandboxing and tool-execution isolation (this bundle) versus launch-gate platform evidence (production-excellence).
|
||||
- platform-engineering (`../../platform-engineering/SKILL.md`) with product-lifecycle — Platform engineering is shared. Route by context: agent sandboxing and tool-execution isolation (this bundle) versus lifecycle delivery handoff (product-lifecycle).
|
||||
- incident-learning (`../../incident-learning/SKILL.md`) with production-excellence — Both bundles consume incident-learning records. This bundle consumes verified-closure records as escalation and disablement inputs; production-excellence uses incident history as gate-entry evidence.
|
||||
- privacy-engineering (`../../privacy-engineering/SKILL.md`) with product-lifecycle — Privacy engineering is shared. This bundle routes to it for trace scrubbing and user-data-access grants; product-lifecycle routes to it for PII, consent, retention, and data flows in any phase.
|
||||
- ../../production-readiness/SKILL.md (`../../production-readiness/SKILL.md`) with production-excellence — Both bundles include production-readiness. This bundle consumes readiness outcomes as authority-gating inputs; production-excellence produces the go/no-go/defer/exception decisions.
|
||||
- ../../production-readiness/SKILL.md (`../../production-readiness/SKILL.md`) with product-lifecycle — Both bundles include production-readiness. Route phase 6 delivery readiness reviews to product-lifecycle; runtime authority decisions for an agent in production go to this bundle.
|
||||
- ../../release-engineering/SKILL.md (`../../release-engineering/SKILL.md`) with production-excellence — Release engineering is shared. Route by context: agent staged-rollout planning (this bundle) versus launch-gate release plans (production-excellence).
|
||||
- ../../release-engineering/SKILL.md (`../../release-engineering/SKILL.md`) with product-lifecycle — Release engineering is shared. Route by context: agent staged-rollout planning (this bundle) versus lifecycle delivery handoff (product-lifecycle).
|
||||
- ../../site-reliability-engineering/SKILL.md (`../../site-reliability-engineering/SKILL.md`) with production-excellence — SRE is shared. This bundle uses it for runtime latency/cost budgets and incident handoff; production-excellence uses it for gate-entry reliability evidence. Incident command stays with SRE in both cases.
|
||||
- ../../site-reliability-engineering/SKILL.md (`../../site-reliability-engineering/SKILL.md`) with product-lifecycle — SRE is shared. This bundle uses it for agent runtime budgets; product-lifecycle routes to it for delivery reliability.
|
||||
- ../../secure-software-engineering/SKILL.md (`../../secure-software-engineering/SKILL.md`) with production-excellence — Security engineering is shared. Route by context: agent authority contracts and disablement security (this bundle) versus launch-gate security evidence (production-excellence).
|
||||
- ../../secure-software-engineering/SKILL.md (`../../secure-software-engineering/SKILL.md`) with product-lifecycle — Security engineering is shared. Route by context: agent trust-boundary and disablement security (this bundle) versus lifecycle-phase security needs (product-lifecycle).
|
||||
- ../../platform-engineering/SKILL.md (`../../platform-engineering/SKILL.md`) with production-excellence — Platform engineering is shared. Route by context: agent sandboxing and tool-execution isolation (this bundle) versus launch-gate platform evidence (production-excellence).
|
||||
- ../../platform-engineering/SKILL.md (`../../platform-engineering/SKILL.md`) with product-lifecycle — Platform engineering is shared. Route by context: agent sandboxing and tool-execution isolation (this bundle) versus lifecycle delivery handoff (product-lifecycle).
|
||||
- ../../incident-learning/SKILL.md (`../../incident-learning/SKILL.md`) with production-excellence — Both bundles consume incident-learning records. This bundle consumes verified-closure records as escalation and disablement inputs; production-excellence uses incident history as gate-entry evidence.
|
||||
- ../../privacy-engineering/SKILL.md (`../../privacy-engineering/SKILL.md`) with product-lifecycle — Privacy engineering is shared. This bundle routes to it for trace scrubbing and user-data-access grants; product-lifecycle routes to it for PII, consent, retention, and data flows in any phase.
|
||||
- **Eval suite:** evals/evals.json
|
||||
|
||||
### forward-deployed-engineering
|
||||
|
||||
- Derivation: `manifest` — source: `bundles/forward-deployed-engineering/manifest.yaml`
|
||||
- Derivation: `manifest` — source: `forward-deployed-engineering/manifest.yaml`
|
||||
- **Purpose:** Carry an embedded technical engagement from ambiguous stakeholder need through discovery, framing, hypothesis, build, evaluation, deployment, adoption, measurement, and generalization while preserving decision rights, evidence, handoffs, and reusable field learning.
|
||||
- **Audience:** Technical leads and agents embedded across stakeholder discovery, implementation, production fit, adoption, and measurable workflow outcomes; this is a continuity layer that routes specialist methods rather than replacing them.
|
||||
- **Stages (ordered):**
|
||||
1. Discover — product-discovery (`../../product-discovery/SKILL.md`), data-engineering (`../../data-engineering/SKILL.md`), remote-systems-administration (`../../remote-systems-administration/SKILL.md`)
|
||||
2. Frame — product-design-and-ux (`../../product-design-and-ux/SKILL.md`), privacy-engineering (`../../privacy-engineering/SKILL.md`), secure-software-engineering (`../../secure-software-engineering/SKILL.md`)
|
||||
3. Hypothesize — product-experimentation (`../../product-experimentation/SKILL.md`), agent-evals-and-observability (`../../agent-evals-and-observability/SKILL.md`)
|
||||
4. Build — implementation-planning (`../../implementation-planning/SKILL.md`), backend-engineering (`../../backend-engineering/SKILL.md`), frontend-engineering (`../../frontend-engineering/SKILL.md`), data-engineering (`../../data-engineering/SKILL.md`)
|
||||
5. Evaluate — agent-evals-and-observability (`../../agent-evals-and-observability/SKILL.md`), qa-methodology (`../../qa-methodology/SKILL.md`), verification-methodology (`../../verification-methodology/SKILL.md`)
|
||||
6. Deploy — production-readiness (`../../production-readiness/SKILL.md`), release-engineering (`../../release-engineering/SKILL.md`), platform-engineering (`../../platform-engineering/SKILL.md`), remote-systems-administration (`../../remote-systems-administration/SKILL.md`)
|
||||
7. Adopt — product-adoption (`../../product-adoption/SKILL.md`), product-design-and-ux (`../../product-design-and-ux/SKILL.md`)
|
||||
8. Measure — product-analytics-and-measurement (`../../product-analytics-and-measurement/SKILL.md`), agent-evals-and-observability (`../../agent-evals-and-observability/SKILL.md`), site-reliability-engineering (`../../site-reliability-engineering/SKILL.md`)
|
||||
9. Generalize — product-lifecycle-learning (`../../product-lifecycle-learning/SKILL.md`), product-methodology (`../../product-methodology/SKILL.md`)
|
||||
1. Discover — ../../product-discovery/SKILL.md (`../../product-discovery/SKILL.md`), ../../data-engineering/SKILL.md (`../../data-engineering/SKILL.md`), ../../remote-systems-administration/SKILL.md (`../../remote-systems-administration/SKILL.md`)
|
||||
2. Frame — ../../product-design-and-ux/SKILL.md (`../../product-design-and-ux/SKILL.md`), ../../privacy-engineering/SKILL.md (`../../privacy-engineering/SKILL.md`), ../../secure-software-engineering/SKILL.md (`../../secure-software-engineering/SKILL.md`)
|
||||
3. Hypothesize — ../../product-experimentation/SKILL.md (`../../product-experimentation/SKILL.md`), ../../agent-evals-and-observability/SKILL.md (`../../agent-evals-and-observability/SKILL.md`)
|
||||
4. Build — ../../implementation-planning/SKILL.md (`../../implementation-planning/SKILL.md`), ../../backend-engineering/SKILL.md (`../../backend-engineering/SKILL.md`), ../../frontend-engineering/SKILL.md (`../../frontend-engineering/SKILL.md`), ../../data-engineering/SKILL.md (`../../data-engineering/SKILL.md`)
|
||||
5. Evaluate — ../../agent-evals-and-observability/SKILL.md (`../../agent-evals-and-observability/SKILL.md`), ../../qa-methodology/SKILL.md (`../../qa-methodology/SKILL.md`), ../../verification-methodology/SKILL.md (`../../verification-methodology/SKILL.md`)
|
||||
6. Deploy — ../../production-readiness/SKILL.md (`../../production-readiness/SKILL.md`), ../../release-engineering/SKILL.md (`../../release-engineering/SKILL.md`), ../../platform-engineering/SKILL.md (`../../platform-engineering/SKILL.md`), ../../remote-systems-administration/SKILL.md (`../../remote-systems-administration/SKILL.md`)
|
||||
7. Adopt — ../../product-adoption/SKILL.md (`../../product-adoption/SKILL.md`), ../../product-design-and-ux/SKILL.md (`../../product-design-and-ux/SKILL.md`)
|
||||
8. Measure — ../../product-analytics-and-measurement/SKILL.md (`../../product-analytics-and-measurement/SKILL.md`), ../../agent-evals-and-observability/SKILL.md (`../../agent-evals-and-observability/SKILL.md`), ../../site-reliability-engineering/SKILL.md (`../../site-reliability-engineering/SKILL.md`)
|
||||
9. Generalize — ../../product-lifecycle-learning/SKILL.md (`../../product-lifecycle-learning/SKILL.md`), ../../product-methodology/SKILL.md (`../../product-methodology/SKILL.md`)
|
||||
- **Included skills:**
|
||||
- product-discovery (`../../product-discovery/SKILL.md`)
|
||||
- product-design-and-ux (`../../product-design-and-ux/SKILL.md`)
|
||||
- product-experimentation (`../../product-experimentation/SKILL.md`)
|
||||
- agent-evals-and-observability (`../../agent-evals-and-observability/SKILL.md`)
|
||||
- implementation-planning (`../../implementation-planning/SKILL.md`)
|
||||
- backend-engineering (`../../backend-engineering/SKILL.md`)
|
||||
- frontend-engineering (`../../frontend-engineering/SKILL.md`)
|
||||
- data-engineering (`../../data-engineering/SKILL.md`)
|
||||
- qa-methodology (`../../qa-methodology/SKILL.md`)
|
||||
- verification-methodology (`../../verification-methodology/SKILL.md`)
|
||||
- production-readiness (`../../production-readiness/SKILL.md`)
|
||||
- release-engineering (`../../release-engineering/SKILL.md`)
|
||||
- platform-engineering (`../../platform-engineering/SKILL.md`)
|
||||
- remote-systems-administration (`../../remote-systems-administration/SKILL.md`)
|
||||
- product-adoption (`../../product-adoption/SKILL.md`)
|
||||
- product-analytics-and-measurement (`../../product-analytics-and-measurement/SKILL.md`)
|
||||
- site-reliability-engineering (`../../site-reliability-engineering/SKILL.md`)
|
||||
- product-lifecycle-learning (`../../product-lifecycle-learning/SKILL.md`)
|
||||
- product-methodology (`../../product-methodology/SKILL.md`)
|
||||
- privacy-engineering (`../../privacy-engineering/SKILL.md`)
|
||||
- secure-software-engineering (`../../secure-software-engineering/SKILL.md`)
|
||||
- ../../product-discovery/SKILL.md (`../../product-discovery/SKILL.md`)
|
||||
- ../../product-design-and-ux/SKILL.md (`../../product-design-and-ux/SKILL.md`)
|
||||
- ../../product-experimentation/SKILL.md (`../../product-experimentation/SKILL.md`)
|
||||
- ../../agent-evals-and-observability/SKILL.md (`../../agent-evals-and-observability/SKILL.md`)
|
||||
- ../../implementation-planning/SKILL.md (`../../implementation-planning/SKILL.md`)
|
||||
- ../../backend-engineering/SKILL.md (`../../backend-engineering/SKILL.md`)
|
||||
- ../../frontend-engineering/SKILL.md (`../../frontend-engineering/SKILL.md`)
|
||||
- ../../data-engineering/SKILL.md (`../../data-engineering/SKILL.md`)
|
||||
- ../../qa-methodology/SKILL.md (`../../qa-methodology/SKILL.md`)
|
||||
- ../../verification-methodology/SKILL.md (`../../verification-methodology/SKILL.md`)
|
||||
- ../../production-readiness/SKILL.md (`../../production-readiness/SKILL.md`)
|
||||
- ../../release-engineering/SKILL.md (`../../release-engineering/SKILL.md`)
|
||||
- ../../platform-engineering/SKILL.md (`../../platform-engineering/SKILL.md`)
|
||||
- ../../remote-systems-administration/SKILL.md (`../../remote-systems-administration/SKILL.md`)
|
||||
- ../../product-adoption/SKILL.md (`../../product-adoption/SKILL.md`)
|
||||
- ../../product-analytics-and-measurement/SKILL.md (`../../product-analytics-and-measurement/SKILL.md`)
|
||||
- ../../site-reliability-engineering/SKILL.md (`../../site-reliability-engineering/SKILL.md`)
|
||||
- ../../product-lifecycle-learning/SKILL.md (`../../product-lifecycle-learning/SKILL.md`)
|
||||
- ../../product-methodology/SKILL.md (`../../product-methodology/SKILL.md`)
|
||||
- ../../privacy-engineering/SKILL.md (`../../privacy-engineering/SKILL.md`)
|
||||
- ../../secure-software-engineering/SKILL.md (`../../secure-software-engineering/SKILL.md`)
|
||||
- **Prerequisites:**
|
||||
- Stakeholder request or observed workflow opportunity and a named accountable lead
|
||||
- Authority to conduct non-destructive discovery with access to relevant stakeholders or workflow evidence
|
||||
@@ -116,79 +116,79 @@ the migration path, and the field definitions. Regenerate with
|
||||
- productization-record → product, platform, or receiving delivery owner — Field learning is classified with evidence, reuse boundary, owner, and next action rather than being promoted by enthusiasm alone.
|
||||
- field-learning-record → engagement sponsor — The engagement closes with observed outcomes, unresolved uncertainty, and a durable transfer or follow-up path.
|
||||
- **Conflicts:**
|
||||
- product-discovery (`../../product-discovery/SKILL.md`) with product-lifecycle — This bundle uses product-discovery for embedded delivery continuity and workflow context; product-lifecycle owns product investment and lifecycle governance.
|
||||
- product-discovery (`../../product-discovery/SKILL.md`) with research-and-vault — Use product-discovery for stakeholder and workflow discovery; use research-and-vault for a reusable web-research-to-knowledge capture chain.
|
||||
- product-experimentation (`../../product-experimentation/SKILL.md`) with product-lifecycle — This bundle routes experiments to test an engagement intervention; product-lifecycle routes product investment experiments within its lifecycle governance.
|
||||
- implementation-planning (`../../implementation-planning/SKILL.md`) with product-lifecycle — This bundle routes implementation planning only during Build after an authorized owner approves the requirement; product-lifecycle owns product delivery handoff. Route a bounded code change to neckbeard.
|
||||
- production-readiness (`../../production-readiness/SKILL.md`) with production-excellence — This bundle carries engagement evidence into the specialist readiness review; production-excellence owns the cross-domain launch gate decision.
|
||||
- production-readiness (`../../production-readiness/SKILL.md`) with product-lifecycle — This bundle routes readiness for an embedded capability; product-lifecycle owns product lifecycle delivery handoff. Do not run both orchestration paths for one decision.
|
||||
- release-engineering (`../../release-engineering/SKILL.md`) with production-excellence — This bundle routes deployment evidence from the engagement; production-excellence uses release evidence for a launch gate.
|
||||
- release-engineering (`../../release-engineering/SKILL.md`) with product-lifecycle — This bundle uses release engineering for embedded rollout continuity; product-lifecycle uses it for product delivery handoff.
|
||||
- platform-engineering (`../../platform-engineering/SKILL.md`) with production-excellence — This bundle routes platform work needed to deploy the engagement capability; production-excellence assembles platform evidence for launch gating.
|
||||
- platform-engineering (`../../platform-engineering/SKILL.md`) with product-lifecycle — This bundle routes platform work needed by the engagement; product-lifecycle routes platform work in a product delivery handoff.
|
||||
- platform-engineering (`../../platform-engineering/SKILL.md`) with agent-production-operations — This bundle routes product or engagement platform delivery; agent-production-operations owns runtime agent sandboxing and tool-execution isolation.
|
||||
- secure-software-engineering (`../../secure-software-engineering/SKILL.md`) with production-excellence — This bundle routes trust-boundary work during the engagement; production-excellence consumes security evidence for its launch gate.
|
||||
- secure-software-engineering (`../../secure-software-engineering/SKILL.md`) with product-lifecycle — This bundle routes security work in the embedded lifecycle; product-lifecycle routes security work in product lifecycle phases.
|
||||
- secure-software-engineering (`../../secure-software-engineering/SKILL.md`) with agent-production-operations — This bundle routes application and engagement security; agent-production-operations owns agent authority, disablement, and runtime security controls.
|
||||
- privacy-engineering (`../../privacy-engineering/SKILL.md`) with product-lifecycle — This bundle routes privacy work for engagement data flows; product-lifecycle routes privacy work across product lifecycle phases.
|
||||
- privacy-engineering (`../../privacy-engineering/SKILL.md`) with agent-production-operations — This bundle routes engagement privacy decisions; agent-production-operations routes trace scrubbing and user-data-access grants.
|
||||
- qa-methodology (`../../qa-methodology/SKILL.md`) with production-excellence — This bundle routes quality evidence for the built capability; production-excellence uses QA evidence at the launch gate.
|
||||
- qa-methodology (`../../qa-methodology/SKILL.md`) with product-lifecycle — This bundle routes evaluation and quality work for engagement delivery; product-lifecycle uses QA at product delivery handoff.
|
||||
- verification-methodology (`../../verification-methodology/SKILL.md`) with production-excellence — This bundle uses verification to label engagement evidence; production-excellence uses it to verify launch-boundary evidence.
|
||||
- verification-methodology (`../../verification-methodology/SKILL.md`) with product-lifecycle — This bundle verifies continuity artifacts and field outcomes; product-lifecycle verifies evidence at product phase gates.
|
||||
- site-reliability-engineering (`../../site-reliability-engineering/SKILL.md`) with production-excellence — This bundle routes reliability evidence for the engagement; production-excellence uses SRE evidence for its production gate.
|
||||
- site-reliability-engineering (`../../site-reliability-engineering/SKILL.md`) with product-lifecycle — This bundle routes reliability work needed for adoption and operation; product-lifecycle routes SRE work in product delivery handoff.
|
||||
- site-reliability-engineering (`../../site-reliability-engineering/SKILL.md`) with agent-production-operations — This bundle routes service reliability; agent-production-operations routes runtime latency, cost budgets, and incident handoff for agents.
|
||||
- data-engineering (`../../data-engineering/SKILL.md`) with production-excellence — This bundle routes data work required by the engagement; production-excellence consumes data evidence in its operational handoff and launch gate.
|
||||
- product-adoption (`../../product-adoption/SKILL.md`) with product-lifecycle — This bundle owns adoption continuity for an embedded engagement; product-lifecycle owns product adoption as one phase of product governance.
|
||||
- product-analytics-and-measurement (`../../product-analytics-and-measurement/SKILL.md`) with product-lifecycle — This bundle measures workflow impact for engagement completion; product-lifecycle measures product outcomes in lifecycle review.
|
||||
- product-lifecycle-learning (`../../product-lifecycle-learning/SKILL.md`) with product-lifecycle — This bundle uses field learning to decide generalization; product-lifecycle-learning owns the product lifecycle learning method and decision record.
|
||||
- agent-evals-and-observability (`../../agent-evals-and-observability/SKILL.md`) with agent-production-operations — This bundle routes eval evidence for engagement release and learning; agent-production-operations consumes eval and trace evidence for runtime control.
|
||||
- production-readiness (`../../production-readiness/SKILL.md`) with agent-production-operations — This bundle routes readiness for an embedded capability; agent-production-operations consumes readiness as an authority-gating input.
|
||||
- release-engineering (`../../release-engineering/SKILL.md`) with agent-production-operations — This bundle uses release engineering for engagement rollout; agent-production-operations uses it for staged runtime rollout and fallback.
|
||||
- product-design-and-ux (`../../product-design-and-ux/SKILL.md`) with neckbeard — This bundle routes UX for embedded workflow adoption; neckbeard uses UX only as needed for a bounded software change. Route by task boundary.
|
||||
- product-discovery (`../../product-discovery/SKILL.md`) with neckbeard — This bundle owns embedded stakeholder and workflow discovery; neckbeard handles the bounded change after its requirements are known.
|
||||
- qa-methodology (`../../qa-methodology/SKILL.md`) with neckbeard — This bundle routes QA for engagement evidence; neckbeard applies QA within its software delivery journey for a bounded repository change.
|
||||
- release-engineering (`../../release-engineering/SKILL.md`) with neckbeard — This bundle routes release work across the engagement lifecycle; neckbeard owns release delivery for a bounded change.
|
||||
- secure-software-engineering (`../../secure-software-engineering/SKILL.md`) with neckbeard — This bundle routes security decisions across embedded delivery; neckbeard applies security to its bounded software change.
|
||||
- site-reliability-engineering (`../../site-reliability-engineering/SKILL.md`) with neckbeard — This bundle routes reliability for engagement outcomes; neckbeard routes reliability concerns within its software delivery journey.
|
||||
- verification-methodology (`../../verification-methodology/SKILL.md`) with neckbeard — This bundle verifies stage continuity and outcome evidence; neckbeard verifies the bounded repository change.
|
||||
- product-design-and-ux (`../../product-design-and-ux/SKILL.md`) with product-lifecycle — This bundle routes UX for embedded workflow adoption; product-lifecycle routes UX for product requirements and lifecycle governance.
|
||||
- product-methodology (`../../product-methodology/SKILL.md`) with product-lifecycle — This bundle uses prioritization only to support engagement generalization; product-lifecycle owns product prioritization and portfolio methods.
|
||||
- ../../product-discovery/SKILL.md (`../../product-discovery/SKILL.md`) with product-lifecycle — This bundle uses product-discovery for embedded delivery continuity and workflow context; product-lifecycle owns product investment and lifecycle governance.
|
||||
- ../../product-discovery/SKILL.md (`../../product-discovery/SKILL.md`) with research-and-vault — Use product-discovery for stakeholder and workflow discovery; use research-and-vault for a reusable web-research-to-knowledge capture chain.
|
||||
- ../../product-experimentation/SKILL.md (`../../product-experimentation/SKILL.md`) with product-lifecycle — This bundle routes experiments to test an engagement intervention; product-lifecycle routes product investment experiments within its lifecycle governance.
|
||||
- ../../implementation-planning/SKILL.md (`../../implementation-planning/SKILL.md`) with product-lifecycle — This bundle routes implementation planning only during Build after an authorized owner approves the requirement; product-lifecycle owns product delivery handoff. Route a bounded code change to neckbeard.
|
||||
- ../../production-readiness/SKILL.md (`../../production-readiness/SKILL.md`) with production-excellence — This bundle carries engagement evidence into the specialist readiness review; production-excellence owns the cross-domain launch gate decision.
|
||||
- ../../production-readiness/SKILL.md (`../../production-readiness/SKILL.md`) with product-lifecycle — This bundle routes readiness for an embedded capability; product-lifecycle owns product lifecycle delivery handoff. Do not run both orchestration paths for one decision.
|
||||
- ../../release-engineering/SKILL.md (`../../release-engineering/SKILL.md`) with production-excellence — This bundle routes deployment evidence from the engagement; production-excellence uses release evidence for a launch gate.
|
||||
- ../../release-engineering/SKILL.md (`../../release-engineering/SKILL.md`) with product-lifecycle — This bundle uses release engineering for embedded rollout continuity; product-lifecycle uses it for product delivery handoff.
|
||||
- ../../platform-engineering/SKILL.md (`../../platform-engineering/SKILL.md`) with production-excellence — This bundle routes platform work needed to deploy the engagement capability; production-excellence assembles platform evidence for launch gating.
|
||||
- ../../platform-engineering/SKILL.md (`../../platform-engineering/SKILL.md`) with product-lifecycle — This bundle routes platform work needed by the engagement; product-lifecycle routes platform work in a product delivery handoff.
|
||||
- ../../platform-engineering/SKILL.md (`../../platform-engineering/SKILL.md`) with agent-production-operations — This bundle routes product or engagement platform delivery; agent-production-operations owns runtime agent sandboxing and tool-execution isolation.
|
||||
- ../../secure-software-engineering/SKILL.md (`../../secure-software-engineering/SKILL.md`) with production-excellence — This bundle routes trust-boundary work during the engagement; production-excellence consumes security evidence for its launch gate.
|
||||
- ../../secure-software-engineering/SKILL.md (`../../secure-software-engineering/SKILL.md`) with product-lifecycle — This bundle routes security work in the embedded lifecycle; product-lifecycle routes security work in product lifecycle phases.
|
||||
- ../../secure-software-engineering/SKILL.md (`../../secure-software-engineering/SKILL.md`) with agent-production-operations — This bundle routes application and engagement security; agent-production-operations owns agent authority, disablement, and runtime security controls.
|
||||
- ../../privacy-engineering/SKILL.md (`../../privacy-engineering/SKILL.md`) with product-lifecycle — This bundle routes privacy work for engagement data flows; product-lifecycle routes privacy work across product lifecycle phases.
|
||||
- ../../privacy-engineering/SKILL.md (`../../privacy-engineering/SKILL.md`) with agent-production-operations — This bundle routes engagement privacy decisions; agent-production-operations routes trace scrubbing and user-data-access grants.
|
||||
- ../../qa-methodology/SKILL.md (`../../qa-methodology/SKILL.md`) with production-excellence — This bundle routes quality evidence for the built capability; production-excellence uses QA evidence at the launch gate.
|
||||
- ../../qa-methodology/SKILL.md (`../../qa-methodology/SKILL.md`) with product-lifecycle — This bundle routes evaluation and quality work for engagement delivery; product-lifecycle uses QA at product delivery handoff.
|
||||
- ../../verification-methodology/SKILL.md (`../../verification-methodology/SKILL.md`) with production-excellence — This bundle uses verification to label engagement evidence; production-excellence uses it to verify launch-boundary evidence.
|
||||
- ../../verification-methodology/SKILL.md (`../../verification-methodology/SKILL.md`) with product-lifecycle — This bundle verifies continuity artifacts and field outcomes; product-lifecycle verifies evidence at product phase gates.
|
||||
- ../../site-reliability-engineering/SKILL.md (`../../site-reliability-engineering/SKILL.md`) with production-excellence — This bundle routes reliability evidence for the engagement; production-excellence uses SRE evidence for its production gate.
|
||||
- ../../site-reliability-engineering/SKILL.md (`../../site-reliability-engineering/SKILL.md`) with product-lifecycle — This bundle routes reliability work needed for adoption and operation; product-lifecycle routes SRE work in product delivery handoff.
|
||||
- ../../site-reliability-engineering/SKILL.md (`../../site-reliability-engineering/SKILL.md`) with agent-production-operations — This bundle routes service reliability; agent-production-operations routes runtime latency, cost budgets, and incident handoff for agents.
|
||||
- ../../data-engineering/SKILL.md (`../../data-engineering/SKILL.md`) with production-excellence — This bundle routes data work required by the engagement; production-excellence consumes data evidence in its operational handoff and launch gate.
|
||||
- ../../product-adoption/SKILL.md (`../../product-adoption/SKILL.md`) with product-lifecycle — This bundle owns adoption continuity for an embedded engagement; product-lifecycle owns product adoption as one phase of product governance.
|
||||
- ../../product-analytics-and-measurement/SKILL.md (`../../product-analytics-and-measurement/SKILL.md`) with product-lifecycle — This bundle measures workflow impact for engagement completion; product-lifecycle measures product outcomes in lifecycle review.
|
||||
- ../../product-lifecycle-learning/SKILL.md (`../../product-lifecycle-learning/SKILL.md`) with product-lifecycle — This bundle uses field learning to decide generalization; product-lifecycle-learning owns the product lifecycle learning method and decision record.
|
||||
- ../../agent-evals-and-observability/SKILL.md (`../../agent-evals-and-observability/SKILL.md`) with agent-production-operations — This bundle routes eval evidence for engagement release and learning; agent-production-operations consumes eval and trace evidence for runtime control.
|
||||
- ../../production-readiness/SKILL.md (`../../production-readiness/SKILL.md`) with agent-production-operations — This bundle routes readiness for an embedded capability; agent-production-operations consumes readiness as an authority-gating input.
|
||||
- ../../release-engineering/SKILL.md (`../../release-engineering/SKILL.md`) with agent-production-operations — This bundle uses release engineering for engagement rollout; agent-production-operations uses it for staged runtime rollout and fallback.
|
||||
- ../../product-design-and-ux/SKILL.md (`../../product-design-and-ux/SKILL.md`) with neckbeard — This bundle routes UX for embedded workflow adoption; neckbeard uses UX only as needed for a bounded software change. Route by task boundary.
|
||||
- ../../product-discovery/SKILL.md (`../../product-discovery/SKILL.md`) with neckbeard — This bundle owns embedded stakeholder and workflow discovery; neckbeard handles the bounded change after its requirements are known.
|
||||
- ../../qa-methodology/SKILL.md (`../../qa-methodology/SKILL.md`) with neckbeard — This bundle routes QA for engagement evidence; neckbeard applies QA within its software delivery journey for a bounded repository change.
|
||||
- ../../release-engineering/SKILL.md (`../../release-engineering/SKILL.md`) with neckbeard — This bundle routes release work across the engagement lifecycle; neckbeard owns release delivery for a bounded change.
|
||||
- ../../secure-software-engineering/SKILL.md (`../../secure-software-engineering/SKILL.md`) with neckbeard — This bundle routes security decisions across embedded delivery; neckbeard applies security to its bounded software change.
|
||||
- ../../site-reliability-engineering/SKILL.md (`../../site-reliability-engineering/SKILL.md`) with neckbeard — This bundle routes reliability for engagement outcomes; neckbeard routes reliability concerns within its software delivery journey.
|
||||
- ../../verification-methodology/SKILL.md (`../../verification-methodology/SKILL.md`) with neckbeard — This bundle verifies stage continuity and outcome evidence; neckbeard verifies the bounded repository change.
|
||||
- ../../product-design-and-ux/SKILL.md (`../../product-design-and-ux/SKILL.md`) with product-lifecycle — This bundle routes UX for embedded workflow adoption; product-lifecycle routes UX for product requirements and lifecycle governance.
|
||||
- ../../product-methodology/SKILL.md (`../../product-methodology/SKILL.md`) with product-lifecycle — This bundle uses prioritization only to support engagement generalization; product-lifecycle owns product prioritization and portfolio methods.
|
||||
- **Eval suite:** evals/evals.json
|
||||
|
||||
### neckbeard
|
||||
|
||||
- Derivation: `manifest` — source: `bundles/neckbeard/manifest.yaml`
|
||||
- Derivation: `manifest` — source: `neckbeard/manifest.yaml`
|
||||
- **Purpose:** A disciplined SDLC delivery operating model for non-trivial software change — fix, build, refactor, review, verify, or release — that routes the work through framing, discovery, design, implementation, review, verification, delivery, and learning, choosing the smallest *safe* intervention, proving it at the real delivery boundary, and leaving an inspectable evidence ledger.
|
||||
- **Audience:** Software engineers and agents delivering non-trivial software changes (bug fixes, features, refactors, reviews, releases) that need a bounded, stage-aware path to a defensible 'done' with recorded evidence; teams running issue-to-PR change-request journeys with gates and an authorized release.
|
||||
- **Stages (ordered):**
|
||||
1. Intake and framing — product-discovery (`../../product-discovery/SKILL.md`)
|
||||
2. Current-state discovery — software-architecture-analysis (`../../software-architecture-analysis/SKILL.md`), systematic-debugging (`../../systematic-debugging/SKILL.md`)
|
||||
3. Design — api-design-and-evolution (`../../api-design-and-evolution/SKILL.md`), product-design-and-ux (`../../product-design-and-ux/SKILL.md`)
|
||||
4. Specification — spec-driven-development (`../../spec-driven-development/SKILL.md`)
|
||||
5. Test planning — qa-methodology (`../../qa-methodology/SKILL.md`)
|
||||
6. Implementation — secure-software-engineering (`../../secure-software-engineering/SKILL.md`), web-accessibility (`../../web-accessibility/SKILL.md`)
|
||||
7. Review and verification — verification-methodology (`../../verification-methodology/SKILL.md`), technical-documentation (`../../technical-documentation/SKILL.md`)
|
||||
8. Readiness and release — release-engineering (`../../release-engineering/SKILL.md`), site-reliability-engineering (`../../site-reliability-engineering/SKILL.md`)
|
||||
1. Intake and framing — ../../product-discovery/SKILL.md (`../../product-discovery/SKILL.md`)
|
||||
2. Current-state discovery — ../../software-architecture-analysis/SKILL.md (`../../software-architecture-analysis/SKILL.md`), ../../systematic-debugging/SKILL.md (`../../systematic-debugging/SKILL.md`)
|
||||
3. Design — ../../api-design-and-evolution/SKILL.md (`../../api-design-and-evolution/SKILL.md`), ../../product-design-and-ux/SKILL.md (`../../product-design-and-ux/SKILL.md`)
|
||||
4. Specification — ../../spec-driven-development/SKILL.md (`../../spec-driven-development/SKILL.md`)
|
||||
5. Test planning — ../../qa-methodology/SKILL.md (`../../qa-methodology/SKILL.md`)
|
||||
6. Implementation — ../../secure-software-engineering/SKILL.md (`../../secure-software-engineering/SKILL.md`), ../../web-accessibility/SKILL.md (`../../web-accessibility/SKILL.md`)
|
||||
7. Review and verification — ../../verification-methodology/SKILL.md (`../../verification-methodology/SKILL.md`), ../../technical-documentation/SKILL.md (`../../technical-documentation/SKILL.md`)
|
||||
8. Readiness and release — ../../release-engineering/SKILL.md (`../../release-engineering/SKILL.md`), ../../site-reliability-engineering/SKILL.md (`../../site-reliability-engineering/SKILL.md`)
|
||||
- **Included skills:**
|
||||
- product-discovery (`../../product-discovery/SKILL.md`)
|
||||
- software-architecture-analysis (`../../software-architecture-analysis/SKILL.md`)
|
||||
- systematic-debugging (`../../systematic-debugging/SKILL.md`)
|
||||
- api-design-and-evolution (`../../api-design-and-evolution/SKILL.md`)
|
||||
- product-design-and-ux (`../../product-design-and-ux/SKILL.md`)
|
||||
- spec-driven-development (`../../spec-driven-development/SKILL.md`)
|
||||
- qa-methodology (`../../qa-methodology/SKILL.md`)
|
||||
- secure-software-engineering (`../../secure-software-engineering/SKILL.md`)
|
||||
- web-accessibility (`../../web-accessibility/SKILL.md`)
|
||||
- verification-methodology (`../../verification-methodology/SKILL.md`)
|
||||
- technical-documentation (`../../technical-documentation/SKILL.md`)
|
||||
- release-engineering (`../../release-engineering/SKILL.md`)
|
||||
- site-reliability-engineering (`../../site-reliability-engineering/SKILL.md`)
|
||||
- ../../product-discovery/SKILL.md (`../../product-discovery/SKILL.md`)
|
||||
- ../../software-architecture-analysis/SKILL.md (`../../software-architecture-analysis/SKILL.md`)
|
||||
- ../../systematic-debugging/SKILL.md (`../../systematic-debugging/SKILL.md`)
|
||||
- ../../api-design-and-evolution/SKILL.md (`../../api-design-and-evolution/SKILL.md`)
|
||||
- ../../product-design-and-ux/SKILL.md (`../../product-design-and-ux/SKILL.md`)
|
||||
- ../../spec-driven-development/SKILL.md (`../../spec-driven-development/SKILL.md`)
|
||||
- ../../qa-methodology/SKILL.md (`../../qa-methodology/SKILL.md`)
|
||||
- ../../secure-software-engineering/SKILL.md (`../../secure-software-engineering/SKILL.md`)
|
||||
- ../../web-accessibility/SKILL.md (`../../web-accessibility/SKILL.md`)
|
||||
- ../../verification-methodology/SKILL.md (`../../verification-methodology/SKILL.md`)
|
||||
- ../../technical-documentation/SKILL.md (`../../technical-documentation/SKILL.md`)
|
||||
- ../../release-engineering/SKILL.md (`../../release-engineering/SKILL.md`)
|
||||
- ../../site-reliability-engineering/SKILL.md (`../../site-reliability-engineering/SKILL.md`)
|
||||
- **Prerequisites:**
|
||||
- A non-trivial change request, issue, or task with a verifiable contract
|
||||
- Current-state evidence (repository, tests, config, recent history) — via software-architecture-analysis (`../../software-architecture-analysis/SKILL.md`)
|
||||
- Change contract and evidence ledger entries — via verification-methodology (`../../verification-methodology/SKILL.md`)
|
||||
- Current-state evidence (repository, tests, config, recent history) — via ../../software-architecture-analysis/SKILL.md (`../../software-architecture-analysis/SKILL.md`)
|
||||
- Change contract and evidence ledger entries — via ../../verification-methodology/SKILL.md (`../../verification-methodology/SKILL.md`)
|
||||
- **Outputs:** change-contract, evidence-ledger, delivery-packet, implementation-plan, verification-report, release-record
|
||||
- **Handoffs:**
|
||||
- verification-report → verification-methodology — The verification report records the declared verification target and the boundary actually exercised; verdicts bind to the exact head and never claim a boundary that was not checked.
|
||||
@@ -196,73 +196,73 @@ the migration path, and the field definitions. Regenerate with
|
||||
- delivery-packet → human reviewer — Change-request journeys hand the delivery packet — gates and evidence — to the required review before merge; a timed-out review is inconclusive, not a reason to launch repeated review rounds.
|
||||
- evidence-ledger → next change (via evidence ledger) — Each run emits a compact evidence record (intent, inspected artifacts, assumptions, rejected alternatives, checks run, observed outputs, unverified boundaries) that carries learning into the next change.
|
||||
- **Conflicts:**
|
||||
- product-discovery (`../../product-discovery/SKILL.md`) with product-lifecycle — Product discovery is shared. Route by context: neckbeard loads it for intake and framing of a change request; product-lifecycle owns the full discovery phase of a product lifecycle.
|
||||
- product-design-and-ux (`../../product-design-and-ux/SKILL.md`) with product-lifecycle — Product design is shared. neckbeard loads it for user-facing behavior, interaction, and information architecture during design; product-lifecycle owns the UX and requirements phase of a product.
|
||||
- spec-driven-development (`../../spec-driven-development/SKILL.md`) with product-lifecycle — Specification is shared. neckbeard uses it for formal specification and phase gates on a change request; product-lifecycle uses it for requirements and acceptance criteria in its lifecycle phases.
|
||||
- qa-methodology (`../../qa-methodology/SKILL.md`) with product-lifecycle — QA methodology is shared. neckbeard loads it for test strategy and regression gates on a change; product-lifecycle routes to it for phase 6 quality gates.
|
||||
- qa-methodology (`../../qa-methodology/SKILL.md`) with production-excellence — QA methodology is shared. neckbeard loads it for change-request test planning; production-excellence uses it for launch verification evidence.
|
||||
- secure-software-engineering (`../../secure-software-engineering/SKILL.md`) with product-lifecycle — Security engineering is shared. Route by context: change-level security review and threat modeling (neckbeard) versus lifecycle-phase security needs (product-lifecycle).
|
||||
- secure-software-engineering (`../../secure-software-engineering/SKILL.md`) with production-excellence — Security engineering is shared. Route by context: change-level security review (neckbeard) versus launch-gate security evidence (production-excellence).
|
||||
- secure-software-engineering (`../../secure-software-engineering/SKILL.md`) with agent-production-operations — Security engineering is shared. Route by context: change-level security review (neckbeard) versus agent authority contracts and disablement security (agent-production-operations).
|
||||
- verification-methodology (`../../verification-methodology/SKILL.md`) with product-lifecycle — Verification methodology is shared. neckbeard requires it to exercise the declared verification boundary on a change; product-lifecycle uses it at every phase gate for evidence.
|
||||
- verification-methodology (`../../verification-methodology/SKILL.md`) with production-excellence — Verification methodology is shared. neckbeard uses it for change-request verification verdicts; production-excellence uses it for boundary labeling of launch evidence.
|
||||
- release-engineering (`../../release-engineering/SKILL.md`) with product-lifecycle — Release engineering is shared. Route by context: change-request release planning (neckbeard) versus lifecycle delivery handoff (product-lifecycle).
|
||||
- release-engineering (`../../release-engineering/SKILL.md`) with production-excellence — Release engineering is shared. Route by context: change-request release planning (neckbeard) versus launch-gate release evidence (production-excellence).
|
||||
- release-engineering (`../../release-engineering/SKILL.md`) with agent-production-operations — Release engineering is shared. Route by context: change-request release planning (neckbeard) versus agent staged-rollout planning (agent-production-operations).
|
||||
- site-reliability-engineering (`../../site-reliability-engineering/SKILL.md`) with product-lifecycle — SRE is shared. neckbeard routes to it for reliability and operational recovery of a delivered change; product-lifecycle routes to it for delivery reliability.
|
||||
- site-reliability-engineering (`../../site-reliability-engineering/SKILL.md`) with production-excellence — SRE is shared. Route by context: change-level reliability (neckbeard) versus gate-entry SLO/error-budget evidence (production-excellence).
|
||||
- site-reliability-engineering (`../../site-reliability-engineering/SKILL.md`) with agent-production-operations — SRE is shared. Route by context: change-level reliability (neckbeard) versus agent runtime latency/cost budgets and incident handoff (agent-production-operations).
|
||||
- ../../product-discovery/SKILL.md (`../../product-discovery/SKILL.md`) with product-lifecycle — Product discovery is shared. Route by context: neckbeard loads it for intake and framing of a change request; product-lifecycle owns the full discovery phase of a product lifecycle.
|
||||
- ../../product-design-and-ux/SKILL.md (`../../product-design-and-ux/SKILL.md`) with product-lifecycle — Product design is shared. neckbeard loads it for user-facing behavior, interaction, and information architecture during design; product-lifecycle owns the UX and requirements phase of a product.
|
||||
- ../../spec-driven-development/SKILL.md (`../../spec-driven-development/SKILL.md`) with product-lifecycle — Specification is shared. neckbeard uses it for formal specification and phase gates on a change request; product-lifecycle uses it for requirements and acceptance criteria in its lifecycle phases.
|
||||
- ../../qa-methodology/SKILL.md (`../../qa-methodology/SKILL.md`) with product-lifecycle — QA methodology is shared. neckbeard loads it for test strategy and regression gates on a change; product-lifecycle routes to it for phase 6 quality gates.
|
||||
- ../../qa-methodology/SKILL.md (`../../qa-methodology/SKILL.md`) with production-excellence — QA methodology is shared. neckbeard loads it for change-request test planning; production-excellence uses it for launch verification evidence.
|
||||
- ../../secure-software-engineering/SKILL.md (`../../secure-software-engineering/SKILL.md`) with product-lifecycle — Security engineering is shared. Route by context: change-level security review and threat modeling (neckbeard) versus lifecycle-phase security needs (product-lifecycle).
|
||||
- ../../secure-software-engineering/SKILL.md (`../../secure-software-engineering/SKILL.md`) with production-excellence — Security engineering is shared. Route by context: change-level security review (neckbeard) versus launch-gate security evidence (production-excellence).
|
||||
- ../../secure-software-engineering/SKILL.md (`../../secure-software-engineering/SKILL.md`) with agent-production-operations — Security engineering is shared. Route by context: change-level security review (neckbeard) versus agent authority contracts and disablement security (agent-production-operations).
|
||||
- ../../verification-methodology/SKILL.md (`../../verification-methodology/SKILL.md`) with product-lifecycle — Verification methodology is shared. neckbeard requires it to exercise the declared verification boundary on a change; product-lifecycle uses it at every phase gate for evidence.
|
||||
- ../../verification-methodology/SKILL.md (`../../verification-methodology/SKILL.md`) with production-excellence — Verification methodology is shared. neckbeard uses it for change-request verification verdicts; production-excellence uses it for boundary labeling of launch evidence.
|
||||
- ../../release-engineering/SKILL.md (`../../release-engineering/SKILL.md`) with product-lifecycle — Release engineering is shared. Route by context: change-request release planning (neckbeard) versus lifecycle delivery handoff (product-lifecycle).
|
||||
- ../../release-engineering/SKILL.md (`../../release-engineering/SKILL.md`) with production-excellence — Release engineering is shared. Route by context: change-request release planning (neckbeard) versus launch-gate release evidence (production-excellence).
|
||||
- ../../release-engineering/SKILL.md (`../../release-engineering/SKILL.md`) with agent-production-operations — Release engineering is shared. Route by context: change-request release planning (neckbeard) versus agent staged-rollout planning (agent-production-operations).
|
||||
- ../../site-reliability-engineering/SKILL.md (`../../site-reliability-engineering/SKILL.md`) with product-lifecycle — SRE is shared. neckbeard routes to it for reliability and operational recovery of a delivered change; product-lifecycle routes to it for delivery reliability.
|
||||
- ../../site-reliability-engineering/SKILL.md (`../../site-reliability-engineering/SKILL.md`) with production-excellence — SRE is shared. Route by context: change-level reliability (neckbeard) versus gate-entry SLO/error-budget evidence (production-excellence).
|
||||
- ../../site-reliability-engineering/SKILL.md (`../../site-reliability-engineering/SKILL.md`) with agent-production-operations — SRE is shared. Route by context: change-level reliability (neckbeard) versus agent runtime latency/cost budgets and incident handoff (agent-production-operations).
|
||||
- **Eval suite:** evals/evals.json
|
||||
|
||||
### product-lifecycle
|
||||
|
||||
- Derivation: `manifest` — source: `bundles/product-lifecycle/manifest.yaml`
|
||||
- Derivation: `manifest` — source: `product-lifecycle/manifest.yaml`
|
||||
- **Purpose:** Route a product through its full lifecycle — discovery, strategy and portfolio choice, roadmap, UX and requirements, experimentation, delivery handoff, adoption, success, and lifecycle review — by composing existing specialist product skills with phase-entry evidence, handoff artifacts, and escalation rules.
|
||||
- **Audience:** Product managers, product operations, and portfolio teams navigating a product across multiple lifecycle phases; agents that need to know which specialist skill to load at each phase and what evidence to hand off to the next phase.
|
||||
- **Stages (ordered):**
|
||||
1. Discovery — product-discovery (`../../product-discovery/SKILL.md`)
|
||||
2. Strategy and portfolio choice — product-strategy (`../../product-strategy/SKILL.md`), strategy-frameworks (`../../strategy-frameworks/SKILL.md`)
|
||||
3. Roadmap — product-roadmapping-and-portfolio (`../../product-roadmapping-and-portfolio/SKILL.md`)
|
||||
4. UX and requirements — product-design-and-ux (`../../product-design-and-ux/SKILL.md`)
|
||||
5. Experimentation — product-experimentation (`../../product-experimentation/SKILL.md`)
|
||||
6. Delivery handoff — implementation-planning (`../../implementation-planning/SKILL.md`), production-readiness (`../../production-readiness/SKILL.md`), release-engineering (`../../release-engineering/SKILL.md`)
|
||||
7. Adoption — product-adoption (`../../product-adoption/SKILL.md`)
|
||||
8. Success — product-analytics-and-measurement (`../../product-analytics-and-measurement/SKILL.md`), conditional-customer-success (`../../conditional-customer-success/SKILL.md`)
|
||||
9. Lifecycle review — product-lifecycle-learning (`../../product-lifecycle-learning/SKILL.md`)
|
||||
1. Discovery — ../../product-discovery/SKILL.md (`../../product-discovery/SKILL.md`)
|
||||
2. Strategy and portfolio choice — ../../product-strategy/SKILL.md (`../../product-strategy/SKILL.md`), ../../strategy-frameworks/SKILL.md (`../../strategy-frameworks/SKILL.md`)
|
||||
3. Roadmap — ../../product-roadmapping-and-portfolio/SKILL.md (`../../product-roadmapping-and-portfolio/SKILL.md`)
|
||||
4. UX and requirements — ../../product-design-and-ux/SKILL.md (`../../product-design-and-ux/SKILL.md`)
|
||||
5. Experimentation — ../../product-experimentation/SKILL.md (`../../product-experimentation/SKILL.md`)
|
||||
6. Delivery handoff — ../../implementation-planning/SKILL.md (`../../implementation-planning/SKILL.md`), ../../production-readiness/SKILL.md (`../../production-readiness/SKILL.md`), ../../release-engineering/SKILL.md (`../../release-engineering/SKILL.md`)
|
||||
7. Adoption — ../../product-adoption/SKILL.md (`../../product-adoption/SKILL.md`)
|
||||
8. Success — ../../product-analytics-and-measurement/SKILL.md (`../../product-analytics-and-measurement/SKILL.md`), ../../conditional-customer-success/SKILL.md (`../../conditional-customer-success/SKILL.md`)
|
||||
9. Lifecycle review — ../../product-lifecycle-learning/SKILL.md (`../../product-lifecycle-learning/SKILL.md`)
|
||||
- **Included skills:**
|
||||
- product-discovery (`../../product-discovery/SKILL.md`)
|
||||
- product-strategy (`../../product-strategy/SKILL.md`)
|
||||
- strategy-frameworks (`../../strategy-frameworks/SKILL.md`)
|
||||
- product-roadmapping-and-portfolio (`../../product-roadmapping-and-portfolio/SKILL.md`)
|
||||
- product-design-and-ux (`../../product-design-and-ux/SKILL.md`)
|
||||
- product-experimentation (`../../product-experimentation/SKILL.md`)
|
||||
- implementation-planning (`../../implementation-planning/SKILL.md`)
|
||||
- production-readiness (`../../production-readiness/SKILL.md`)
|
||||
- release-engineering (`../../release-engineering/SKILL.md`)
|
||||
- product-adoption (`../../product-adoption/SKILL.md`)
|
||||
- product-analytics-and-measurement (`../../product-analytics-and-measurement/SKILL.md`)
|
||||
- conditional-customer-success (`../../conditional-customer-success/SKILL.md`)
|
||||
- product-lifecycle-learning (`../../product-lifecycle-learning/SKILL.md`)
|
||||
- product-methodology (`../../product-methodology/SKILL.md`)
|
||||
- product-operations-and-governance (`../../product-operations-and-governance/SKILL.md`)
|
||||
- financial-modeling (`../../financial-modeling/SKILL.md`)
|
||||
- go-to-market (`../../go-to-market/SKILL.md`)
|
||||
- data-scientist (`../../data-scientist/SKILL.md`)
|
||||
- spec-driven-development (`../../spec-driven-development/SKILL.md`)
|
||||
- privacy-engineering (`../../privacy-engineering/SKILL.md`)
|
||||
- secure-software-engineering (`../../secure-software-engineering/SKILL.md`)
|
||||
- verification-methodology (`../../verification-methodology/SKILL.md`)
|
||||
- qa-methodology (`../../qa-methodology/SKILL.md`)
|
||||
- site-reliability-engineering (`../../site-reliability-engineering/SKILL.md`)
|
||||
- platform-engineering (`../../platform-engineering/SKILL.md`)
|
||||
- neckbeard (`../../bundles/neckbeard/SKILL.md`)
|
||||
- ../../product-discovery/SKILL.md (`../../product-discovery/SKILL.md`)
|
||||
- ../../product-strategy/SKILL.md (`../../product-strategy/SKILL.md`)
|
||||
- ../../strategy-frameworks/SKILL.md (`../../strategy-frameworks/SKILL.md`)
|
||||
- ../../product-roadmapping-and-portfolio/SKILL.md (`../../product-roadmapping-and-portfolio/SKILL.md`)
|
||||
- ../../product-design-and-ux/SKILL.md (`../../product-design-and-ux/SKILL.md`)
|
||||
- ../../product-experimentation/SKILL.md (`../../product-experimentation/SKILL.md`)
|
||||
- ../../implementation-planning/SKILL.md (`../../implementation-planning/SKILL.md`)
|
||||
- ../../production-readiness/SKILL.md (`../../production-readiness/SKILL.md`)
|
||||
- ../../release-engineering/SKILL.md (`../../release-engineering/SKILL.md`)
|
||||
- ../../product-adoption/SKILL.md (`../../product-adoption/SKILL.md`)
|
||||
- ../../product-analytics-and-measurement/SKILL.md (`../../product-analytics-and-measurement/SKILL.md`)
|
||||
- ../../conditional-customer-success/SKILL.md (`../../conditional-customer-success/SKILL.md`)
|
||||
- ../../product-lifecycle-learning/SKILL.md (`../../product-lifecycle-learning/SKILL.md`)
|
||||
- ../../product-methodology/SKILL.md (`../../product-methodology/SKILL.md`)
|
||||
- ../../product-operations-and-governance/SKILL.md (`../../product-operations-and-governance/SKILL.md`)
|
||||
- ../../financial-modeling/SKILL.md (`../../financial-modeling/SKILL.md`)
|
||||
- ../../go-to-market/SKILL.md (`../../go-to-market/SKILL.md`)
|
||||
- ../../data-scientist/SKILL.md (`../../data-scientist/SKILL.md`)
|
||||
- ../../spec-driven-development/SKILL.md (`../../spec-driven-development/SKILL.md`)
|
||||
- ../../privacy-engineering/SKILL.md (`../../privacy-engineering/SKILL.md`)
|
||||
- ../../secure-software-engineering/SKILL.md (`../../secure-software-engineering/SKILL.md`)
|
||||
- ../../verification-methodology/SKILL.md (`../../verification-methodology/SKILL.md`)
|
||||
- ../../qa-methodology/SKILL.md (`../../qa-methodology/SKILL.md`)
|
||||
- ../../site-reliability-engineering/SKILL.md (`../../site-reliability-engineering/SKILL.md`)
|
||||
- ../../platform-engineering/SKILL.md (`../../platform-engineering/SKILL.md`)
|
||||
- ../../bundles/neckbeard/SKILL.md (`../../bundles/neckbeard/SKILL.md`)
|
||||
- **Prerequisites:**
|
||||
- Product idea, market signal, or stakeholder request
|
||||
- Problem statement and discovery log — via product-discovery (`../../product-discovery/SKILL.md`)
|
||||
- Strategic assessment and portfolio decision — via product-strategy (`../../product-strategy/SKILL.md`)
|
||||
- Roadmap entry and bet record — via product-roadmapping-and-portfolio (`../../product-roadmapping-and-portfolio/SKILL.md`)
|
||||
- UX contracts and acceptance criteria — via product-design-and-ux (`../../product-design-and-ux/SKILL.md`)
|
||||
- Experiment readout and assumptions register — via product-experimentation (`../../product-experimentation/SKILL.md`)
|
||||
- Problem statement and discovery log — via ../../product-discovery/SKILL.md (`../../product-discovery/SKILL.md`)
|
||||
- Strategic assessment and portfolio decision — via ../../product-strategy/SKILL.md (`../../product-strategy/SKILL.md`)
|
||||
- Roadmap entry and bet record — via ../../product-roadmapping-and-portfolio/SKILL.md (`../../product-roadmapping-and-portfolio/SKILL.md`)
|
||||
- UX contracts and acceptance criteria — via ../../product-design-and-ux/SKILL.md (`../../product-design-and-ux/SKILL.md`)
|
||||
- Experiment readout and assumptions register — via ../../product-experimentation/SKILL.md (`../../product-experimentation/SKILL.md`)
|
||||
- **Outputs:** lifecycle-evidence-ledger, problem-statement, strategic-assessment, roadmap-entry, interface-contracts, experiment-brief, implementation-plan, readiness-verdict, release-plan, adoption-plan, outcome-measurement, outcome-review, lifecycle-decision
|
||||
- **Handoffs:**
|
||||
- readiness-verdict → production-excellence bundle — Phase 6 delivery handoff routes the production-readiness verdict to the production-excellence launch gate when that bundle is available.
|
||||
@@ -270,52 +270,52 @@ the migration path, and the field definitions. Regenerate with
|
||||
- lifecycle-evidence-ledger → next phase (via evidence ledger) — Every phase reads and writes the shared lifecycle evidence ledger; the next phase never re-derives prior-phase evidence.
|
||||
- lifecycle-decision → product-lifecycle-learning — Phase 9 records the continue/improve/harvest/pivot/pause/retire decision and retained learning in the learning loop.
|
||||
- **Conflicts:**
|
||||
- production-readiness (`../../production-readiness/SKILL.md`) with production-excellence — Both bundles include production-readiness. Use production-excellence for launch-gate decisions; use product-lifecycle for phase 6 delivery handoff routing. Load the bundle matching the active decision context, never both at once.
|
||||
- production-readiness (`../../production-readiness/SKILL.md`) with agent-production-operations — agent-production-operations consumes readiness outcomes as authority- gating inputs. Route phase 6 readiness reviews here; runtime authority decisions go to agent-production-operations.
|
||||
- release-engineering (`../../release-engineering/SKILL.md`) with production-excellence — Release engineering is shared. Route by context: lifecycle delivery handoff (this bundle) versus gate-entry release evidence (production-excellence).
|
||||
- release-engineering (`../../release-engineering/SKILL.md`) with agent-production-operations — Release engineering is shared. Route by context: lifecycle delivery handoff (this bundle) versus agent staged-rollout planning (agent-production-operations).
|
||||
- site-reliability-engineering (`../../site-reliability-engineering/SKILL.md`) with production-excellence — SRE is shared. This bundle routes to it for reliability needs in delivery handoff; production-excellence routes to it for gate-entry SLO/error-budget evidence.
|
||||
- site-reliability-engineering (`../../site-reliability-engineering/SKILL.md`) with agent-production-operations — SRE is shared. This bundle uses it for delivery reliability; agent-production-operations uses it for runtime latency/cost budgets and incident handoff.
|
||||
- secure-software-engineering (`../../secure-software-engineering/SKILL.md`) with production-excellence — Security engineering is shared. Route by phase/domain: trust-boundary work in lifecycle phases (this bundle) versus security evidence for launch gates (production-excellence).
|
||||
- secure-software-engineering (`../../secure-software-engineering/SKILL.md`) with agent-production-operations — Security engineering is shared. Route by context: lifecycle-phase security needs (this bundle) versus agent authority contracts and disablement security (agent-production-operations).
|
||||
- platform-engineering (`../../platform-engineering/SKILL.md`) with production-excellence — Platform engineering is shared. Route by context: lifecycle delivery handoff (this bundle) versus gate-entry platform evidence (production-excellence).
|
||||
- platform-engineering (`../../platform-engineering/SKILL.md`) with agent-production-operations — Platform engineering is shared. Route by context: lifecycle delivery handoff (this bundle) versus agent sandboxing and tool-execution isolation (agent-production-operations).
|
||||
- privacy-engineering (`../../privacy-engineering/SKILL.md`) with agent-production-operations — Privacy engineering is shared. This bundle routes to it for PII, consent, retention, and data flows in any phase; agent-production-operations routes to it for trace scrubbing and user-data-access grants.
|
||||
- qa-methodology (`../../qa-methodology/SKILL.md`) with production-excellence — QA methodology is shared. Route by context: lifecycle phase 6 quality gates (this bundle) versus launch verification evidence (production-excellence).
|
||||
- verification-methodology (`../../verification-methodology/SKILL.md`) with production-excellence — Verification methodology is shared. This bundle uses it at every phase gate for evidence; production-excellence uses it for boundary labeling of launch evidence.
|
||||
- ../../production-readiness/SKILL.md (`../../production-readiness/SKILL.md`) with production-excellence — Both bundles include production-readiness. Use production-excellence for launch-gate decisions; use product-lifecycle for phase 6 delivery handoff routing. Load the bundle matching the active decision context, never both at once.
|
||||
- ../../production-readiness/SKILL.md (`../../production-readiness/SKILL.md`) with agent-production-operations — agent-production-operations consumes readiness outcomes as authority- gating inputs. Route phase 6 readiness reviews here; runtime authority decisions go to agent-production-operations.
|
||||
- ../../release-engineering/SKILL.md (`../../release-engineering/SKILL.md`) with production-excellence — Release engineering is shared. Route by context: lifecycle delivery handoff (this bundle) versus gate-entry release evidence (production-excellence).
|
||||
- ../../release-engineering/SKILL.md (`../../release-engineering/SKILL.md`) with agent-production-operations — Release engineering is shared. Route by context: lifecycle delivery handoff (this bundle) versus agent staged-rollout planning (agent-production-operations).
|
||||
- ../../site-reliability-engineering/SKILL.md (`../../site-reliability-engineering/SKILL.md`) with production-excellence — SRE is shared. This bundle routes to it for reliability needs in delivery handoff; production-excellence routes to it for gate-entry SLO/error-budget evidence.
|
||||
- ../../site-reliability-engineering/SKILL.md (`../../site-reliability-engineering/SKILL.md`) with agent-production-operations — SRE is shared. This bundle uses it for delivery reliability; agent-production-operations uses it for runtime latency/cost budgets and incident handoff.
|
||||
- ../../secure-software-engineering/SKILL.md (`../../secure-software-engineering/SKILL.md`) with production-excellence — Security engineering is shared. Route by phase/domain: trust-boundary work in lifecycle phases (this bundle) versus security evidence for launch gates (production-excellence).
|
||||
- ../../secure-software-engineering/SKILL.md (`../../secure-software-engineering/SKILL.md`) with agent-production-operations — Security engineering is shared. Route by context: lifecycle-phase security needs (this bundle) versus agent authority contracts and disablement security (agent-production-operations).
|
||||
- ../../platform-engineering/SKILL.md (`../../platform-engineering/SKILL.md`) with production-excellence — Platform engineering is shared. Route by context: lifecycle delivery handoff (this bundle) versus gate-entry platform evidence (production-excellence).
|
||||
- ../../platform-engineering/SKILL.md (`../../platform-engineering/SKILL.md`) with agent-production-operations — Platform engineering is shared. Route by context: lifecycle delivery handoff (this bundle) versus agent sandboxing and tool-execution isolation (agent-production-operations).
|
||||
- ../../privacy-engineering/SKILL.md (`../../privacy-engineering/SKILL.md`) with agent-production-operations — Privacy engineering is shared. This bundle routes to it for PII, consent, retention, and data flows in any phase; agent-production-operations routes to it for trace scrubbing and user-data-access grants.
|
||||
- ../../qa-methodology/SKILL.md (`../../qa-methodology/SKILL.md`) with production-excellence — QA methodology is shared. Route by context: lifecycle phase 6 quality gates (this bundle) versus launch verification evidence (production-excellence).
|
||||
- ../../verification-methodology/SKILL.md (`../../verification-methodology/SKILL.md`) with production-excellence — Verification methodology is shared. This bundle uses it at every phase gate for evidence; production-excellence uses it for boundary labeling of launch evidence.
|
||||
- **Eval suite:** evals/evals.json
|
||||
|
||||
### production-excellence
|
||||
|
||||
- Derivation: `manifest` — source: `bundles/production-excellence/manifest.yaml`
|
||||
- Derivation: `manifest` — source: `production-excellence/manifest.yaml`
|
||||
- **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 (ordered):**
|
||||
1. Cross-domain evidence assembly — production-readiness (`../../production-readiness/SKILL.md`), migration-engineering (`../../migration-engineering/SKILL.md`), resilience-and-recovery (`../../resilience-and-recovery/SKILL.md`), capacity-and-cost-engineering (`../../capacity-and-cost-engineering/SKILL.md`), incident-learning (`../../incident-learning/SKILL.md`)
|
||||
2. Gate evaluation — production-readiness (`../../production-readiness/SKILL.md`), site-reliability-engineering (`../../site-reliability-engineering/SKILL.md`), verification-methodology (`../../verification-methodology/SKILL.md`), qa-methodology (`../../qa-methodology/SKILL.md`)
|
||||
3. Operational handoff — release-engineering (`../../release-engineering/SKILL.md`), platform-engineering (`../../platform-engineering/SKILL.md`), secure-software-engineering (`../../secure-software-engineering/SKILL.md`), data-engineering (`../../data-engineering/SKILL.md`)
|
||||
4. Post-launch learning — incident-learning (`../../incident-learning/SKILL.md`)
|
||||
1. Cross-domain evidence assembly — ../../production-readiness/SKILL.md (`../../production-readiness/SKILL.md`), ../../migration-engineering/SKILL.md (`../../migration-engineering/SKILL.md`), ../../resilience-and-recovery/SKILL.md (`../../resilience-and-recovery/SKILL.md`), ../../capacity-and-cost-engineering/SKILL.md (`../../capacity-and-cost-engineering/SKILL.md`), ../../incident-learning/SKILL.md (`../../incident-learning/SKILL.md`)
|
||||
2. Gate evaluation — ../../production-readiness/SKILL.md (`../../production-readiness/SKILL.md`), ../../site-reliability-engineering/SKILL.md (`../../site-reliability-engineering/SKILL.md`), ../../verification-methodology/SKILL.md (`../../verification-methodology/SKILL.md`), ../../qa-methodology/SKILL.md (`../../qa-methodology/SKILL.md`)
|
||||
3. Operational handoff — ../../release-engineering/SKILL.md (`../../release-engineering/SKILL.md`), ../../platform-engineering/SKILL.md (`../../platform-engineering/SKILL.md`), ../../secure-software-engineering/SKILL.md (`../../secure-software-engineering/SKILL.md`), ../../data-engineering/SKILL.md (`../../data-engineering/SKILL.md`)
|
||||
4. Post-launch learning — ../../incident-learning/SKILL.md (`../../incident-learning/SKILL.md`)
|
||||
- **Included skills:**
|
||||
- production-readiness (`../../production-readiness/SKILL.md`)
|
||||
- migration-engineering (`../../migration-engineering/SKILL.md`)
|
||||
- resilience-and-recovery (`../../resilience-and-recovery/SKILL.md`)
|
||||
- capacity-and-cost-engineering (`../../capacity-and-cost-engineering/SKILL.md`)
|
||||
- incident-learning (`../../incident-learning/SKILL.md`)
|
||||
- site-reliability-engineering (`../../site-reliability-engineering/SKILL.md`)
|
||||
- release-engineering (`../../release-engineering/SKILL.md`)
|
||||
- platform-engineering (`../../platform-engineering/SKILL.md`)
|
||||
- secure-software-engineering (`../../secure-software-engineering/SKILL.md`)
|
||||
- data-engineering (`../../data-engineering/SKILL.md`)
|
||||
- qa-methodology (`../../qa-methodology/SKILL.md`)
|
||||
- verification-methodology (`../../verification-methodology/SKILL.md`)
|
||||
- ../../production-readiness/SKILL.md (`../../production-readiness/SKILL.md`)
|
||||
- ../../migration-engineering/SKILL.md (`../../migration-engineering/SKILL.md`)
|
||||
- ../../resilience-and-recovery/SKILL.md (`../../resilience-and-recovery/SKILL.md`)
|
||||
- ../../capacity-and-cost-engineering/SKILL.md (`../../capacity-and-cost-engineering/SKILL.md`)
|
||||
- ../../incident-learning/SKILL.md (`../../incident-learning/SKILL.md`)
|
||||
- ../../site-reliability-engineering/SKILL.md (`../../site-reliability-engineering/SKILL.md`)
|
||||
- ../../release-engineering/SKILL.md (`../../release-engineering/SKILL.md`)
|
||||
- ../../platform-engineering/SKILL.md (`../../platform-engineering/SKILL.md`)
|
||||
- ../../secure-software-engineering/SKILL.md (`../../secure-software-engineering/SKILL.md`)
|
||||
- ../../data-engineering/SKILL.md (`../../data-engineering/SKILL.md`)
|
||||
- ../../qa-methodology/SKILL.md (`../../qa-methodology/SKILL.md`)
|
||||
- ../../verification-methodology/SKILL.md (`../../verification-methodology/SKILL.md`)
|
||||
- **Prerequisites:**
|
||||
- Readiness review evidence packet (risk-scaled, 11 categories) — via production-readiness (`../../production-readiness/SKILL.md`)
|
||||
- Migration plan, compatibility windows, and reconciliation evidence — via migration-engineering (`../../migration-engineering/SKILL.md`)
|
||||
- Resilience and recovery evidence (RTO/RPO, restore tests, game days) — via resilience-and-recovery (`../../resilience-and-recovery/SKILL.md`)
|
||||
- Capacity and cost model evidence (demand, scaling, unit cost) — via capacity-and-cost-engineering (`../../capacity-and-cost-engineering/SKILL.md`)
|
||||
- Incident history, causal hypotheses, and verified-closure records — via incident-learning (`../../incident-learning/SKILL.md`)
|
||||
- SLO and error-budget status — via site-reliability-engineering (`../../site-reliability-engineering/SKILL.md`)
|
||||
- Release plan and rollback strategy — via release-engineering (`../../release-engineering/SKILL.md`)
|
||||
- Readiness review evidence packet (risk-scaled, 11 categories) — via ../../production-readiness/SKILL.md (`../../production-readiness/SKILL.md`)
|
||||
- Migration plan, compatibility windows, and reconciliation evidence — via ../../migration-engineering/SKILL.md (`../../migration-engineering/SKILL.md`)
|
||||
- Resilience and recovery evidence (RTO/RPO, restore tests, game days) — via ../../resilience-and-recovery/SKILL.md (`../../resilience-and-recovery/SKILL.md`)
|
||||
- Capacity and cost model evidence (demand, scaling, unit cost) — via ../../capacity-and-cost-engineering/SKILL.md (`../../capacity-and-cost-engineering/SKILL.md`)
|
||||
- Incident history, causal hypotheses, and verified-closure records — via ../../incident-learning/SKILL.md (`../../incident-learning/SKILL.md`)
|
||||
- SLO and error-budget status — via ../../site-reliability-engineering/SKILL.md (`../../site-reliability-engineering/SKILL.md`)
|
||||
- Release plan and rollback strategy — via ../../release-engineering/SKILL.md (`../../release-engineering/SKILL.md`)
|
||||
- **Outputs:** gate-decision, operational-handoff-record, accountable-owner-record, evidence-gap-register
|
||||
- **Handoffs:**
|
||||
- operational-handoff-record → incident-learning — 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.
|
||||
@@ -323,35 +323,35 @@ the migration path, and the field definitions. Regenerate with
|
||||
- gate-decision → agent-production-operations — Readiness outcomes (go/no-go/defer/exception) gate agent authority expansion when the runtime control plane is in use.
|
||||
- accountable-owner-record → service owner — Every gate outcome names an accountable owner and records the evidence supporting it; no gate passes on a bare checklist.
|
||||
- **Conflicts:**
|
||||
- production-readiness (`../../production-readiness/SKILL.md`) with product-lifecycle — 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.
|
||||
- production-readiness (`../../production-readiness/SKILL.md`) with agent-production-operations — 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.
|
||||
- release-engineering (`../../release-engineering/SKILL.md`) with product-lifecycle — Release engineering is shared. Route by context: gate-entry release evidence (this bundle) versus lifecycle delivery handoff (product-lifecycle).
|
||||
- release-engineering (`../../release-engineering/SKILL.md`) with agent-production-operations — Release engineering is shared. Route by context: launch-gate release plans (this bundle) versus agent staged-rollout planning (agent-production-operations).
|
||||
- site-reliability-engineering (`../../site-reliability-engineering/SKILL.md`) with product-lifecycle — SRE is shared. This bundle routes to it for gate-entry SLO/error-budget evidence; product-lifecycle routes to it for delivery reliability.
|
||||
- site-reliability-engineering (`../../site-reliability-engineering/SKILL.md`) with agent-production-operations — 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.
|
||||
- secure-software-engineering (`../../secure-software-engineering/SKILL.md`) with product-lifecycle — Security engineering is shared. Route by context: security evidence for launch gates (this bundle) versus trust-boundary work in lifecycle phases (product-lifecycle).
|
||||
- secure-software-engineering (`../../secure-software-engineering/SKILL.md`) with agent-production-operations — Security engineering is shared. Route by context: launch-gate security evidence (this bundle) versus agent authority contracts and disablement security (agent-production-operations).
|
||||
- platform-engineering (`../../platform-engineering/SKILL.md`) with product-lifecycle — Platform engineering is shared. Route by context: gate-entry platform evidence (this bundle) versus lifecycle delivery handoff (product-lifecycle).
|
||||
- platform-engineering (`../../platform-engineering/SKILL.md`) with agent-production-operations — Platform engineering is shared. Route by context: launch-gate platform evidence (this bundle) versus agent sandboxing and tool-execution isolation (agent-production-operations).
|
||||
- incident-learning (`../../incident-learning/SKILL.md`) with agent-production-operations — 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.
|
||||
- qa-methodology (`../../qa-methodology/SKILL.md`) with product-lifecycle — QA methodology is shared. Route by context: launch verification evidence (this bundle) versus lifecycle phase 6 quality gates (product-lifecycle).
|
||||
- verification-methodology (`../../verification-methodology/SKILL.md`) with product-lifecycle — Verification methodology is shared. This bundle uses it for boundary labeling of launch evidence; product-lifecycle uses it at every phase gate.
|
||||
- ../../production-readiness/SKILL.md (`../../production-readiness/SKILL.md`) with product-lifecycle — 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.
|
||||
- ../../production-readiness/SKILL.md (`../../production-readiness/SKILL.md`) with agent-production-operations — 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.
|
||||
- ../../release-engineering/SKILL.md (`../../release-engineering/SKILL.md`) with product-lifecycle — Release engineering is shared. Route by context: gate-entry release evidence (this bundle) versus lifecycle delivery handoff (product-lifecycle).
|
||||
- ../../release-engineering/SKILL.md (`../../release-engineering/SKILL.md`) with agent-production-operations — Release engineering is shared. Route by context: launch-gate release plans (this bundle) versus agent staged-rollout planning (agent-production-operations).
|
||||
- ../../site-reliability-engineering/SKILL.md (`../../site-reliability-engineering/SKILL.md`) with product-lifecycle — SRE is shared. This bundle routes to it for gate-entry SLO/error-budget evidence; product-lifecycle routes to it for delivery reliability.
|
||||
- ../../site-reliability-engineering/SKILL.md (`../../site-reliability-engineering/SKILL.md`) with agent-production-operations — 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.
|
||||
- ../../secure-software-engineering/SKILL.md (`../../secure-software-engineering/SKILL.md`) with product-lifecycle — Security engineering is shared. Route by context: security evidence for launch gates (this bundle) versus trust-boundary work in lifecycle phases (product-lifecycle).
|
||||
- ../../secure-software-engineering/SKILL.md (`../../secure-software-engineering/SKILL.md`) with agent-production-operations — Security engineering is shared. Route by context: launch-gate security evidence (this bundle) versus agent authority contracts and disablement security (agent-production-operations).
|
||||
- ../../platform-engineering/SKILL.md (`../../platform-engineering/SKILL.md`) with product-lifecycle — Platform engineering is shared. Route by context: gate-entry platform evidence (this bundle) versus lifecycle delivery handoff (product-lifecycle).
|
||||
- ../../platform-engineering/SKILL.md (`../../platform-engineering/SKILL.md`) with agent-production-operations — Platform engineering is shared. Route by context: launch-gate platform evidence (this bundle) versus agent sandboxing and tool-execution isolation (agent-production-operations).
|
||||
- ../../incident-learning/SKILL.md (`../../incident-learning/SKILL.md`) with agent-production-operations — 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.
|
||||
- ../../qa-methodology/SKILL.md (`../../qa-methodology/SKILL.md`) with product-lifecycle — QA methodology is shared. Route by context: launch verification evidence (this bundle) versus lifecycle phase 6 quality gates (product-lifecycle).
|
||||
- ../../verification-methodology/SKILL.md (`../../verification-methodology/SKILL.md`) with product-lifecycle — 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
|
||||
|
||||
### research-and-vault
|
||||
|
||||
- Derivation: `manifest` — source: `bundles/research-and-vault/manifest.yaml`
|
||||
- Derivation: `manifest` — source: `research-and-vault/manifest.yaml`
|
||||
- **Purpose:** Chain web research, atomic extraction, and durable knowledge capture into a repeatable research-to-note workflow: capture source URLs and dates before interpretation, extract independent atomic claims before synthesis, and write the durable note only after source coverage and gaps are explicit.
|
||||
- **Audience:** Agents and knowledge workers that repeatedly need the full research-to-note sequence (web research, atomic extraction, durable capture) and want a stable order of operations with a clear handoff artifact instead of ad-hoc steps; not for single lookups or single notes, which route to the domain skill directly.
|
||||
- **Stages (ordered):**
|
||||
1. Web research — research-methodology (`../../research-methodology/SKILL.md`)
|
||||
2. Source capture — research-methodology (`../../research-methodology/SKILL.md`)
|
||||
3. Atomic extraction — research-methodology (`../../research-methodology/SKILL.md`)
|
||||
4. Synthesis and durable capture — research-methodology (`../../research-methodology/SKILL.md`)
|
||||
1. Web research — ../../research-methodology/SKILL.md (`../../research-methodology/SKILL.md`)
|
||||
2. Source capture — ../../research-methodology/SKILL.md (`../../research-methodology/SKILL.md`)
|
||||
3. Atomic extraction — ../../research-methodology/SKILL.md (`../../research-methodology/SKILL.md`)
|
||||
4. Synthesis and durable capture — ../../research-methodology/SKILL.md (`../../research-methodology/SKILL.md`)
|
||||
- **Included skills:**
|
||||
- research-methodology (`../../research-methodology/SKILL.md`)
|
||||
- ../../research-methodology/SKILL.md (`../../research-methodology/SKILL.md`)
|
||||
- **Prerequisites:**
|
||||
- A research question or topic and access to web-research tooling — via research-methodology (`../../research-methodology/SKILL.md`)
|
||||
- A research question or topic and access to web-research tooling — via ../../research-methodology/SKILL.md (`../../research-methodology/SKILL.md`)
|
||||
- **Outputs:** source-capture-record, atomic-claim-extract, durable-note
|
||||
- **Handoffs:**
|
||||
- source-capture-record → research-methodology — Source URLs and dates are captured before interpretation and carried into extraction and synthesis; never interpret a source before its URL and date are recorded.
|
||||
@@ -362,7 +362,7 @@ the migration path, and the field definitions. Regenerate with
|
||||
|
||||
### tailscale
|
||||
|
||||
- Derivation: `manifest` — source: `bundles/tailscale/manifest.yaml`
|
||||
- Derivation: `manifest` — source: `tailscale/manifest.yaml`
|
||||
- **Purpose:** Operate a self-hosted Tailscale/Headscale ecosystem end to end: deploy and manage a Headscale control server, configure Tailscale clients, define ACL policy, manage node lifecycle, advertise subnet routes and exit nodes, operate DERP relays, and back up, restore, or migrate the control plane.
|
||||
- **Audience:** Platform and homelab operators running self-hosted Tailscale/Headscale infrastructure; agents that need to know which sub-skill to load for deploy, policy, client, node, routing, DERP, or backup tasks in a WireGuard mesh.
|
||||
- **Stages (ordered):**
|
||||
@@ -396,7 +396,7 @@ the migration path, and the field definitions. Regenerate with
|
||||
|
||||
### workflow-architect
|
||||
|
||||
- Derivation: `manifest` — source: `bundles/workflow-architect/manifest.yaml`
|
||||
- Derivation: `manifest` — source: `workflow-architect/manifest.yaml`
|
||||
- **Purpose:** Discover a user's actual workflow through active interrogation or passive observation, then generate a tailored Agent Skills bundle that encodes it as loadable skills with trigger conditions, a decision map, a manifest, and an optional kanban board — turning a session that feels aimless into structure.
|
||||
- **Audience:** Users and agents that want to formalize how they work — understand their own process, encode it as trigger-driven skills they can reuse, or share it with collaborators. Not for single factual questions or tasks already owned by a more specific skill.
|
||||
- **Stages (ordered):**
|
||||
|
||||
Reference in New Issue
Block a user