mirror of
https://github.com/magnus919/agent-skills.git
synced 2026-09-11 19:47:12 +03:00
feat(flatten): rewrite moved-file paths for flat layout
Re-point relative references inside the six non-tailscale/workflow-architect
bundle dirs now that they live one level shallower at the repo root:
- bundle-root SKILL.md/manifest.yaml/README.md: ../../<target> -> ../<target>,
cross-bundle ../../bundles/<x> -> ../<x>
- forward-deployed-engineering references/: ../../../<target> -> ../../<target>
- product-lifecycle references cross-bundle ../../bundles/neckbeard -> ../../neckbeard
- product-lifecycle references/discovery-brief.md prose headings drop bundles/ prefix
- neckbeard eval shell commands bundles/neckbeard/eval -> neckbeard/eval
- production-excellence AGENTS.md depth note updated
- manifest header comments point at ../schemas/bundle-manifest-v1.schema.json
- regenerate docs/lifecycle-capability-matrix.{md,json}
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
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
42447b23eb
commit
a315b77bd8
@@ -47,7 +47,7 @@ results gate the next release.
|
||||
## Quick Start
|
||||
|
||||
1. Start with an agent that has passed evaluation (use
|
||||
[agent-evals-and-observability](../../agent-evals-and-observability/SKILL.md)).
|
||||
[agent-evals-and-observability](../agent-evals-and-observability/SKILL.md)).
|
||||
|
||||
2. Define the agent's production contract using
|
||||
[references/agent-production-contract.md](references/agent-production-contract.md).
|
||||
@@ -55,9 +55,9 @@ results gate the next release.
|
||||
|
||||
3. Consume the most recent production-readiness review outcome for the agent's
|
||||
host service from
|
||||
[production-readiness](../../production-readiness/SKILL.md) and any open
|
||||
[production-readiness](../production-readiness/SKILL.md) and any open
|
||||
incident-learning records from
|
||||
[incident-learning](../../incident-learning/SKILL.md). Record both in the
|
||||
[incident-learning](../incident-learning/SKILL.md). Record both in the
|
||||
contract.
|
||||
|
||||
4. Plan versioning, staged rollout, and fallback using
|
||||
|
||||
@@ -44,21 +44,21 @@ Do **not** load this bundle for:
|
||||
- Building or designing an agent from scratch — route to the appropriate
|
||||
framework skill (LangGraph, CrewAI, AutoGen, etc.).
|
||||
- Designing agent evaluations or observability — route to
|
||||
[agent-evals-and-observability](../../agent-evals-and-observability/SKILL.md).
|
||||
[agent-evals-and-observability](../agent-evals-and-observability/SKILL.md).
|
||||
- General release engineering (CI/CD pipelines, artifact promotion) — route to
|
||||
[release-engineering](../../release-engineering/SKILL.md).
|
||||
[release-engineering](../release-engineering/SKILL.md).
|
||||
- General site reliability engineering (incident response, SLO definition,
|
||||
error budgets) — route to
|
||||
[site-reliability-engineering](../../site-reliability-engineering/SKILL.md).
|
||||
[site-reliability-engineering](../site-reliability-engineering/SKILL.md).
|
||||
- General security engineering (threat modeling, vulnerability assessment) —
|
||||
route to [secure-software-engineering](../../secure-software-engineering/SKILL.md).
|
||||
route to [secure-software-engineering](../secure-software-engineering/SKILL.md).
|
||||
- General platform infrastructure (compute, networking, storage) — route to
|
||||
[platform-engineering](../../platform-engineering/SKILL.md).
|
||||
[platform-engineering](../platform-engineering/SKILL.md).
|
||||
- Performing a production-readiness review — route to
|
||||
[production-readiness](../../production-readiness/SKILL.md); this bundle
|
||||
[production-readiness](../production-readiness/SKILL.md); this bundle
|
||||
**consumes** readiness outcomes, it does not produce them.
|
||||
- Conducting an incident postmortem — route to
|
||||
[incident-learning](../../incident-learning/SKILL.md); this bundle
|
||||
[incident-learning](../incident-learning/SKILL.md); this bundle
|
||||
**consumes** incident records as escalation and feedback inputs.
|
||||
|
||||
## Autonomy is not assumed uniform
|
||||
@@ -85,13 +85,13 @@ domain is the active concern; the bundle owns the cross-domain coordination.
|
||||
|
||||
| Concern | Specialist skill | When to load | What the bundle adds |
|
||||
|---|---|---|---|
|
||||
| Agent evaluation and observability | [agent-evals-and-observability](../../agent-evals-and-observability/SKILL.md) | Designing evals, instrumenting observability, detecting regression | Trace-to-eval feedback loop; eval-case generation from production incidents |
|
||||
| Release engineering | [release-engineering](../../release-engineering/SKILL.md) | Release pipeline design, artifact promotion, CI/CD | Agent-specific staged rollout with authority gating; rollback triggers tied to agent health |
|
||||
| Site reliability engineering | [site-reliability-engineering](../../site-reliability-engineering/SKILL.md) | Incident response, SLO/SLI definition, error budgets | Agent-specific latency/cost budgets; tool-health SLOs; escalation handoff to incident command |
|
||||
| Security engineering | [secure-software-engineering](../../secure-software-engineering/SKILL.md) | Threat modeling, trust-boundary validation, secure design | Agent authority contracts with side-effect boundaries; disablement security (revoke, not just stop) |
|
||||
| Platform engineering | [platform-engineering](../../platform-engineering/SKILL.md) | Compute, networking, storage, service infrastructure | Agent sandboxing requirements; tool-execution isolation preferences |
|
||||
| Production readiness | [production-readiness](../../production-readiness/SKILL.md) | Readiness reviews, go/no-go/defer/exception decisions | Consumed as input: readiness outcomes gate agent authority expansion |
|
||||
| Incident learning | [incident-learning](../../incident-learning/SKILL.md) | Post-incident analysis, verified closure, follow-up work | Consumed as input: incident records feed escalation thresholds and eval-case generation |
|
||||
| Agent evaluation and observability | [agent-evals-and-observability](../agent-evals-and-observability/SKILL.md) | Designing evals, instrumenting observability, detecting regression | Trace-to-eval feedback loop; eval-case generation from production incidents |
|
||||
| Release engineering | [release-engineering](../release-engineering/SKILL.md) | Release pipeline design, artifact promotion, CI/CD | Agent-specific staged rollout with authority gating; rollback triggers tied to agent health |
|
||||
| Site reliability engineering | [site-reliability-engineering](../site-reliability-engineering/SKILL.md) | Incident response, SLO/SLI definition, error budgets | Agent-specific latency/cost budgets; tool-health SLOs; escalation handoff to incident command |
|
||||
| Security engineering | [secure-software-engineering](../secure-software-engineering/SKILL.md) | Threat modeling, trust-boundary validation, secure design | Agent authority contracts with side-effect boundaries; disablement security (revoke, not just stop) |
|
||||
| Platform engineering | [platform-engineering](../platform-engineering/SKILL.md) | Compute, networking, storage, service infrastructure | Agent sandboxing requirements; tool-execution isolation preferences |
|
||||
| Production readiness | [production-readiness](../production-readiness/SKILL.md) | Readiness reviews, go/no-go/defer/exception decisions | Consumed as input: readiness outcomes gate agent authority expansion |
|
||||
| Incident learning | [incident-learning](../incident-learning/SKILL.md) | Post-incident analysis, verified closure, follow-up work | Consumed as input: incident records feed escalation thresholds and eval-case generation |
|
||||
|
||||
## Loading protocol
|
||||
|
||||
@@ -169,7 +169,7 @@ used in this bundle. Reference files are loaded on trigger:
|
||||
agent action, and verified closure is not yet complete.
|
||||
- Human operator issues an explicit disable directive.
|
||||
- Tool compromise or credential leak detected (route through
|
||||
[secure-software-engineering](../../secure-software-engineering/SKILL.md)).
|
||||
[secure-software-engineering](../secure-software-engineering/SKILL.md)).
|
||||
- **Action**: revoke all credentials and tokens; remove from routing/load-balancing;
|
||||
record disablement reason, timestamp, and authorizing evidence; notify
|
||||
escalation channel; prevent automatic restart until a new
|
||||
@@ -214,14 +214,14 @@ used in this bundle. Reference files are loaded on trigger:
|
||||
its authority contract.
|
||||
- Agent traces and conversation logs must be scrubbed of PII before entering
|
||||
the trace-to-eval feedback pipeline (route scrubbing design to
|
||||
[privacy-engineering](../../privacy-engineering/SKILL.md)).
|
||||
[privacy-engineering](../privacy-engineering/SKILL.md)).
|
||||
- Data retention for agent traces defaults to 30 days unless a shorter period
|
||||
is specified in the production contract.
|
||||
- Any PII access by a read-only agent triggers immediate escalation (the
|
||||
read-only profile should never touch PII).
|
||||
- **Privacy breach**: any PII access outside the granted scope triggers
|
||||
escalation and a mandatory security review via
|
||||
[secure-software-engineering](../../secure-software-engineering/SKILL.md).
|
||||
[secure-software-engineering](../secure-software-engineering/SKILL.md).
|
||||
|
||||
## Core workflow
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# Bundle manifest (bundle-manifest-v1) — see schemas/bundle-manifest-v1.schema.json
|
||||
# Bundle manifest (bundle-manifest-v1) — see ../schemas/bundle-manifest-v1.schema.json
|
||||
# and docs/bundle-manifest-design.md. Paths are relative to this bundle dir.
|
||||
|
||||
schema_version: 1
|
||||
@@ -19,49 +19,49 @@ audience: >-
|
||||
stages:
|
||||
- name: Contract definition
|
||||
skills:
|
||||
- ../../agent-evals-and-observability/SKILL.md
|
||||
- ../../production-readiness/SKILL.md
|
||||
- ../../incident-learning/SKILL.md
|
||||
- ../agent-evals-and-observability/SKILL.md
|
||||
- ../production-readiness/SKILL.md
|
||||
- ../incident-learning/SKILL.md
|
||||
- name: Versioning and rollout planning
|
||||
skills:
|
||||
- ../../release-engineering/SKILL.md
|
||||
- ../../platform-engineering/SKILL.md
|
||||
- ../release-engineering/SKILL.md
|
||||
- ../platform-engineering/SKILL.md
|
||||
- name: Staged rollout
|
||||
skills:
|
||||
- ../../platform-engineering/SKILL.md
|
||||
- ../../site-reliability-engineering/SKILL.md
|
||||
- ../platform-engineering/SKILL.md
|
||||
- ../site-reliability-engineering/SKILL.md
|
||||
- name: Runtime monitoring
|
||||
skills:
|
||||
- ../../site-reliability-engineering/SKILL.md
|
||||
- ../../secure-software-engineering/SKILL.md
|
||||
- ../site-reliability-engineering/SKILL.md
|
||||
- ../secure-software-engineering/SKILL.md
|
||||
- name: Trace-to-eval feedback
|
||||
skills:
|
||||
- ../../agent-evals-and-observability/SKILL.md
|
||||
- ../agent-evals-and-observability/SKILL.md
|
||||
- name: Learning and disablement
|
||||
skills:
|
||||
- ../../incident-learning/SKILL.md
|
||||
- ../../production-readiness/SKILL.md
|
||||
- ../../privacy-engineering/SKILL.md
|
||||
- ../incident-learning/SKILL.md
|
||||
- ../production-readiness/SKILL.md
|
||||
- ../privacy-engineering/SKILL.md
|
||||
|
||||
included_skills:
|
||||
- ../../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-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
|
||||
|
||||
prerequisites:
|
||||
- artifact: Agent evaluation results and observability instrumentation
|
||||
skill: ../../agent-evals-and-observability/SKILL.md
|
||||
skill: ../agent-evals-and-observability/SKILL.md
|
||||
- artifact: Production-readiness evidence (go/no-go/defer/exception outcomes)
|
||||
skill: ../../production-readiness/SKILL.md
|
||||
skill: ../production-readiness/SKILL.md
|
||||
- artifact: Incident-learning records (verified closure, follow-up work map)
|
||||
skill: ../../incident-learning/SKILL.md
|
||||
skill: ../incident-learning/SKILL.md
|
||||
- artifact: Release pipeline and artifact promotion baseline
|
||||
skill: ../../release-engineering/SKILL.md
|
||||
skill: ../release-engineering/SKILL.md
|
||||
|
||||
outputs:
|
||||
- agent-production-contract
|
||||
@@ -95,72 +95,72 @@ handoffs:
|
||||
authorizing evidence.
|
||||
|
||||
conflicts:
|
||||
- skill: ../../production-readiness/SKILL.md
|
||||
- skill: ../production-readiness/SKILL.md
|
||||
with: production-excellence
|
||||
guidance: >-
|
||||
Both bundles include production-readiness. This bundle consumes
|
||||
readiness outcomes as authority-gating inputs; production-excellence
|
||||
produces the go/no-go/defer/exception decisions.
|
||||
- skill: ../../production-readiness/SKILL.md
|
||||
- skill: ../production-readiness/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
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.
|
||||
- skill: ../../release-engineering/SKILL.md
|
||||
- skill: ../release-engineering/SKILL.md
|
||||
with: production-excellence
|
||||
guidance: >-
|
||||
Release engineering is shared. Route by context: agent staged-rollout
|
||||
planning (this bundle) versus launch-gate release plans
|
||||
(production-excellence).
|
||||
- skill: ../../release-engineering/SKILL.md
|
||||
- skill: ../release-engineering/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
Release engineering is shared. Route by context: agent staged-rollout
|
||||
planning (this bundle) versus lifecycle delivery handoff
|
||||
(product-lifecycle).
|
||||
- skill: ../../site-reliability-engineering/SKILL.md
|
||||
- skill: ../site-reliability-engineering/SKILL.md
|
||||
with: production-excellence
|
||||
guidance: >-
|
||||
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.
|
||||
- skill: ../../site-reliability-engineering/SKILL.md
|
||||
- skill: ../site-reliability-engineering/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
SRE is shared. This bundle uses it for agent runtime budgets;
|
||||
product-lifecycle routes to it for delivery reliability.
|
||||
- skill: ../../secure-software-engineering/SKILL.md
|
||||
- skill: ../secure-software-engineering/SKILL.md
|
||||
with: production-excellence
|
||||
guidance: >-
|
||||
Security engineering is shared. Route by context: agent authority
|
||||
contracts and disablement security (this bundle) versus launch-gate
|
||||
security evidence (production-excellence).
|
||||
- skill: ../../secure-software-engineering/SKILL.md
|
||||
- skill: ../secure-software-engineering/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
Security engineering is shared. Route by context: agent trust-boundary
|
||||
and disablement security (this bundle) versus lifecycle-phase security
|
||||
needs (product-lifecycle).
|
||||
- skill: ../../platform-engineering/SKILL.md
|
||||
- skill: ../platform-engineering/SKILL.md
|
||||
with: production-excellence
|
||||
guidance: >-
|
||||
Platform engineering is shared. Route by context: agent sandboxing and
|
||||
tool-execution isolation (this bundle) versus launch-gate platform
|
||||
evidence (production-excellence).
|
||||
- skill: ../../platform-engineering/SKILL.md
|
||||
- skill: ../platform-engineering/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
Platform engineering is shared. Route by context: agent sandboxing and
|
||||
tool-execution isolation (this bundle) versus lifecycle delivery
|
||||
handoff (product-lifecycle).
|
||||
- skill: ../../incident-learning/SKILL.md
|
||||
- skill: ../incident-learning/SKILL.md
|
||||
with: production-excellence
|
||||
guidance: >-
|
||||
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.
|
||||
- skill: ../../privacy-engineering/SKILL.md
|
||||
- skill: ../privacy-engineering/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
Privacy engineering is shared. This bundle routes to it for trace
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
+239
-239
@@ -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/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 |
|
||||
| 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 |
|
||||
| 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 |
|
||||
|
||||
@@ -27,26 +27,26 @@ the migration path, and the field definitions. Regenerate with
|
||||
- **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/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`)
|
||||
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`)
|
||||
- **Included skills:**
|
||||
- ../../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`)
|
||||
- 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`)
|
||||
- **Prerequisites:**
|
||||
- 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`)
|
||||
- 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`)
|
||||
- **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,18 +54,18 @@ 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/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.
|
||||
- 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.
|
||||
- **Eval suite:** evals/evals.json
|
||||
|
||||
### forward-deployed-engineering
|
||||
@@ -74,37 +74,37 @@ the migration path, and the field definitions. Regenerate with
|
||||
- **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/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`)
|
||||
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`)
|
||||
- **Included skills:**
|
||||
- ../../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`)
|
||||
- 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`)
|
||||
- **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,45 +116,45 @@ 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/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.
|
||||
- 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.
|
||||
- **Eval suite:** evals/evals.json
|
||||
|
||||
### neckbeard
|
||||
@@ -163,32 +163,32 @@ the migration path, and the field definitions. Regenerate with
|
||||
- **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/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`)
|
||||
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`)
|
||||
- **Included skills:**
|
||||
- ../../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`)
|
||||
- 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`)
|
||||
- **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/SKILL.md (`../../software-architecture-analysis/SKILL.md`)
|
||||
- Change contract and evidence ledger entries — via ../../verification-methodology/SKILL.md (`../../verification-methodology/SKILL.md`)
|
||||
- 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`)
|
||||
- **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,22 +196,22 @@ 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/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).
|
||||
- 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).
|
||||
- **Eval suite:** evals/evals.json
|
||||
|
||||
### product-lifecycle
|
||||
@@ -220,49 +220,49 @@ the migration path, and the field definitions. Regenerate with
|
||||
- **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/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`)
|
||||
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`)
|
||||
- **Included skills:**
|
||||
- ../../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`)
|
||||
- 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 (`../neckbeard/SKILL.md`)
|
||||
- **Prerequisites:**
|
||||
- Product idea, market signal, or stakeholder request
|
||||
- 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`)
|
||||
- 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`)
|
||||
- **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,19 +270,19 @@ 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/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.
|
||||
- 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.
|
||||
- **Eval suite:** evals/evals.json
|
||||
|
||||
### production-excellence
|
||||
@@ -291,31 +291,31 @@ the migration path, and the field definitions. Regenerate with
|
||||
- **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/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`)
|
||||
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`)
|
||||
- **Included skills:**
|
||||
- ../../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`)
|
||||
- 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`)
|
||||
- **Prerequisites:**
|
||||
- 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`)
|
||||
- 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`)
|
||||
- **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,19 +323,19 @@ 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/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.
|
||||
- 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.
|
||||
- **Eval suite:** evals/evals.json
|
||||
|
||||
### research-and-vault
|
||||
@@ -344,14 +344,14 @@ the migration path, and the field definitions. Regenerate with
|
||||
- **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/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`)
|
||||
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`)
|
||||
- **Included skills:**
|
||||
- ../../research-methodology/SKILL.md (`../../research-methodology/SKILL.md`)
|
||||
- research-methodology (`../research-methodology/SKILL.md`)
|
||||
- **Prerequisites:**
|
||||
- A research question or topic and access to web-research tooling — via ../../research-methodology/SKILL.md (`../../research-methodology/SKILL.md`)
|
||||
- A research question or topic and access to web-research tooling — via research-methodology (`../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.
|
||||
|
||||
@@ -68,7 +68,7 @@ stages unless the current charter's stop conditions require it.
|
||||
| Released within the authorized boundary | Adopt |
|
||||
| Adopted and measuring against the decision rule | Measure |
|
||||
| Post-launch evidence and a generalization question | Generalize |
|
||||
| A well-specified bounded change with no continuity need | Route to [neckbeard](../../bundles/neckbeard/SKILL.md) instead |
|
||||
| A well-specified bounded change with no continuity need | Route to [neckbeard](../neckbeard/SKILL.md) instead |
|
||||
|
||||
Before acting at any entry point, review the current charter, workflow map,
|
||||
ledger, and preceding stage-handoff record as entry evidence.
|
||||
@@ -87,8 +87,8 @@ ledger, and preceding stage-handoff record as entry evidence.
|
||||
access, security, privacy, irreversible, cost, and external-commitment
|
||||
decisions to their authorized owner.
|
||||
5. Before calling applied AI or any risky capability production-ready, load
|
||||
[agent-evals-and-observability](../../agent-evals-and-observability/SKILL.md)
|
||||
and [production-readiness](../../production-readiness/SKILL.md), and require
|
||||
[agent-evals-and-observability](../agent-evals-and-observability/SKILL.md)
|
||||
and [production-readiness](../production-readiness/SKILL.md), and require
|
||||
baseline, representative and adversarial evidence, constraints, and a
|
||||
release decision.
|
||||
6. Treat adoption and measured workflow impact as completion conditions, not
|
||||
@@ -127,17 +127,17 @@ or access is missing, evidence fails, adoption remains unexplained or below the
|
||||
decision rule, or the next action exceeds the charter. Escalate rather than
|
||||
guess on security, privacy, irreversible changes, material cost, external
|
||||
commitments, or business authority. Route a well-specified repository bug
|
||||
directly to [neckbeard](../../bundles/neckbeard/SKILL.md) and the relevant
|
||||
directly to [neckbeard](../neckbeard/SKILL.md) and the relevant
|
||||
specialist instead of invoking this lifecycle.
|
||||
|
||||
## When not to use
|
||||
|
||||
| Scenario | Reach for | Why |
|
||||
|---|---|---|
|
||||
| Well-bounded repository change | [neckbeard](../../bundles/neckbeard/SKILL.md) | Owns intake through verified PR and authorized release for a bounded change |
|
||||
| Product investment, portfolio, or lifecycle governance | [product-lifecycle](../../bundles/product-lifecycle/SKILL.md) | Owns investment and lifecycle governance, not delivery continuity |
|
||||
| Ongoing reliability ownership (SLOs, alerts, incidents) | [site-reliability-engineering](../../site-reliability-engineering/SKILL.md) | Standing operational ownership, not an embedded engagement |
|
||||
| Internal platform design or operation | [platform-engineering](../../platform-engineering/SKILL.md) | Platform ownership, not customer delivery |
|
||||
| Well-bounded repository change | [neckbeard](../neckbeard/SKILL.md) | Owns intake through verified PR and authorized release for a bounded change |
|
||||
| Product investment, portfolio, or lifecycle governance | [product-lifecycle](../product-lifecycle/SKILL.md) | Owns investment and lifecycle governance, not delivery continuity |
|
||||
| Ongoing reliability ownership (SLOs, alerts, incidents) | [site-reliability-engineering](../site-reliability-engineering/SKILL.md) | Standing operational ownership, not an embedded engagement |
|
||||
| Internal platform design or operation | [platform-engineering](../platform-engineering/SKILL.md) | Platform ownership, not customer delivery |
|
||||
| One discipline fully owns the task | That specialist directly | FDE stops routing when one specialist owns the request |
|
||||
| Advisory analysis ending before implementation and adoption | The relevant architecture or decision specialist | FDE completion requires adoption and outcome continuity |
|
||||
|
||||
|
||||
@@ -16,71 +16,71 @@ audience: >-
|
||||
stages:
|
||||
- name: Discover
|
||||
skills:
|
||||
- ../../product-discovery/SKILL.md
|
||||
- ../../data-engineering/SKILL.md
|
||||
- ../../remote-systems-administration/SKILL.md
|
||||
- ../product-discovery/SKILL.md
|
||||
- ../data-engineering/SKILL.md
|
||||
- ../remote-systems-administration/SKILL.md
|
||||
- name: Frame
|
||||
skills:
|
||||
- ../../product-design-and-ux/SKILL.md
|
||||
- ../../privacy-engineering/SKILL.md
|
||||
- ../../secure-software-engineering/SKILL.md
|
||||
- ../product-design-and-ux/SKILL.md
|
||||
- ../privacy-engineering/SKILL.md
|
||||
- ../secure-software-engineering/SKILL.md
|
||||
- name: Hypothesize
|
||||
skills:
|
||||
- ../../product-experimentation/SKILL.md
|
||||
- ../../agent-evals-and-observability/SKILL.md
|
||||
- ../product-experimentation/SKILL.md
|
||||
- ../agent-evals-and-observability/SKILL.md
|
||||
- name: Build
|
||||
skills:
|
||||
- ../../implementation-planning/SKILL.md
|
||||
- ../../backend-engineering/SKILL.md
|
||||
- ../../frontend-engineering/SKILL.md
|
||||
- ../../data-engineering/SKILL.md
|
||||
- ../implementation-planning/SKILL.md
|
||||
- ../backend-engineering/SKILL.md
|
||||
- ../frontend-engineering/SKILL.md
|
||||
- ../data-engineering/SKILL.md
|
||||
- name: Evaluate
|
||||
skills:
|
||||
- ../../agent-evals-and-observability/SKILL.md
|
||||
- ../../qa-methodology/SKILL.md
|
||||
- ../../verification-methodology/SKILL.md
|
||||
- ../agent-evals-and-observability/SKILL.md
|
||||
- ../qa-methodology/SKILL.md
|
||||
- ../verification-methodology/SKILL.md
|
||||
- name: Deploy
|
||||
skills:
|
||||
- ../../production-readiness/SKILL.md
|
||||
- ../../release-engineering/SKILL.md
|
||||
- ../../platform-engineering/SKILL.md
|
||||
- ../../remote-systems-administration/SKILL.md
|
||||
- ../production-readiness/SKILL.md
|
||||
- ../release-engineering/SKILL.md
|
||||
- ../platform-engineering/SKILL.md
|
||||
- ../remote-systems-administration/SKILL.md
|
||||
- name: Adopt
|
||||
skills:
|
||||
- ../../product-adoption/SKILL.md
|
||||
- ../../product-design-and-ux/SKILL.md
|
||||
- ../product-adoption/SKILL.md
|
||||
- ../product-design-and-ux/SKILL.md
|
||||
- name: Measure
|
||||
skills:
|
||||
- ../../product-analytics-and-measurement/SKILL.md
|
||||
- ../../agent-evals-and-observability/SKILL.md
|
||||
- ../../site-reliability-engineering/SKILL.md
|
||||
- ../product-analytics-and-measurement/SKILL.md
|
||||
- ../agent-evals-and-observability/SKILL.md
|
||||
- ../site-reliability-engineering/SKILL.md
|
||||
- name: Generalize
|
||||
skills:
|
||||
- ../../product-lifecycle-learning/SKILL.md
|
||||
- ../../product-methodology/SKILL.md
|
||||
- ../product-lifecycle-learning/SKILL.md
|
||||
- ../product-methodology/SKILL.md
|
||||
|
||||
included_skills:
|
||||
- ../../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
|
||||
- ../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
|
||||
|
||||
prerequisites:
|
||||
- artifact: Stakeholder request or observed workflow opportunity and a named accountable lead
|
||||
@@ -126,198 +126,198 @@ handoffs:
|
||||
durable transfer or follow-up path.
|
||||
|
||||
conflicts:
|
||||
- skill: ../../product-discovery/SKILL.md
|
||||
- skill: ../product-discovery/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
This bundle uses product-discovery for embedded delivery continuity and
|
||||
workflow context; product-lifecycle owns product investment and lifecycle governance.
|
||||
- skill: ../../product-discovery/SKILL.md
|
||||
- skill: ../product-discovery/SKILL.md
|
||||
with: research-and-vault
|
||||
guidance: >-
|
||||
Use product-discovery for stakeholder and workflow discovery; use research-and-vault
|
||||
for a reusable web-research-to-knowledge capture chain.
|
||||
- skill: ../../product-experimentation/SKILL.md
|
||||
- skill: ../product-experimentation/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
This bundle routes experiments to test an engagement intervention; product-lifecycle
|
||||
routes product investment experiments within its lifecycle governance.
|
||||
- skill: ../../implementation-planning/SKILL.md
|
||||
- skill: ../implementation-planning/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
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.
|
||||
- skill: ../../production-readiness/SKILL.md
|
||||
- skill: ../production-readiness/SKILL.md
|
||||
with: production-excellence
|
||||
guidance: >-
|
||||
This bundle carries engagement evidence into the specialist readiness review;
|
||||
production-excellence owns the cross-domain launch gate decision.
|
||||
- skill: ../../production-readiness/SKILL.md
|
||||
- skill: ../production-readiness/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
This bundle routes readiness for an embedded capability; product-lifecycle
|
||||
owns product lifecycle delivery handoff. Do not run both orchestration paths for one decision.
|
||||
- skill: ../../release-engineering/SKILL.md
|
||||
- skill: ../release-engineering/SKILL.md
|
||||
with: production-excellence
|
||||
guidance: >-
|
||||
This bundle routes deployment evidence from the engagement; production-excellence
|
||||
uses release evidence for a launch gate.
|
||||
- skill: ../../release-engineering/SKILL.md
|
||||
- skill: ../release-engineering/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
This bundle uses release engineering for embedded rollout continuity;
|
||||
product-lifecycle uses it for product delivery handoff.
|
||||
- skill: ../../platform-engineering/SKILL.md
|
||||
- skill: ../platform-engineering/SKILL.md
|
||||
with: production-excellence
|
||||
guidance: >-
|
||||
This bundle routes platform work needed to deploy the engagement capability;
|
||||
production-excellence assembles platform evidence for launch gating.
|
||||
- skill: ../../platform-engineering/SKILL.md
|
||||
- skill: ../platform-engineering/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
This bundle routes platform work needed by the engagement; product-lifecycle
|
||||
routes platform work in a product delivery handoff.
|
||||
- skill: ../../platform-engineering/SKILL.md
|
||||
- skill: ../platform-engineering/SKILL.md
|
||||
with: agent-production-operations
|
||||
guidance: >-
|
||||
This bundle routes product or engagement platform delivery; agent-production-operations
|
||||
owns runtime agent sandboxing and tool-execution isolation.
|
||||
- skill: ../../secure-software-engineering/SKILL.md
|
||||
- skill: ../secure-software-engineering/SKILL.md
|
||||
with: production-excellence
|
||||
guidance: >-
|
||||
This bundle routes trust-boundary work during the engagement; production-excellence
|
||||
consumes security evidence for its launch gate.
|
||||
- skill: ../../secure-software-engineering/SKILL.md
|
||||
- skill: ../secure-software-engineering/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
This bundle routes security work in the embedded lifecycle; product-lifecycle
|
||||
routes security work in product lifecycle phases.
|
||||
- skill: ../../secure-software-engineering/SKILL.md
|
||||
- skill: ../secure-software-engineering/SKILL.md
|
||||
with: agent-production-operations
|
||||
guidance: >-
|
||||
This bundle routes application and engagement security; agent-production-operations
|
||||
owns agent authority, disablement, and runtime security controls.
|
||||
- skill: ../../privacy-engineering/SKILL.md
|
||||
- skill: ../privacy-engineering/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
This bundle routes privacy work for engagement data flows; product-lifecycle
|
||||
routes privacy work across product lifecycle phases.
|
||||
- skill: ../../privacy-engineering/SKILL.md
|
||||
- skill: ../privacy-engineering/SKILL.md
|
||||
with: agent-production-operations
|
||||
guidance: >-
|
||||
This bundle routes engagement privacy decisions; agent-production-operations
|
||||
routes trace scrubbing and user-data-access grants.
|
||||
- skill: ../../qa-methodology/SKILL.md
|
||||
- skill: ../qa-methodology/SKILL.md
|
||||
with: production-excellence
|
||||
guidance: >-
|
||||
This bundle routes quality evidence for the built capability; production-excellence
|
||||
uses QA evidence at the launch gate.
|
||||
- skill: ../../qa-methodology/SKILL.md
|
||||
- skill: ../qa-methodology/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
This bundle routes evaluation and quality work for engagement delivery;
|
||||
product-lifecycle uses QA at product delivery handoff.
|
||||
- skill: ../../verification-methodology/SKILL.md
|
||||
- skill: ../verification-methodology/SKILL.md
|
||||
with: production-excellence
|
||||
guidance: >-
|
||||
This bundle uses verification to label engagement evidence; production-excellence
|
||||
uses it to verify launch-boundary evidence.
|
||||
- skill: ../../verification-methodology/SKILL.md
|
||||
- skill: ../verification-methodology/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
This bundle verifies continuity artifacts and field outcomes; product-lifecycle
|
||||
verifies evidence at product phase gates.
|
||||
- skill: ../../site-reliability-engineering/SKILL.md
|
||||
- skill: ../site-reliability-engineering/SKILL.md
|
||||
with: production-excellence
|
||||
guidance: >-
|
||||
This bundle routes reliability evidence for the engagement; production-excellence
|
||||
uses SRE evidence for its production gate.
|
||||
- skill: ../../site-reliability-engineering/SKILL.md
|
||||
- skill: ../site-reliability-engineering/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
This bundle routes reliability work needed for adoption and operation;
|
||||
product-lifecycle routes SRE work in product delivery handoff.
|
||||
- skill: ../../site-reliability-engineering/SKILL.md
|
||||
- skill: ../site-reliability-engineering/SKILL.md
|
||||
with: agent-production-operations
|
||||
guidance: >-
|
||||
This bundle routes service reliability; agent-production-operations routes
|
||||
runtime latency, cost budgets, and incident handoff for agents.
|
||||
- skill: ../../data-engineering/SKILL.md
|
||||
- skill: ../data-engineering/SKILL.md
|
||||
with: production-excellence
|
||||
guidance: >-
|
||||
This bundle routes data work required by the engagement; production-excellence
|
||||
consumes data evidence in its operational handoff and launch gate.
|
||||
- skill: ../../product-adoption/SKILL.md
|
||||
- skill: ../product-adoption/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
This bundle owns adoption continuity for an embedded engagement; product-lifecycle
|
||||
owns product adoption as one phase of product governance.
|
||||
- skill: ../../product-analytics-and-measurement/SKILL.md
|
||||
- skill: ../product-analytics-and-measurement/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
This bundle measures workflow impact for engagement completion; product-lifecycle
|
||||
measures product outcomes in lifecycle review.
|
||||
- skill: ../../product-lifecycle-learning/SKILL.md
|
||||
- skill: ../product-lifecycle-learning/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
This bundle uses field learning to decide generalization; product-lifecycle-learning
|
||||
owns the product lifecycle learning method and decision record.
|
||||
- skill: ../../agent-evals-and-observability/SKILL.md
|
||||
- skill: ../agent-evals-and-observability/SKILL.md
|
||||
with: agent-production-operations
|
||||
guidance: >-
|
||||
This bundle routes eval evidence for engagement release and learning;
|
||||
agent-production-operations consumes eval and trace evidence for runtime control.
|
||||
- skill: ../../production-readiness/SKILL.md
|
||||
- skill: ../production-readiness/SKILL.md
|
||||
with: agent-production-operations
|
||||
guidance: >-
|
||||
This bundle routes readiness for an embedded capability; agent-production-operations
|
||||
consumes readiness as an authority-gating input.
|
||||
- skill: ../../release-engineering/SKILL.md
|
||||
- skill: ../release-engineering/SKILL.md
|
||||
with: agent-production-operations
|
||||
guidance: >-
|
||||
This bundle uses release engineering for engagement rollout; agent-production-operations
|
||||
uses it for staged runtime rollout and fallback.
|
||||
- skill: ../../product-design-and-ux/SKILL.md
|
||||
- skill: ../product-design-and-ux/SKILL.md
|
||||
with: neckbeard
|
||||
guidance: >-
|
||||
This bundle routes UX for embedded workflow adoption; neckbeard uses UX
|
||||
only as needed for a bounded software change. Route by task boundary.
|
||||
- skill: ../../product-discovery/SKILL.md
|
||||
- skill: ../product-discovery/SKILL.md
|
||||
with: neckbeard
|
||||
guidance: >-
|
||||
This bundle owns embedded stakeholder and workflow discovery; neckbeard
|
||||
handles the bounded change after its requirements are known.
|
||||
- skill: ../../qa-methodology/SKILL.md
|
||||
- skill: ../qa-methodology/SKILL.md
|
||||
with: neckbeard
|
||||
guidance: >-
|
||||
This bundle routes QA for engagement evidence; neckbeard applies QA within
|
||||
its software delivery journey for a bounded repository change.
|
||||
- skill: ../../release-engineering/SKILL.md
|
||||
- skill: ../release-engineering/SKILL.md
|
||||
with: neckbeard
|
||||
guidance: >-
|
||||
This bundle routes release work across the engagement lifecycle; neckbeard
|
||||
owns release delivery for a bounded change.
|
||||
- skill: ../../secure-software-engineering/SKILL.md
|
||||
- skill: ../secure-software-engineering/SKILL.md
|
||||
with: neckbeard
|
||||
guidance: >-
|
||||
This bundle routes security decisions across embedded delivery; neckbeard
|
||||
applies security to its bounded software change.
|
||||
- skill: ../../site-reliability-engineering/SKILL.md
|
||||
- skill: ../site-reliability-engineering/SKILL.md
|
||||
with: neckbeard
|
||||
guidance: >-
|
||||
This bundle routes reliability for engagement outcomes; neckbeard routes
|
||||
reliability concerns within its software delivery journey.
|
||||
- skill: ../../verification-methodology/SKILL.md
|
||||
- skill: ../verification-methodology/SKILL.md
|
||||
with: neckbeard
|
||||
guidance: >-
|
||||
This bundle verifies stage continuity and outcome evidence; neckbeard
|
||||
verifies the bounded repository change.
|
||||
- skill: ../../product-design-and-ux/SKILL.md
|
||||
- skill: ../product-design-and-ux/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
This bundle routes UX for embedded workflow adoption; product-lifecycle
|
||||
routes UX for product requirements and lifecycle governance.
|
||||
- skill: ../../product-methodology/SKILL.md
|
||||
- skill: ../product-methodology/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
This bundle uses prioritization only to support engagement generalization;
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
Record the access route, identity and privilege needed, approved egress,
|
||||
systems and data in scope, change window, reviewer, rollback or recovery path,
|
||||
external-boundary verification, and evidence that the action succeeded. Load
|
||||
[remote-systems-administration](../../../remote-systems-administration/SKILL.md)
|
||||
[remote-systems-administration](../../remote-systems-administration/SKILL.md)
|
||||
for its operational method rather than inventing one here.
|
||||
|
||||
## Authority table
|
||||
@@ -31,5 +31,5 @@ authority substitute.
|
||||
An applied-AI demo is not production-ready without a representative baseline,
|
||||
adversarial or failure cases, risk constraints, evaluation results, an owner for
|
||||
residual risk, rollout and rollback evidence, and an explicit release decision.
|
||||
Route evaluation details to [agent-evals-and-observability](../../../agent-evals-and-observability/SKILL.md)
|
||||
and readiness details to [production-readiness](../../../production-readiness/SKILL.md).
|
||||
Route evaluation details to [agent-evals-and-observability](../../agent-evals-and-observability/SKILL.md)
|
||||
and readiness details to [production-readiness](../../production-readiness/SKILL.md).
|
||||
|
||||
@@ -15,10 +15,10 @@ standardized methodology.
|
||||
|
||||
| Existing owner | Already owns | FDE bundle boundary |
|
||||
|---|---|---|
|
||||
| [product-discovery](../../../product-discovery/SKILL.md) | Stakeholder mapping, workflow walkthroughs, hidden assumptions, validation, and interpretation handoff | Routes discovery and carries its evidence forward; does not duplicate discovery method |
|
||||
| [agent-evals-and-observability](../../../agent-evals-and-observability/SKILL.md) | Decision/risk contracts, datasets, baselines, graders, trajectory review, release gates, telemetry, and incident learning | Routes evaluation evidence and applies it to engagement continuity; does not restate eval method |
|
||||
| [production-readiness](../../../production-readiness/SKILL.md) | Risk-scaled evidence, ownership, SLOs, observability, support, security, data, rollback, capacity, cost, and verdicts | Routes readiness at the deployment boundary; does not invent a customer-site readiness method |
|
||||
| [remote-systems-administration](../../../remote-systems-administration/SKILL.md) | Access routes, privilege, bastions, sessions, recovery, rollback, canaries, bounded rollout, and external verification | Routes constrained-environment discovery before action; does not create a second remote-operations runbook |
|
||||
| [product-discovery](../../product-discovery/SKILL.md) | Stakeholder mapping, workflow walkthroughs, hidden assumptions, validation, and interpretation handoff | Routes discovery and carries its evidence forward; does not duplicate discovery method |
|
||||
| [agent-evals-and-observability](../../agent-evals-and-observability/SKILL.md) | Decision/risk contracts, datasets, baselines, graders, trajectory review, release gates, telemetry, and incident learning | Routes evaluation evidence and applies it to engagement continuity; does not restate eval method |
|
||||
| [production-readiness](../../production-readiness/SKILL.md) | Risk-scaled evidence, ownership, SLOs, observability, support, security, data, rollback, capacity, cost, and verdicts | Routes readiness at the deployment boundary; does not invent a customer-site readiness method |
|
||||
| [remote-systems-administration](../../remote-systems-administration/SKILL.md) | Access routes, privilege, bastions, sessions, recovery, rollback, canaries, bounded rollout, and external verification | Routes constrained-environment discovery before action; does not create a second remote-operations runbook |
|
||||
| [product-lifecycle](../../product-lifecycle/SKILL.md) | Product investment and lifecycle governance | FDE owns embedded delivery continuity, not portfolio choice or product lifecycle governance |
|
||||
| [production-excellence](../../production-excellence/SKILL.md) | Cross-domain production gate and handoff | FDE prepares engagement continuity and routes evidence; production-excellence owns its launch gate |
|
||||
| [neckbeard](../../neckbeard/SKILL.md) | Bounded software change journey | FDE stops routing and sends a well-specified repository change directly to neckbeard |
|
||||
|
||||
@@ -23,5 +23,5 @@ decision, and the commitment to implement or transfer it. Return reusable
|
||||
patterns and negative learning to the appropriate product, platform, research,
|
||||
or deployment owner without bypassing their authority. A classification is not
|
||||
an implementation approval: route to
|
||||
[implementation-planning](../../../implementation-planning/SKILL.md) only after
|
||||
[implementation-planning](../../implementation-planning/SKILL.md) only after
|
||||
the receiving owner approves a requirement or specification.
|
||||
|
||||
@@ -8,32 +8,32 @@ bounded task directly.
|
||||
|
||||
| Stage | Candidate | Load only when | Do not load when |
|
||||
|---|---|---|---|
|
||||
| Discover | [product-discovery](../../../product-discovery/SKILL.md) | The user, workflow, problem, outcome, or stakeholder interpretation is unvalidated | The problem and acceptance boundary are already explicit |
|
||||
| Discover | [data-engineering](../../../data-engineering/SKILL.md) | Discovery depends on data sources, contracts, quality, lineage, or pipeline feasibility | Data is incidental to the workflow question |
|
||||
| Discover | [remote-systems-administration](../../../remote-systems-administration/SKILL.md) | Relevant evidence or action sits behind remote access, privilege, egress, bastion, or recovery constraints | No remote or constrained system is involved |
|
||||
| Frame | [product-design-and-ux](../../../product-design-and-ux/SKILL.md) | The frame depends on user journeys, interaction behavior, service experience, or usability constraints | The work has no user-facing or workflow-experience question |
|
||||
| Frame | [privacy-engineering](../../../privacy-engineering/SKILL.md) | The frame includes personal data, consent, retention, disclosure, or privacy rights | No privacy-relevant data or processing is in scope |
|
||||
| Frame | [secure-software-engineering](../../../secure-software-engineering/SKILL.md) | The frame requires threat, trust-boundary, authentication, authorization, or secure-design decisions | Security is not a material part of the proposed intervention |
|
||||
| Hypothesize | [product-experimentation](../../../product-experimentation/SKILL.md) | The intervention needs a causal or comparative product/workflow experiment | The hypothesis is verified through engineering acceptance rather than an experiment |
|
||||
| Hypothesize | [agent-evals-and-observability](../../../agent-evals-and-observability/SKILL.md) | An agent, LLM, model, or nondeterministic workflow needs a decision/risk contract and evaluation plan | The capability is deterministic and ordinary test methods are sufficient |
|
||||
| Build | [implementation-planning](../../../implementation-planning/SKILL.md) | An authorized decision-maker has approved the requirement or specification and a dependency-aware delivery plan is needed | The requirement is not approved; stop and return upstream |
|
||||
| Build | [backend-engineering](../../../backend-engineering/SKILL.md) | The approved slice requires backend service or API implementation | No backend component is in scope |
|
||||
| Build | [frontend-engineering](../../../frontend-engineering/SKILL.md) | The approved slice requires a web frontend or client implementation | No frontend component is in scope |
|
||||
| Build | [data-engineering](../../../data-engineering/SKILL.md) | The approved slice requires data pipelines, contracts, storage, or transformation | Data work is not part of the implementation |
|
||||
| Evaluate | [agent-evals-and-observability](../../../agent-evals-and-observability/SKILL.md) | Agent, LLM, model, or nondeterministic behavior needs representative, adversarial, trajectory, or production-feedback evaluation | Ordinary deterministic verification is sufficient |
|
||||
| Evaluate | [qa-methodology](../../../qa-methodology/SKILL.md) | A risk-scaled test strategy or coverage model is needed | Acceptance criteria can be verified directly without a broader QA design |
|
||||
| Evaluate | [verification-methodology](../../../verification-methodology/SKILL.md) | Explicit acceptance criteria need direct pass/fail evidence | Criteria are not yet defined; return to framing or hypothesis work |
|
||||
| Deploy | [production-readiness](../../../production-readiness/SKILL.md) | A production or high-impact release needs a risk-scaled readiness verdict | The change is not crossing a production-like boundary |
|
||||
| Deploy | [release-engineering](../../../release-engineering/SKILL.md) | Release mechanics, versioning, promotion, rollback, or delivery automation are needed | No release artifact or promotion path exists |
|
||||
| Deploy | [platform-engineering](../../../platform-engineering/SKILL.md) | Deployment is blocked on an internal platform capability or platform-owned interface | The engagement itself is ongoing platform ownership; route directly instead |
|
||||
| Deploy | [remote-systems-administration](../../../remote-systems-administration/SKILL.md) | Deployment occurs through a constrained remote access or recovery path | The environment is local and unconstrained |
|
||||
| Adopt | [product-adoption](../../../product-adoption/SKILL.md) | Activation, onboarding, feature discovery, behavior change, or sustained use is below the decision rule | Intended workflow adoption is already evidenced |
|
||||
| Adopt | [product-design-and-ux](../../../product-design-and-ux/SKILL.md) | Adoption evidence points to usability or workflow-experience friction | The barrier is access, support, incentive, or ownership rather than UX |
|
||||
| Measure | [product-analytics-and-measurement](../../../product-analytics-and-measurement/SKILL.md) | Outcome metrics, instrumentation, events, funnels, cohorts, or governance are needed | Existing measurement evidence already answers the decision rule |
|
||||
| Measure | [agent-evals-and-observability](../../../agent-evals-and-observability/SKILL.md) | Model or agent quality needs production feedback and evaluation drift evidence | No agentic or nondeterministic component exists |
|
||||
| Measure | [site-reliability-engineering](../../../site-reliability-engineering/SKILL.md) | Reliability is an agreed outcome or a blocker to workflow impact | The request is ongoing SRE ownership; route directly instead |
|
||||
| Generalize | [product-lifecycle-learning](../../../product-lifecycle-learning/SKILL.md) | Expected and observed outcomes must be compared to choose continue, improve, pivot, pause, or retire | There is no post-launch evidence to compare |
|
||||
| Generalize | [product-methodology](../../../product-methodology/SKILL.md) | A bounded classification, prioritization, or decision log is needed for the local pattern | The question is portfolio investment or full product lifecycle governance |
|
||||
| Discover | [product-discovery](../../product-discovery/SKILL.md) | The user, workflow, problem, outcome, or stakeholder interpretation is unvalidated | The problem and acceptance boundary are already explicit |
|
||||
| Discover | [data-engineering](../../data-engineering/SKILL.md) | Discovery depends on data sources, contracts, quality, lineage, or pipeline feasibility | Data is incidental to the workflow question |
|
||||
| Discover | [remote-systems-administration](../../remote-systems-administration/SKILL.md) | Relevant evidence or action sits behind remote access, privilege, egress, bastion, or recovery constraints | No remote or constrained system is involved |
|
||||
| Frame | [product-design-and-ux](../../product-design-and-ux/SKILL.md) | The frame depends on user journeys, interaction behavior, service experience, or usability constraints | The work has no user-facing or workflow-experience question |
|
||||
| Frame | [privacy-engineering](../../privacy-engineering/SKILL.md) | The frame includes personal data, consent, retention, disclosure, or privacy rights | No privacy-relevant data or processing is in scope |
|
||||
| Frame | [secure-software-engineering](../../secure-software-engineering/SKILL.md) | The frame requires threat, trust-boundary, authentication, authorization, or secure-design decisions | Security is not a material part of the proposed intervention |
|
||||
| Hypothesize | [product-experimentation](../../product-experimentation/SKILL.md) | The intervention needs a causal or comparative product/workflow experiment | The hypothesis is verified through engineering acceptance rather than an experiment |
|
||||
| Hypothesize | [agent-evals-and-observability](../../agent-evals-and-observability/SKILL.md) | An agent, LLM, model, or nondeterministic workflow needs a decision/risk contract and evaluation plan | The capability is deterministic and ordinary test methods are sufficient |
|
||||
| Build | [implementation-planning](../../implementation-planning/SKILL.md) | An authorized decision-maker has approved the requirement or specification and a dependency-aware delivery plan is needed | The requirement is not approved; stop and return upstream |
|
||||
| Build | [backend-engineering](../../backend-engineering/SKILL.md) | The approved slice requires backend service or API implementation | No backend component is in scope |
|
||||
| Build | [frontend-engineering](../../frontend-engineering/SKILL.md) | The approved slice requires a web frontend or client implementation | No frontend component is in scope |
|
||||
| Build | [data-engineering](../../data-engineering/SKILL.md) | The approved slice requires data pipelines, contracts, storage, or transformation | Data work is not part of the implementation |
|
||||
| Evaluate | [agent-evals-and-observability](../../agent-evals-and-observability/SKILL.md) | Agent, LLM, model, or nondeterministic behavior needs representative, adversarial, trajectory, or production-feedback evaluation | Ordinary deterministic verification is sufficient |
|
||||
| Evaluate | [qa-methodology](../../qa-methodology/SKILL.md) | A risk-scaled test strategy or coverage model is needed | Acceptance criteria can be verified directly without a broader QA design |
|
||||
| Evaluate | [verification-methodology](../../verification-methodology/SKILL.md) | Explicit acceptance criteria need direct pass/fail evidence | Criteria are not yet defined; return to framing or hypothesis work |
|
||||
| Deploy | [production-readiness](../../production-readiness/SKILL.md) | A production or high-impact release needs a risk-scaled readiness verdict | The change is not crossing a production-like boundary |
|
||||
| Deploy | [release-engineering](../../release-engineering/SKILL.md) | Release mechanics, versioning, promotion, rollback, or delivery automation are needed | No release artifact or promotion path exists |
|
||||
| Deploy | [platform-engineering](../../platform-engineering/SKILL.md) | Deployment is blocked on an internal platform capability or platform-owned interface | The engagement itself is ongoing platform ownership; route directly instead |
|
||||
| Deploy | [remote-systems-administration](../../remote-systems-administration/SKILL.md) | Deployment occurs through a constrained remote access or recovery path | The environment is local and unconstrained |
|
||||
| Adopt | [product-adoption](../../product-adoption/SKILL.md) | Activation, onboarding, feature discovery, behavior change, or sustained use is below the decision rule | Intended workflow adoption is already evidenced |
|
||||
| Adopt | [product-design-and-ux](../../product-design-and-ux/SKILL.md) | Adoption evidence points to usability or workflow-experience friction | The barrier is access, support, incentive, or ownership rather than UX |
|
||||
| Measure | [product-analytics-and-measurement](../../product-analytics-and-measurement/SKILL.md) | Outcome metrics, instrumentation, events, funnels, cohorts, or governance are needed | Existing measurement evidence already answers the decision rule |
|
||||
| Measure | [agent-evals-and-observability](../../agent-evals-and-observability/SKILL.md) | Model or agent quality needs production feedback and evaluation drift evidence | No agentic or nondeterministic component exists |
|
||||
| Measure | [site-reliability-engineering](../../site-reliability-engineering/SKILL.md) | Reliability is an agreed outcome or a blocker to workflow impact | The request is ongoing SRE ownership; route directly instead |
|
||||
| Generalize | [product-lifecycle-learning](../../product-lifecycle-learning/SKILL.md) | Expected and observed outcomes must be compared to choose continue, improve, pivot, pause, or retire | There is no post-launch evidence to compare |
|
||||
| Generalize | [product-methodology](../../product-methodology/SKILL.md) | A bounded classification, prioritization, or decision log is needed for the local pattern | The question is portfolio investment or full product lifecycle governance |
|
||||
|
||||
## Approval boundaries
|
||||
|
||||
|
||||
+45
-45
@@ -1,4 +1,4 @@
|
||||
# Bundle manifest (bundle-manifest-v1) — see schemas/bundle-manifest-v1.schema.json
|
||||
# Bundle manifest (bundle-manifest-v1) — see ../schemas/bundle-manifest-v1.schema.json
|
||||
# and docs/bundle-manifest-design.md. Paths are relative to this bundle dir.
|
||||
|
||||
schema_version: 1
|
||||
@@ -20,55 +20,55 @@ audience: >-
|
||||
stages:
|
||||
- name: Intake and framing
|
||||
skills:
|
||||
- ../../product-discovery/SKILL.md
|
||||
- ../product-discovery/SKILL.md
|
||||
- name: Current-state discovery
|
||||
skills:
|
||||
- ../../software-architecture-analysis/SKILL.md
|
||||
- ../../systematic-debugging/SKILL.md
|
||||
- ../software-architecture-analysis/SKILL.md
|
||||
- ../systematic-debugging/SKILL.md
|
||||
- name: Design
|
||||
skills:
|
||||
- ../../api-design-and-evolution/SKILL.md
|
||||
- ../../product-design-and-ux/SKILL.md
|
||||
- ../api-design-and-evolution/SKILL.md
|
||||
- ../product-design-and-ux/SKILL.md
|
||||
- name: Specification
|
||||
skills:
|
||||
- ../../spec-driven-development/SKILL.md
|
||||
- ../spec-driven-development/SKILL.md
|
||||
- name: Test planning
|
||||
skills:
|
||||
- ../../qa-methodology/SKILL.md
|
||||
- ../qa-methodology/SKILL.md
|
||||
- name: Implementation
|
||||
skills:
|
||||
- ../../secure-software-engineering/SKILL.md
|
||||
- ../../web-accessibility/SKILL.md
|
||||
- ../secure-software-engineering/SKILL.md
|
||||
- ../web-accessibility/SKILL.md
|
||||
- name: Review and verification
|
||||
skills:
|
||||
- ../../verification-methodology/SKILL.md
|
||||
- ../../technical-documentation/SKILL.md
|
||||
- ../verification-methodology/SKILL.md
|
||||
- ../technical-documentation/SKILL.md
|
||||
- name: Readiness and release
|
||||
skills:
|
||||
- ../../release-engineering/SKILL.md
|
||||
- ../../site-reliability-engineering/SKILL.md
|
||||
- ../release-engineering/SKILL.md
|
||||
- ../site-reliability-engineering/SKILL.md
|
||||
|
||||
included_skills:
|
||||
- ../../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
|
||||
- ../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
|
||||
|
||||
prerequisites:
|
||||
- artifact: A non-trivial change request, issue, or task with a verifiable contract
|
||||
- artifact: Current-state evidence (repository, tests, config, recent history)
|
||||
skill: ../../software-architecture-analysis/SKILL.md
|
||||
skill: ../software-architecture-analysis/SKILL.md
|
||||
- artifact: Change contract and evidence ledger entries
|
||||
skill: ../../verification-methodology/SKILL.md
|
||||
skill: ../verification-methodology/SKILL.md
|
||||
|
||||
outputs:
|
||||
- change-contract
|
||||
@@ -104,96 +104,96 @@ handoffs:
|
||||
unverified boundaries) that carries learning into the next change.
|
||||
|
||||
conflicts:
|
||||
- skill: ../../product-discovery/SKILL.md
|
||||
- skill: ../product-discovery/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
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.
|
||||
- skill: ../../product-design-and-ux/SKILL.md
|
||||
- skill: ../product-design-and-ux/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
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.
|
||||
- skill: ../../spec-driven-development/SKILL.md
|
||||
- skill: ../spec-driven-development/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
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.
|
||||
- skill: ../../qa-methodology/SKILL.md
|
||||
- skill: ../qa-methodology/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
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.
|
||||
- skill: ../../qa-methodology/SKILL.md
|
||||
- skill: ../qa-methodology/SKILL.md
|
||||
with: production-excellence
|
||||
guidance: >-
|
||||
QA methodology is shared. neckbeard loads it for change-request test
|
||||
planning; production-excellence uses it for launch verification
|
||||
evidence.
|
||||
- skill: ../../secure-software-engineering/SKILL.md
|
||||
- skill: ../secure-software-engineering/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
Security engineering is shared. Route by context: change-level security
|
||||
review and threat modeling (neckbeard) versus lifecycle-phase security
|
||||
needs (product-lifecycle).
|
||||
- skill: ../../secure-software-engineering/SKILL.md
|
||||
- skill: ../secure-software-engineering/SKILL.md
|
||||
with: production-excellence
|
||||
guidance: >-
|
||||
Security engineering is shared. Route by context: change-level security
|
||||
review (neckbeard) versus launch-gate security evidence
|
||||
(production-excellence).
|
||||
- skill: ../../secure-software-engineering/SKILL.md
|
||||
- skill: ../secure-software-engineering/SKILL.md
|
||||
with: agent-production-operations
|
||||
guidance: >-
|
||||
Security engineering is shared. Route by context: change-level security
|
||||
review (neckbeard) versus agent authority contracts and disablement
|
||||
security (agent-production-operations).
|
||||
- skill: ../../verification-methodology/SKILL.md
|
||||
- skill: ../verification-methodology/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
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.
|
||||
- skill: ../../verification-methodology/SKILL.md
|
||||
- skill: ../verification-methodology/SKILL.md
|
||||
with: production-excellence
|
||||
guidance: >-
|
||||
Verification methodology is shared. neckbeard uses it for change-request
|
||||
verification verdicts; production-excellence uses it for boundary
|
||||
labeling of launch evidence.
|
||||
- skill: ../../release-engineering/SKILL.md
|
||||
- skill: ../release-engineering/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
Release engineering is shared. Route by context: change-request release
|
||||
planning (neckbeard) versus lifecycle delivery handoff
|
||||
(product-lifecycle).
|
||||
- skill: ../../release-engineering/SKILL.md
|
||||
- skill: ../release-engineering/SKILL.md
|
||||
with: production-excellence
|
||||
guidance: >-
|
||||
Release engineering is shared. Route by context: change-request release
|
||||
planning (neckbeard) versus launch-gate release evidence
|
||||
(production-excellence).
|
||||
- skill: ../../release-engineering/SKILL.md
|
||||
- skill: ../release-engineering/SKILL.md
|
||||
with: agent-production-operations
|
||||
guidance: >-
|
||||
Release engineering is shared. Route by context: change-request release
|
||||
planning (neckbeard) versus agent staged-rollout planning
|
||||
(agent-production-operations).
|
||||
- skill: ../../site-reliability-engineering/SKILL.md
|
||||
- skill: ../site-reliability-engineering/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
SRE is shared. neckbeard routes to it for reliability and operational
|
||||
recovery of a delivered change; product-lifecycle routes to it for
|
||||
delivery reliability.
|
||||
- skill: ../../site-reliability-engineering/SKILL.md
|
||||
- skill: ../site-reliability-engineering/SKILL.md
|
||||
with: production-excellence
|
||||
guidance: >-
|
||||
SRE is shared. Route by context: change-level reliability (neckbeard)
|
||||
versus gate-entry SLO/error-budget evidence (production-excellence).
|
||||
- skill: ../../site-reliability-engineering/SKILL.md
|
||||
- skill: ../site-reliability-engineering/SKILL.md
|
||||
with: agent-production-operations
|
||||
guidance: >-
|
||||
SRE is shared. Route by context: change-level reliability (neckbeard)
|
||||
|
||||
@@ -80,8 +80,8 @@ The runner ([../eval/run_eval.py](../eval/run_eval.py)) validates both
|
||||
single-task and trajectory fixtures in one pass:
|
||||
|
||||
```sh
|
||||
.venv/bin/python3 bundles/neckbeard/eval/run_eval.py \
|
||||
--suite bundles/neckbeard/eval/fixtures --validate-only
|
||||
.venv/bin/python3 neckbeard/eval/run_eval.py \
|
||||
--suite neckbeard/eval/fixtures --validate-only
|
||||
```
|
||||
|
||||
Expected output (current fixture set):
|
||||
@@ -99,9 +99,9 @@ OK: 14 fixture(s) valid.
|
||||
To scaffold a scoring report for manual evaluation:
|
||||
|
||||
```sh
|
||||
.venv/bin/python3 bundles/neckbeard/eval/run_eval.py \
|
||||
--suite bundles/neckbeard/eval/fixtures \
|
||||
--report bundles/neckbeard/eval/out/report.md
|
||||
.venv/bin/python3 neckbeard/eval/run_eval.py \
|
||||
--suite neckbeard/eval/fixtures \
|
||||
--report neckbeard/eval/out/report.md
|
||||
```
|
||||
|
||||
## Holdout discipline
|
||||
|
||||
+26
-26
@@ -37,15 +37,15 @@ behavior and completion criteria. Full phase contracts are in
|
||||
|
||||
| # | Phase | Primary specialist(s) | Entry evidence | Output artifacts | Escalation behavior | Completion criteria |
|
||||
|---|---|---|---|---|---|---|
|
||||
| 1 | **Discovery** | [product-discovery](../../product-discovery/SKILL.md) | Product idea, market signal, or stakeholder request | Problem statement, stakeholder map, discovery log, product type classification | Stop if: problem cannot be articulated in user terms; no stakeholder describes a real need; problem is already solved; out of organizational remit | Problem statement exists that a stakeholder recognizes; product type classified; proceed/pause/stop decision recorded |
|
||||
| 2 | **Strategy and portfolio choice** | [product-strategy](../../product-strategy/SKILL.md), [strategy-frameworks](../../strategy-frameworks/SKILL.md) | Problem statement and discovery log from Phase 1 | Strategic assessment, market sizing, portfolio recommendation, investment thesis | Stop if: opportunity conflicts with strategy; market evidence contradicts thesis; resource constraints are infeasible; strategic direction is ambiguous | Strategic assessment with fit/no-fit reasoning; portfolio decision recorded; resource estimate recorded |
|
||||
| 3 | **Roadmap** | [product-roadmapping-and-portfolio](../../product-roadmapping-and-portfolio/SKILL.md) | Strategic assessment and portfolio decision from Phase 2 | Outcome roadmap entry, Now/Next/Later placement, strategic bet record, dependency map, capacity allocation | Stop if: dependencies cannot be resolved; capacity unavailable; confidence below threshold; conflicts with higher-priority bet | Roadmap entry exists; bet record complete with kill criteria; dependencies mapped and acknowledged |
|
||||
| 4 | **UX and requirements** | [product-design-and-ux](../../product-design-and-ux/SKILL.md) | Roadmap entry and bet record from Phase 3; discovery log | Information architecture, task flows, interface contracts, acceptance criteria | Stop if: UX reveals fundamentally different problem; user research contradicts hypothesis; behavior cannot be specified testably; constraints cannot be satisfied | IA and task flows documented; interface contracts exist; acceptance criteria are testable and traceable |
|
||||
| 5 | **Experimentation** | [product-experimentation](../../product-experimentation/SKILL.md) | UX contracts, assumptions register, risk assessment | Experiment brief, experiment readout, updated assumptions register, proceed/pivot/stop decision | Stop if: experiment cannot be designed ethically; method infeasible; reveals safety/privacy/security risk; hypothesis disproved with no viable pivot | Experiment brief exists with hypothesis and decision rule; readout exists; proceed/pivot/stop decision recorded with evidence |
|
||||
| 6 | **Delivery handoff** | [implementation-planning](../../implementation-planning/SKILL.md), [production-readiness](../../production-readiness/SKILL.md), [release-engineering](../../release-engineering/SKILL.md) | Proceed decision, UX contracts, acceptance criteria, assumptions register | Implementation plan, formal spec, production-readiness verdict (Go/No-go/Defer/Exception), release plan | Stop if: infeasible dependency; readiness returns No-go or blocked Exception; security/privacy/compliance blocks launch; release plan cannot satisfy change-governance | Implementation plan accepted by delivery team; readiness verdict recorded with evidence; release plan documented and reviewed |
|
||||
| 7 | **Adoption** | [product-adoption](../../product-adoption/SKILL.md) | Launch decision (Go), release evidence, target segments, success metrics | Adoption plan, activation baseline, segmentation record, adoption metrics | Stop if: adoption materially below threshold after intervention; fundamental product-market mismatch; structural adoption problem beyond product changes | Adoption plan executed; activation and adoption baselines measured; proceed/intervene/pivot/stop decision recorded |
|
||||
| 8 | **Success** | [product-analytics-and-measurement](../../product-analytics-and-measurement/SKILL.md) | Adoption evidence, success criteria, experiment readouts | Outcome measurement, metric tree with actuals vs. targets, success/mixed/not-met assessment | Stop if: outcomes materially below expectations with unknown root cause; measurement infrastructure insufficient; evidence contradicts investment thesis | Outcome metrics measured against criteria; success assessment recorded; ledger complete for review |
|
||||
| 9 | **Lifecycle review** | [product-lifecycle-learning](../../product-lifecycle-learning/SKILL.md) | Outcome measurement, full evidence ledger, original assumptions register | Outcome review (expected vs. observed), assumption ledger update, continue/improve/harvest/pivot/pause/retire decision, retained learning record | Stop if: retirement has material implications beyond team authority; retained learning contradicts foundational assumption; systemic pattern requires executive attention | Outcome review recorded; lifecycle decision recorded with rationale; retained learning captured; ledger closed |
|
||||
| 1 | **Discovery** | [product-discovery](../product-discovery/SKILL.md) | Product idea, market signal, or stakeholder request | Problem statement, stakeholder map, discovery log, product type classification | Stop if: problem cannot be articulated in user terms; no stakeholder describes a real need; problem is already solved; out of organizational remit | Problem statement exists that a stakeholder recognizes; product type classified; proceed/pause/stop decision recorded |
|
||||
| 2 | **Strategy and portfolio choice** | [product-strategy](../product-strategy/SKILL.md), [strategy-frameworks](../strategy-frameworks/SKILL.md) | Problem statement and discovery log from Phase 1 | Strategic assessment, market sizing, portfolio recommendation, investment thesis | Stop if: opportunity conflicts with strategy; market evidence contradicts thesis; resource constraints are infeasible; strategic direction is ambiguous | Strategic assessment with fit/no-fit reasoning; portfolio decision recorded; resource estimate recorded |
|
||||
| 3 | **Roadmap** | [product-roadmapping-and-portfolio](../product-roadmapping-and-portfolio/SKILL.md) | Strategic assessment and portfolio decision from Phase 2 | Outcome roadmap entry, Now/Next/Later placement, strategic bet record, dependency map, capacity allocation | Stop if: dependencies cannot be resolved; capacity unavailable; confidence below threshold; conflicts with higher-priority bet | Roadmap entry exists; bet record complete with kill criteria; dependencies mapped and acknowledged |
|
||||
| 4 | **UX and requirements** | [product-design-and-ux](../product-design-and-ux/SKILL.md) | Roadmap entry and bet record from Phase 3; discovery log | Information architecture, task flows, interface contracts, acceptance criteria | Stop if: UX reveals fundamentally different problem; user research contradicts hypothesis; behavior cannot be specified testably; constraints cannot be satisfied | IA and task flows documented; interface contracts exist; acceptance criteria are testable and traceable |
|
||||
| 5 | **Experimentation** | [product-experimentation](../product-experimentation/SKILL.md) | UX contracts, assumptions register, risk assessment | Experiment brief, experiment readout, updated assumptions register, proceed/pivot/stop decision | Stop if: experiment cannot be designed ethically; method infeasible; reveals safety/privacy/security risk; hypothesis disproved with no viable pivot | Experiment brief exists with hypothesis and decision rule; readout exists; proceed/pivot/stop decision recorded with evidence |
|
||||
| 6 | **Delivery handoff** | [implementation-planning](../implementation-planning/SKILL.md), [production-readiness](../production-readiness/SKILL.md), [release-engineering](../release-engineering/SKILL.md) | Proceed decision, UX contracts, acceptance criteria, assumptions register | Implementation plan, formal spec, production-readiness verdict (Go/No-go/Defer/Exception), release plan | Stop if: infeasible dependency; readiness returns No-go or blocked Exception; security/privacy/compliance blocks launch; release plan cannot satisfy change-governance | Implementation plan accepted by delivery team; readiness verdict recorded with evidence; release plan documented and reviewed |
|
||||
| 7 | **Adoption** | [product-adoption](../product-adoption/SKILL.md) | Launch decision (Go), release evidence, target segments, success metrics | Adoption plan, activation baseline, segmentation record, adoption metrics | Stop if: adoption materially below threshold after intervention; fundamental product-market mismatch; structural adoption problem beyond product changes | Adoption plan executed; activation and adoption baselines measured; proceed/intervene/pivot/stop decision recorded |
|
||||
| 8 | **Success** | [product-analytics-and-measurement](../product-analytics-and-measurement/SKILL.md) | Adoption evidence, success criteria, experiment readouts | Outcome measurement, metric tree with actuals vs. targets, success/mixed/not-met assessment | Stop if: outcomes materially below expectations with unknown root cause; measurement infrastructure insufficient; evidence contradicts investment thesis | Outcome metrics measured against criteria; success assessment recorded; ledger complete for review |
|
||||
| 9 | **Lifecycle review** | [product-lifecycle-learning](../product-lifecycle-learning/SKILL.md) | Outcome measurement, full evidence ledger, original assumptions register | Outcome review (expected vs. observed), assumption ledger update, continue/improve/harvest/pivot/pause/retire decision, retained learning record | Stop if: retirement has material implications beyond team authority; retained learning contradicts foundational assumption; systemic pattern requires executive attention | Outcome review recorded; lifecycle decision recorded with rationale; retained learning captured; ledger closed |
|
||||
|
||||
### Supporting and cross-cutting skills
|
||||
|
||||
@@ -54,19 +54,19 @@ and are routed to when their specific capability is needed.
|
||||
|
||||
| Skill | When loaded |
|
||||
|---|---|
|
||||
| [product-methodology](../../product-methodology/SKILL.md) | When a phase produces alternatives that need ranking (RICE, MoSCoW, Kano, OST) |
|
||||
| [product-operations-and-governance](../../product-operations-and-governance/SKILL.md) | When setting up or changing governance; at phase boundaries needing formal decision authority |
|
||||
| [financial-modeling](../../financial-modeling/SKILL.md) | When unit economics, pricing, or business-model analysis is needed (Phases 2, 8) |
|
||||
| [go-to-market](../../go-to-market/SKILL.md) | When positioning, acquisition strategy, or growth modeling is needed (Phases 7, 8) |
|
||||
| [data-scientist](../../data-scientist/SKILL.md) | When statistical design, causal inference, or rigorous experiment analysis is needed (Phases 5, 8) |
|
||||
| [spec-driven-development](../../spec-driven-development/SKILL.md) | When formal specification with phase gates is needed (Phase 6) |
|
||||
| [privacy-engineering](../../privacy-engineering/SKILL.md) | When any phase handles PII, consent, retention, or data flows |
|
||||
| [secure-software-engineering](../../secure-software-engineering/SKILL.md) | When any phase touches trust boundaries, auth, or sensitive data |
|
||||
| [verification-methodology](../../verification-methodology/SKILL.md) | At every phase gate where evidence is required |
|
||||
| [qa-methodology](../../qa-methodology/SKILL.md) | When test strategy and quality gates are needed (Phase 6) |
|
||||
| [site-reliability-engineering](../../site-reliability-engineering/SKILL.md) | When reliability, SLOs, or operational readiness is needed (Phase 6) |
|
||||
| [platform-engineering](../../platform-engineering/SKILL.md) | When infrastructure, CI/CD, or platform capabilities are needed (Phase 6) |
|
||||
| [neckbeard](../../bundles/neckbeard/SKILL.md) | When the software delivery lifecycle (SDLC) change-request journey is needed for implementation (Phase 6) |
|
||||
| [product-methodology](../product-methodology/SKILL.md) | When a phase produces alternatives that need ranking (RICE, MoSCoW, Kano, OST) |
|
||||
| [product-operations-and-governance](../product-operations-and-governance/SKILL.md) | When setting up or changing governance; at phase boundaries needing formal decision authority |
|
||||
| [financial-modeling](../financial-modeling/SKILL.md) | When unit economics, pricing, or business-model analysis is needed (Phases 2, 8) |
|
||||
| [go-to-market](../go-to-market/SKILL.md) | When positioning, acquisition strategy, or growth modeling is needed (Phases 7, 8) |
|
||||
| [data-scientist](../data-scientist/SKILL.md) | When statistical design, causal inference, or rigorous experiment analysis is needed (Phases 5, 8) |
|
||||
| [spec-driven-development](../spec-driven-development/SKILL.md) | When formal specification with phase gates is needed (Phase 6) |
|
||||
| [privacy-engineering](../privacy-engineering/SKILL.md) | When any phase handles PII, consent, retention, or data flows |
|
||||
| [secure-software-engineering](../secure-software-engineering/SKILL.md) | When any phase touches trust boundaries, auth, or sensitive data |
|
||||
| [verification-methodology](../verification-methodology/SKILL.md) | At every phase gate where evidence is required |
|
||||
| [qa-methodology](../qa-methodology/SKILL.md) | When test strategy and quality gates are needed (Phase 6) |
|
||||
| [site-reliability-engineering](../site-reliability-engineering/SKILL.md) | When reliability, SLOs, or operational readiness is needed (Phase 6) |
|
||||
| [platform-engineering](../platform-engineering/SKILL.md) | When infrastructure, CI/CD, or platform capabilities are needed (Phase 6) |
|
||||
| [neckbeard](../neckbeard/SKILL.md) | When the software delivery lifecycle (SDLC) change-request journey is needed for implementation (Phase 6) |
|
||||
| `production-excellence` bundle (when available) | When the full production-excellence bundle is available as a handoff target (Phase 6) — composes production-readiness, migration-engineering, resilience-and-recovery, capacity-and-cost-engineering, and incident-learning |
|
||||
|
||||
## Loading protocol
|
||||
@@ -95,7 +95,7 @@ For capability lookup without traversing the full lifecycle, use the
|
||||
unnecessary for single-phase work.
|
||||
- **Software delivery lifecycle.** If the work is a code change, bug fix, or
|
||||
feature implementation — not product-level decision-making — route to
|
||||
[neckbeard](../../bundles/neckbeard/SKILL.md).
|
||||
[neckbeard](../neckbeard/SKILL.md).
|
||||
- **Duplicate methodology.** This bundle does NOT duplicate product-discovery,
|
||||
product-strategy, product-design-and-ux, product-experimentation,
|
||||
product-analytics-and-measurement, or release-engineering methods. Load those
|
||||
@@ -104,12 +104,12 @@ For capability lookup without traversing the full lifecycle, use the
|
||||
Customer-success routing (Phase 8) is CONDITIONAL on product type.
|
||||
Internal tools, public-service products, transactional products, and consumer
|
||||
products proceed without loading
|
||||
[conditional-customer-success](../../conditional-customer-success/SKILL.md).
|
||||
[conditional-customer-success](../conditional-customer-success/SKILL.md).
|
||||
- **Strategic frameworks.** For standalone strategic analysis (Five Forces,
|
||||
Blue Ocean, Ansoff) without a lifecycle context, load
|
||||
[strategy-frameworks](../../strategy-frameworks/SKILL.md) directly.
|
||||
[strategy-frameworks](../strategy-frameworks/SKILL.md) directly.
|
||||
- **Financial modeling.** For standalone financial analysis without a lifecycle
|
||||
context, load [financial-modeling](../../financial-modeling/SKILL.md) directly.
|
||||
context, load [financial-modeling](../financial-modeling/SKILL.md) directly.
|
||||
|
||||
## File map
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# Bundle manifest (bundle-manifest-v1) — see schemas/bundle-manifest-v1.schema.json
|
||||
# Bundle manifest (bundle-manifest-v1) — see ../schemas/bundle-manifest-v1.schema.json
|
||||
# and docs/bundle-manifest-design.md. Paths are relative to this bundle dir.
|
||||
|
||||
schema_version: 1
|
||||
@@ -20,76 +20,76 @@ audience: >-
|
||||
stages:
|
||||
- name: Discovery
|
||||
skills:
|
||||
- ../../product-discovery/SKILL.md
|
||||
- ../product-discovery/SKILL.md
|
||||
- name: Strategy and portfolio choice
|
||||
skills:
|
||||
- ../../product-strategy/SKILL.md
|
||||
- ../../strategy-frameworks/SKILL.md
|
||||
- ../product-strategy/SKILL.md
|
||||
- ../strategy-frameworks/SKILL.md
|
||||
- name: Roadmap
|
||||
skills:
|
||||
- ../../product-roadmapping-and-portfolio/SKILL.md
|
||||
- ../product-roadmapping-and-portfolio/SKILL.md
|
||||
- name: UX and requirements
|
||||
skills:
|
||||
- ../../product-design-and-ux/SKILL.md
|
||||
- ../product-design-and-ux/SKILL.md
|
||||
- name: Experimentation
|
||||
skills:
|
||||
- ../../product-experimentation/SKILL.md
|
||||
- ../product-experimentation/SKILL.md
|
||||
- name: Delivery handoff
|
||||
skills:
|
||||
- ../../implementation-planning/SKILL.md
|
||||
- ../../production-readiness/SKILL.md
|
||||
- ../../release-engineering/SKILL.md
|
||||
- ../implementation-planning/SKILL.md
|
||||
- ../production-readiness/SKILL.md
|
||||
- ../release-engineering/SKILL.md
|
||||
- name: Adoption
|
||||
skills:
|
||||
- ../../product-adoption/SKILL.md
|
||||
- ../product-adoption/SKILL.md
|
||||
- name: Success
|
||||
skills:
|
||||
- ../../product-analytics-and-measurement/SKILL.md
|
||||
- ../../conditional-customer-success/SKILL.md
|
||||
- ../product-analytics-and-measurement/SKILL.md
|
||||
- ../conditional-customer-success/SKILL.md
|
||||
- name: Lifecycle review
|
||||
skills:
|
||||
- ../../product-lifecycle-learning/SKILL.md
|
||||
- ../product-lifecycle-learning/SKILL.md
|
||||
|
||||
included_skills:
|
||||
- ../../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-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
|
||||
- ../neckbeard/SKILL.md
|
||||
|
||||
prerequisites:
|
||||
- artifact: Product idea, market signal, or stakeholder request
|
||||
- artifact: Problem statement and discovery log
|
||||
skill: ../../product-discovery/SKILL.md
|
||||
skill: ../product-discovery/SKILL.md
|
||||
- artifact: Strategic assessment and portfolio decision
|
||||
skill: ../../product-strategy/SKILL.md
|
||||
skill: ../product-strategy/SKILL.md
|
||||
- artifact: Roadmap entry and bet record
|
||||
skill: ../../product-roadmapping-and-portfolio/SKILL.md
|
||||
skill: ../product-roadmapping-and-portfolio/SKILL.md
|
||||
- artifact: UX contracts and acceptance criteria
|
||||
skill: ../../product-design-and-ux/SKILL.md
|
||||
skill: ../product-design-and-ux/SKILL.md
|
||||
- artifact: Experiment readout and assumptions register
|
||||
skill: ../../product-experimentation/SKILL.md
|
||||
skill: ../product-experimentation/SKILL.md
|
||||
|
||||
outputs:
|
||||
- lifecycle-evidence-ledger
|
||||
@@ -129,81 +129,81 @@ handoffs:
|
||||
and retained learning in the learning loop.
|
||||
|
||||
conflicts:
|
||||
- skill: ../../production-readiness/SKILL.md
|
||||
- skill: ../production-readiness/SKILL.md
|
||||
with: production-excellence
|
||||
guidance: >-
|
||||
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.
|
||||
- skill: ../../production-readiness/SKILL.md
|
||||
- skill: ../production-readiness/SKILL.md
|
||||
with: agent-production-operations
|
||||
guidance: >-
|
||||
agent-production-operations consumes readiness outcomes as authority-
|
||||
gating inputs. Route phase 6 readiness reviews here; runtime authority
|
||||
decisions go to agent-production-operations.
|
||||
- skill: ../../release-engineering/SKILL.md
|
||||
- skill: ../release-engineering/SKILL.md
|
||||
with: production-excellence
|
||||
guidance: >-
|
||||
Release engineering is shared. Route by context: lifecycle delivery
|
||||
handoff (this bundle) versus gate-entry release evidence
|
||||
(production-excellence).
|
||||
- skill: ../../release-engineering/SKILL.md
|
||||
- skill: ../release-engineering/SKILL.md
|
||||
with: agent-production-operations
|
||||
guidance: >-
|
||||
Release engineering is shared. Route by context: lifecycle delivery
|
||||
handoff (this bundle) versus agent staged-rollout planning
|
||||
(agent-production-operations).
|
||||
- skill: ../../site-reliability-engineering/SKILL.md
|
||||
- skill: ../site-reliability-engineering/SKILL.md
|
||||
with: production-excellence
|
||||
guidance: >-
|
||||
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.
|
||||
- skill: ../../site-reliability-engineering/SKILL.md
|
||||
- skill: ../site-reliability-engineering/SKILL.md
|
||||
with: agent-production-operations
|
||||
guidance: >-
|
||||
SRE is shared. This bundle uses it for delivery reliability;
|
||||
agent-production-operations uses it for runtime latency/cost budgets
|
||||
and incident handoff.
|
||||
- skill: ../../secure-software-engineering/SKILL.md
|
||||
- skill: ../secure-software-engineering/SKILL.md
|
||||
with: production-excellence
|
||||
guidance: >-
|
||||
Security engineering is shared. Route by phase/domain: trust-boundary
|
||||
work in lifecycle phases (this bundle) versus security evidence for
|
||||
launch gates (production-excellence).
|
||||
- skill: ../../secure-software-engineering/SKILL.md
|
||||
- skill: ../secure-software-engineering/SKILL.md
|
||||
with: agent-production-operations
|
||||
guidance: >-
|
||||
Security engineering is shared. Route by context: lifecycle-phase
|
||||
security needs (this bundle) versus agent authority contracts and
|
||||
disablement security (agent-production-operations).
|
||||
- skill: ../../platform-engineering/SKILL.md
|
||||
- skill: ../platform-engineering/SKILL.md
|
||||
with: production-excellence
|
||||
guidance: >-
|
||||
Platform engineering is shared. Route by context: lifecycle delivery
|
||||
handoff (this bundle) versus gate-entry platform evidence
|
||||
(production-excellence).
|
||||
- skill: ../../platform-engineering/SKILL.md
|
||||
- skill: ../platform-engineering/SKILL.md
|
||||
with: agent-production-operations
|
||||
guidance: >-
|
||||
Platform engineering is shared. Route by context: lifecycle delivery
|
||||
handoff (this bundle) versus agent sandboxing and tool-execution
|
||||
isolation (agent-production-operations).
|
||||
- skill: ../../privacy-engineering/SKILL.md
|
||||
- skill: ../privacy-engineering/SKILL.md
|
||||
with: agent-production-operations
|
||||
guidance: >-
|
||||
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.
|
||||
- skill: ../../qa-methodology/SKILL.md
|
||||
- skill: ../qa-methodology/SKILL.md
|
||||
with: production-excellence
|
||||
guidance: >-
|
||||
QA methodology is shared. Route by context: lifecycle phase 6 quality
|
||||
gates (this bundle) versus launch verification evidence
|
||||
(production-excellence).
|
||||
- skill: ../../verification-methodology/SKILL.md
|
||||
- skill: ../verification-methodology/SKILL.md
|
||||
with: production-excellence
|
||||
guidance: >-
|
||||
Verification methodology is shared. This bundle uses it at every phase
|
||||
|
||||
@@ -42,7 +42,7 @@ cross-phase routing; this map provides point lookup.
|
||||
| Platform engineering, infrastructure, CI/CD | [platform-engineering](../../platform-engineering/SKILL.md) |
|
||||
| QA strategy, test planning, quality gates | [qa-methodology](../../qa-methodology/SKILL.md) |
|
||||
| Verification methodology, evidence trails | [verification-methodology](../../verification-methodology/SKILL.md) |
|
||||
| Software delivery lifecycle (SDLC) | [neckbeard](../../bundles/neckbeard/SKILL.md) |
|
||||
| Software delivery lifecycle (SDLC) | [neckbeard](../../neckbeard/SKILL.md) |
|
||||
|
||||
## Cross-cutting concerns
|
||||
|
||||
|
||||
@@ -18,7 +18,7 @@ must manually chain skills. This bundle provides that routing.
|
||||
|
||||
## Comparison with existing bundles
|
||||
|
||||
### bundles/neckbeard
|
||||
### neckbeard
|
||||
|
||||
neckbeard is an SDLC delivery operating model — it routes a **code change**
|
||||
through framing, discovery, design, implementation, review, verification,
|
||||
@@ -33,7 +33,7 @@ release-engineering, and the neckbeard change-request journey for the
|
||||
implementation and delivery of product decisions. The two bundles intersect at
|
||||
the delivery-handoff boundary but own different domains.
|
||||
|
||||
### bundles/workflow-architect
|
||||
### workflow-architect
|
||||
|
||||
workflow-architect is a meta-skill that discovers a **person's** workflow
|
||||
through conversation or observation and generates a tailored skills bundle. It
|
||||
@@ -43,14 +43,14 @@ provides a fixed, opinionated lifecycle routing table for product work. A user
|
||||
might run workflow-architect to discover their own product workflow and then
|
||||
use the product-lifecycle bundle as a reference for building it.
|
||||
|
||||
### bundles/tailscale
|
||||
### tailscale
|
||||
|
||||
tailscale is a domain-specific infrastructure bundle for self-hosted
|
||||
Tailscale/Headscale VPN. It has no product management content and no lifecycle
|
||||
routing. No overlap with product-lifecycle. Mentioned here only for comparison
|
||||
completeness.
|
||||
|
||||
### bundles/research-and-vault
|
||||
### research-and-vault
|
||||
|
||||
research-and-vault is a thin orchestrator for a repeatable research-to-notes
|
||||
pipeline: gather sources, extract atomic claims, create durable notes. It
|
||||
@@ -99,7 +99,7 @@ Additional skills that may be routed to contextually: `site-reliability-engineer
|
||||
- **Release engineering, CI/CD, deployment.** Routes to `release-engineering` and `production-readiness`.
|
||||
- **Analytics instrumentation and pipelines.** Routes to `product-analytics-and-measurement` and `data-engineering`.
|
||||
- **Customer success account management.** Routes to `conditional-customer-success` (conditional on product type).
|
||||
- **Software delivery lifecycle.** Routes to `bundles/neckbeard` and `implementation-planning`.
|
||||
- **Software delivery lifecycle.** Routes to `neckbeard` and `implementation-planning`.
|
||||
- **Financial modeling and pricing.** Routes to `financial-modeling`.
|
||||
- **GTM strategy and execution.** Routes to `go-to-market`.
|
||||
- **Privacy, security, legal compliance.** Routes to `privacy-engineering`, `secure-software-engineering`, `legal-strategy`.
|
||||
|
||||
@@ -255,7 +255,7 @@ to engineering and production skills rather than doing the work itself.
|
||||
- [release-engineering](../../release-engineering/SKILL.md) — release process, progressive delivery, versioning
|
||||
|
||||
**Supporting:**
|
||||
- [neckbeard](../../bundles/neckbeard/SKILL.md) — change-request journey for the implementation itself
|
||||
- [neckbeard](../../neckbeard/SKILL.md) — change-request journey for the implementation itself
|
||||
- [site-reliability-engineering](../../site-reliability-engineering/SKILL.md) — reliability and SLOs
|
||||
- [platform-engineering](../../platform-engineering/SKILL.md) — infrastructure and CI/CD
|
||||
- [secure-software-engineering](../../secure-software-engineering/SKILL.md) — security requirements and review
|
||||
|
||||
@@ -23,6 +23,6 @@ point; all routed skills are top-level catalog skills, not nested sub-skills.
|
||||
- Compatible harnesses are guaranteed to see this bundle's `SKILL.md`. Nested
|
||||
sub-skill auto-loading is not applicable (no nested skills exist).
|
||||
- The bundle's routing table in `SKILL.md` uses relative links from the bundle
|
||||
root (`bundles/production-excellence/`) to top-level skill directories
|
||||
(`../../<skill>/SKILL.md`). Harnesses must resolve these relative to the
|
||||
root (`production-excellence/`) to top-level skill directories
|
||||
(`../<skill>/SKILL.md`). Harnesses must resolve these relative to the
|
||||
repository root.
|
||||
|
||||
@@ -46,19 +46,19 @@ Load when:
|
||||
Do **not** load this bundle for:
|
||||
|
||||
- **Incident command or SLO operations** — those are owned by
|
||||
[site-reliability-engineering](../../site-reliability-engineering/SKILL.md).
|
||||
[site-reliability-engineering](../site-reliability-engineering/SKILL.md).
|
||||
- **Release-pipeline mechanics, versioning, or deployment strategies** — those are
|
||||
owned by [release-engineering](../../release-engineering/SKILL.md).
|
||||
owned by [release-engineering](../release-engineering/SKILL.md).
|
||||
- **Platform architecture or internal-developer-platform design** — those are
|
||||
owned by [platform-engineering](../../platform-engineering/SKILL.md).
|
||||
owned by [platform-engineering](../platform-engineering/SKILL.md).
|
||||
- **Threat modeling, security review procedure, or vulnerability assessment** —
|
||||
those are owned by
|
||||
[secure-software-engineering](../../secure-software-engineering/SKILL.md).
|
||||
[secure-software-engineering](../secure-software-engineering/SKILL.md).
|
||||
- **Data-pipeline design, ETL, or storage architecture** — those are owned by
|
||||
[data-engineering](../../data-engineering/SKILL.md).
|
||||
[data-engineering](../data-engineering/SKILL.md).
|
||||
- **Test-strategy design, regression-suite management, or test-automation
|
||||
framework design** — those are owned by
|
||||
[qa-methodology](../../qa-methodology/SKILL.md).
|
||||
[qa-methodology](../qa-methodology/SKILL.md).
|
||||
- **A generic checklist detached from service ownership, risk, evidence, and
|
||||
verification** — every gate in this bundle requires a named service owner,
|
||||
assessed risk, verified evidence, and a declaration of the verification
|
||||
@@ -78,23 +78,23 @@ assembly and the gate decision.
|
||||
|
||||
| Domain | Specialist skill | What the specialist owns | What the bundle adds |
|
||||
|---|---|---|---|
|
||||
| **Production readiness** | [production-readiness](../../production-readiness/SKILL.md) | Risk-scaled evidence packet (11 categories), go/no-go/defer/exception launch decisions, accountable owners | Cross-domain assembly with migration, recovery, capacity/cost, and incident evidence; gate integration |
|
||||
| **Migration** | [migration-engineering](../../migration-engineering/SKILL.md) | Expand/contract, compatibility windows, dual-running, backfills, reconciliation, cutover, recovery paths | Migration evidence as input to the gate model; handoff of migration verification to the operational record |
|
||||
| **Resilience and recovery** | [resilience-and-recovery](../../resilience-and-recovery/SKILL.md) | Failure modes, degradation choices, RTO/RPO, restore testing, DR, game days, failover, data integrity | Recovery evidence as a gate condition; exercise results feed the handoff record |
|
||||
| **Capacity and cost** | [capacity-and-cost-engineering](../../capacity-and-cost-engineering/SKILL.md) | Demand/capacity/scaling/utilization models, unit-cost connection to SLO decisions, cost-constrained scenarios | Capacity/cost evidence as a gate condition; SLO/cost tradeoff decisions feed the gate model |
|
||||
| **Incident learning** | [incident-learning](../../incident-learning/SKILL.md) | Observed facts, causal hypotheses, contributing conditions, follow-up work mapping, verified closure | Pre-existing incident evidence as a gate condition; post-launch incidents routed back to incident-learning |
|
||||
| **Production readiness** | [production-readiness](../production-readiness/SKILL.md) | Risk-scaled evidence packet (11 categories), go/no-go/defer/exception launch decisions, accountable owners | Cross-domain assembly with migration, recovery, capacity/cost, and incident evidence; gate integration |
|
||||
| **Migration** | [migration-engineering](../migration-engineering/SKILL.md) | Expand/contract, compatibility windows, dual-running, backfills, reconciliation, cutover, recovery paths | Migration evidence as input to the gate model; handoff of migration verification to the operational record |
|
||||
| **Resilience and recovery** | [resilience-and-recovery](../resilience-and-recovery/SKILL.md) | Failure modes, degradation choices, RTO/RPO, restore testing, DR, game days, failover, data integrity | Recovery evidence as a gate condition; exercise results feed the handoff record |
|
||||
| **Capacity and cost** | [capacity-and-cost-engineering](../capacity-and-cost-engineering/SKILL.md) | Demand/capacity/scaling/utilization models, unit-cost connection to SLO decisions, cost-constrained scenarios | Capacity/cost evidence as a gate condition; SLO/cost tradeoff decisions feed the gate model |
|
||||
| **Incident learning** | [incident-learning](../incident-learning/SKILL.md) | Observed facts, causal hypotheses, contributing conditions, follow-up work mapping, verified closure | Pre-existing incident evidence as a gate condition; post-launch incidents routed back to incident-learning |
|
||||
|
||||
### Supporting specialist routes
|
||||
|
||||
| Domain | Specialist skill | When routed |
|
||||
|---|---|---|
|
||||
| **Reliability / SLOs** | [site-reliability-engineering](../../site-reliability-engineering/SKILL.md) | SLO/error-budget status required for gate entry; incident response for post-launch issues |
|
||||
| **Release mechanics** | [release-engineering](../../release-engineering/SKILL.md) | Release plan, rollout/rollback strategy required for gate entry |
|
||||
| **Platform** | [platform-engineering](../../platform-engineering/SKILL.md) | Service-catalog entry, paved-road status for new services |
|
||||
| **Security** | [secure-software-engineering](../../secure-software-engineering/SKILL.md) | Security review evidence for trust-boundary changes |
|
||||
| **Data** | [data-engineering](../../data-engineering/SKILL.md) | Data-quality and pipeline evidence for data-path changes |
|
||||
| **QA** | [qa-methodology](../../qa-methodology/SKILL.md) | Verification evidence for all launches |
|
||||
| **Verification** | [verification-methodology](../../verification-methodology/SKILL.md) | Boundary labeling and gap declaration for evidence assessment |
|
||||
| **Reliability / SLOs** | [site-reliability-engineering](../site-reliability-engineering/SKILL.md) | SLO/error-budget status required for gate entry; incident response for post-launch issues |
|
||||
| **Release mechanics** | [release-engineering](../release-engineering/SKILL.md) | Release plan, rollout/rollback strategy required for gate entry |
|
||||
| **Platform** | [platform-engineering](../platform-engineering/SKILL.md) | Service-catalog entry, paved-road status for new services |
|
||||
| **Security** | [secure-software-engineering](../secure-software-engineering/SKILL.md) | Security review evidence for trust-boundary changes |
|
||||
| **Data** | [data-engineering](../data-engineering/SKILL.md) | Data-quality and pipeline evidence for data-path changes |
|
||||
| **QA** | [qa-methodology](../qa-methodology/SKILL.md) | Verification evidence for all launches |
|
||||
| **Verification** | [verification-methodology](../verification-methodology/SKILL.md) | Boundary labeling and gap declaration for evidence assessment |
|
||||
|
||||
## Cross-domain entry evidence
|
||||
|
||||
@@ -142,13 +142,13 @@ Launch outcomes and post-launch observations feed two learning routes:
|
||||
|
||||
1. **Incident learning** — post-launch incidents (SLO degradations, unexpected
|
||||
failures, capacity breaches) are routed to
|
||||
[incident-learning](../../incident-learning/SKILL.md). The handoff record
|
||||
[incident-learning](../incident-learning/SKILL.md). The handoff record
|
||||
provides the launch context; the incident-learning skill's verified-closure
|
||||
requirement ensures follow-up items are tracked to completion.
|
||||
|
||||
2. **Lifecycle learning** — expected outcomes recorded in the handoff (SLO
|
||||
targets, capacity assumptions, cost projections) are routed to
|
||||
[product-lifecycle-learning](../../product-lifecycle-learning/SKILL.md)
|
||||
[product-lifecycle-learning](../product-lifecycle-learning/SKILL.md)
|
||||
for expected-vs-observed comparison at the handoff's review cadence. The
|
||||
lifecycle-learning skill's continue/improve/harvest/pivot/pause/retire
|
||||
decisions are informed by the gap between predicted and observed production
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# Bundle manifest (bundle-manifest-v1) — see schemas/bundle-manifest-v1.schema.json
|
||||
# Bundle manifest (bundle-manifest-v1) — see ../schemas/bundle-manifest-v1.schema.json
|
||||
# and docs/bundle-manifest-design.md. Paths are relative to this bundle dir.
|
||||
|
||||
schema_version: 1
|
||||
@@ -19,56 +19,56 @@ audience: >-
|
||||
stages:
|
||||
- name: Cross-domain evidence assembly
|
||||
skills:
|
||||
- ../../production-readiness/SKILL.md
|
||||
- ../../migration-engineering/SKILL.md
|
||||
- ../../resilience-and-recovery/SKILL.md
|
||||
- ../../capacity-and-cost-engineering/SKILL.md
|
||||
- ../../incident-learning/SKILL.md
|
||||
- ../production-readiness/SKILL.md
|
||||
- ../migration-engineering/SKILL.md
|
||||
- ../resilience-and-recovery/SKILL.md
|
||||
- ../capacity-and-cost-engineering/SKILL.md
|
||||
- ../incident-learning/SKILL.md
|
||||
- name: Gate evaluation
|
||||
skills:
|
||||
- ../../production-readiness/SKILL.md
|
||||
- ../../site-reliability-engineering/SKILL.md
|
||||
- ../../verification-methodology/SKILL.md
|
||||
- ../../qa-methodology/SKILL.md
|
||||
- ../production-readiness/SKILL.md
|
||||
- ../site-reliability-engineering/SKILL.md
|
||||
- ../verification-methodology/SKILL.md
|
||||
- ../qa-methodology/SKILL.md
|
||||
- name: Operational handoff
|
||||
skills:
|
||||
- ../../release-engineering/SKILL.md
|
||||
- ../../platform-engineering/SKILL.md
|
||||
- ../../secure-software-engineering/SKILL.md
|
||||
- ../../data-engineering/SKILL.md
|
||||
- ../release-engineering/SKILL.md
|
||||
- ../platform-engineering/SKILL.md
|
||||
- ../secure-software-engineering/SKILL.md
|
||||
- ../data-engineering/SKILL.md
|
||||
- name: Post-launch learning
|
||||
skills:
|
||||
- ../../incident-learning/SKILL.md
|
||||
- ../incident-learning/SKILL.md
|
||||
|
||||
included_skills:
|
||||
- ../../production-readiness/SKILL.md
|
||||
- ../../migration-engineering/SKILL.md
|
||||
- ../../resilience-and-recovery/SKILL.md
|
||||
- ../../capacity-and-cost-engineering/SKILL.md
|
||||
- ../../incident-learning/SKILL.md
|
||||
- ../../site-reliability-engineering/SKILL.md
|
||||
- ../../release-engineering/SKILL.md
|
||||
- ../../platform-engineering/SKILL.md
|
||||
- ../../secure-software-engineering/SKILL.md
|
||||
- ../../data-engineering/SKILL.md
|
||||
- ../../qa-methodology/SKILL.md
|
||||
- ../../verification-methodology/SKILL.md
|
||||
- ../production-readiness/SKILL.md
|
||||
- ../migration-engineering/SKILL.md
|
||||
- ../resilience-and-recovery/SKILL.md
|
||||
- ../capacity-and-cost-engineering/SKILL.md
|
||||
- ../incident-learning/SKILL.md
|
||||
- ../site-reliability-engineering/SKILL.md
|
||||
- ../release-engineering/SKILL.md
|
||||
- ../platform-engineering/SKILL.md
|
||||
- ../secure-software-engineering/SKILL.md
|
||||
- ../data-engineering/SKILL.md
|
||||
- ../qa-methodology/SKILL.md
|
||||
- ../verification-methodology/SKILL.md
|
||||
|
||||
prerequisites:
|
||||
- artifact: Readiness review evidence packet (risk-scaled, 11 categories)
|
||||
skill: ../../production-readiness/SKILL.md
|
||||
skill: ../production-readiness/SKILL.md
|
||||
- artifact: Migration plan, compatibility windows, and reconciliation evidence
|
||||
skill: ../../migration-engineering/SKILL.md
|
||||
skill: ../migration-engineering/SKILL.md
|
||||
- artifact: Resilience and recovery evidence (RTO/RPO, restore tests, game days)
|
||||
skill: ../../resilience-and-recovery/SKILL.md
|
||||
skill: ../resilience-and-recovery/SKILL.md
|
||||
- artifact: Capacity and cost model evidence (demand, scaling, unit cost)
|
||||
skill: ../../capacity-and-cost-engineering/SKILL.md
|
||||
skill: ../capacity-and-cost-engineering/SKILL.md
|
||||
- artifact: Incident history, causal hypotheses, and verified-closure records
|
||||
skill: ../../incident-learning/SKILL.md
|
||||
skill: ../incident-learning/SKILL.md
|
||||
- artifact: SLO and error-budget status
|
||||
skill: ../../site-reliability-engineering/SKILL.md
|
||||
skill: ../site-reliability-engineering/SKILL.md
|
||||
- artifact: Release plan and rollback strategy
|
||||
skill: ../../release-engineering/SKILL.md
|
||||
skill: ../release-engineering/SKILL.md
|
||||
|
||||
outputs:
|
||||
- gate-decision
|
||||
@@ -101,78 +101,78 @@ handoffs:
|
||||
supporting it; no gate passes on a bare checklist.
|
||||
|
||||
conflicts:
|
||||
- skill: ../../production-readiness/SKILL.md
|
||||
- skill: ../production-readiness/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
Both bundles include production-readiness. This bundle owns the launch
|
||||
gate decision; product-lifecycle routes phase 6 delivery handoff. Load
|
||||
the bundle matching the active decision context, never both at once.
|
||||
- skill: ../../production-readiness/SKILL.md
|
||||
- skill: ../production-readiness/SKILL.md
|
||||
with: agent-production-operations
|
||||
guidance: >-
|
||||
agent-production-operations consumes readiness outcomes as authority-
|
||||
gating inputs. Readiness reviews and go/no-go/defer/exception outcomes
|
||||
are produced here and consumed there.
|
||||
- skill: ../../release-engineering/SKILL.md
|
||||
- skill: ../release-engineering/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
Release engineering is shared. Route by context: gate-entry release
|
||||
evidence (this bundle) versus lifecycle delivery handoff
|
||||
(product-lifecycle).
|
||||
- skill: ../../release-engineering/SKILL.md
|
||||
- skill: ../release-engineering/SKILL.md
|
||||
with: agent-production-operations
|
||||
guidance: >-
|
||||
Release engineering is shared. Route by context: launch-gate release
|
||||
plans (this bundle) versus agent staged-rollout planning
|
||||
(agent-production-operations).
|
||||
- skill: ../../site-reliability-engineering/SKILL.md
|
||||
- skill: ../site-reliability-engineering/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
SRE is shared. This bundle routes to it for gate-entry SLO/error-budget
|
||||
evidence; product-lifecycle routes to it for delivery reliability.
|
||||
- skill: ../../site-reliability-engineering/SKILL.md
|
||||
- skill: ../site-reliability-engineering/SKILL.md
|
||||
with: agent-production-operations
|
||||
guidance: >-
|
||||
SRE is shared. This bundle uses it for gate-entry reliability evidence;
|
||||
agent-production-operations uses it for runtime latency/cost budgets
|
||||
and incident handoff. Incident command stays with SRE in both cases.
|
||||
- skill: ../../secure-software-engineering/SKILL.md
|
||||
- skill: ../secure-software-engineering/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
Security engineering is shared. Route by context: security evidence for
|
||||
launch gates (this bundle) versus trust-boundary work in lifecycle
|
||||
phases (product-lifecycle).
|
||||
- skill: ../../secure-software-engineering/SKILL.md
|
||||
- skill: ../secure-software-engineering/SKILL.md
|
||||
with: agent-production-operations
|
||||
guidance: >-
|
||||
Security engineering is shared. Route by context: launch-gate security
|
||||
evidence (this bundle) versus agent authority contracts and disablement
|
||||
security (agent-production-operations).
|
||||
- skill: ../../platform-engineering/SKILL.md
|
||||
- skill: ../platform-engineering/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
Platform engineering is shared. Route by context: gate-entry platform
|
||||
evidence (this bundle) versus lifecycle delivery handoff
|
||||
(product-lifecycle).
|
||||
- skill: ../../platform-engineering/SKILL.md
|
||||
- skill: ../platform-engineering/SKILL.md
|
||||
with: agent-production-operations
|
||||
guidance: >-
|
||||
Platform engineering is shared. Route by context: launch-gate platform
|
||||
evidence (this bundle) versus agent sandboxing and tool-execution
|
||||
isolation (agent-production-operations).
|
||||
- skill: ../../incident-learning/SKILL.md
|
||||
- skill: ../incident-learning/SKILL.md
|
||||
with: agent-production-operations
|
||||
guidance: >-
|
||||
Both bundles consume incident-learning records. This bundle uses
|
||||
incident history as gate-entry evidence; agent-production-operations
|
||||
consumes verified-closure records as escalation and disablement inputs.
|
||||
- skill: ../../qa-methodology/SKILL.md
|
||||
- skill: ../qa-methodology/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
QA methodology is shared. Route by context: launch verification evidence
|
||||
(this bundle) versus lifecycle phase 6 quality gates
|
||||
(product-lifecycle).
|
||||
- skill: ../../verification-methodology/SKILL.md
|
||||
- skill: ../verification-methodology/SKILL.md
|
||||
with: product-lifecycle
|
||||
guidance: >-
|
||||
Verification methodology is shared. This bundle uses it for boundary
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# Bundle manifest (bundle-manifest-v1) — see schemas/bundle-manifest-v1.schema.json
|
||||
# Bundle manifest (bundle-manifest-v1) — see ../schemas/bundle-manifest-v1.schema.json
|
||||
# and docs/bundle-manifest-design.md. Paths are relative to this bundle dir.
|
||||
|
||||
schema_version: 1
|
||||
@@ -20,23 +20,23 @@ audience: >-
|
||||
stages:
|
||||
- name: Web research
|
||||
skills:
|
||||
- ../../research-methodology/SKILL.md
|
||||
- ../research-methodology/SKILL.md
|
||||
- name: Source capture
|
||||
skills:
|
||||
- ../../research-methodology/SKILL.md
|
||||
- ../research-methodology/SKILL.md
|
||||
- name: Atomic extraction
|
||||
skills:
|
||||
- ../../research-methodology/SKILL.md
|
||||
- ../research-methodology/SKILL.md
|
||||
- name: Synthesis and durable capture
|
||||
skills:
|
||||
- ../../research-methodology/SKILL.md
|
||||
- ../research-methodology/SKILL.md
|
||||
|
||||
included_skills:
|
||||
- ../../research-methodology/SKILL.md
|
||||
- ../research-methodology/SKILL.md
|
||||
|
||||
prerequisites:
|
||||
- artifact: A research question or topic and access to web-research tooling
|
||||
skill: ../../research-methodology/SKILL.md
|
||||
skill: ../research-methodology/SKILL.md
|
||||
|
||||
outputs:
|
||||
- source-capture-record
|
||||
|
||||
Reference in New Issue
Block a user