mirror of
https://github.com/magnus919/agent-skills.git
synced 2026-09-19 07:27:04 +03:00
Magnus Hedemarkandfactory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
a315b77bd8
Re-point relative references inside the six non-tailscale/workflow-architect
bundle dirs now that they live one level shallower at the repo root:
- bundle-root SKILL.md/manifest.yaml/README.md: ../../<target> -> ../<target>,
cross-bundle ../../bundles/<x> -> ../<x>
- forward-deployed-engineering references/: ../../../<target> -> ../../<target>
- product-lifecycle references cross-bundle ../../bundles/neckbeard -> ../../neckbeard
- product-lifecycle references/discovery-brief.md prose headings drop bundles/ prefix
- neckbeard eval shell commands bundles/neckbeard/eval -> neckbeard/eval
- production-excellence AGENTS.md depth note updated
- manifest header comments point at ../schemas/bundle-manifest-v1.schema.json
- regenerate docs/lifecycle-capability-matrix.{md,json}
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
5.3 KiB
5.3 KiB
Capability Map — product-lifecycle bundle
This map indexes product management capabilities to their owning specialist skills. When a user needs a specific capability, load the owning skill directly rather than traversing the full lifecycle. The lifecycle bundle provides cross-phase routing; this map provides point lookup.
Capability → Owning skill
| Capability area | Owning skill |
|---|---|
| Stakeholder discovery, user research, requirements elicitation | product-discovery |
| Product vision, strategy, competitive positioning | product-strategy |
| Strategic frameworks (Five Forces, Blue Ocean, Ansoff) | strategy-frameworks |
| Market sizing (TAM/SAM/SOM), product-market fit | product-strategy |
| Outcome roadmaps, Now/Next/Later views | product-roadmapping-and-portfolio |
| Strategic bets, portfolio management, continue/pause/kill | product-roadmapping-and-portfolio |
| Prioritization frameworks (RICE, MoSCoW, Kano, OST) | product-methodology |
| Information architecture, task flows, interaction design | product-design-and-ux |
| Experiment design, method selection, guardrails | product-experimentation |
| Statistical design, causal inference, A/B analysis | data-scientist |
| Specification, acceptance criteria, phase gates | spec-driven-development |
| Work breakdown, dependency mapping, rollout planning | implementation-planning |
| Release process, progressive delivery, versioning | release-engineering |
| Production readiness, launch evidence, go/no-go | production-readiness |
| Onboarding, activation, feature discovery, sustained use | product-adoption |
| Metric trees, tracking plans, outcome measurement | product-analytics-and-measurement |
| Customer success, account health, renewals (conditional) | conditional-customer-success |
| Outcome review, assumption updates, retirement decisions | product-lifecycle-learning |
| Decision rights, governance cadences, evidence standards | product-operations-and-governance |
| Financial modeling, unit economics, pricing | financial-modeling |
| Go-to-market strategy, positioning, acquisition | go-to-market |
| Privacy requirements, data lifecycle, retention | privacy-engineering |
| Security requirements, threat modeling, secure design | secure-software-engineering |
| Legal analysis, regulatory landscape, IP strategy | legal-strategy |
| Data pipelines, ETL, schema design | data-engineering |
| Production resilience, recovery, game days | resilience-and-recovery |
| Capacity planning, cost engineering, SLO-cost tradeoffs | capacity-and-cost-engineering |
| Migration planning, expand/contract, cutover | migration-engineering |
| Incident learning, post-incident improvement | incident-learning |
| Site reliability, SLOs, alerting, incident response | site-reliability-engineering |
| Platform engineering, infrastructure, CI/CD | platform-engineering |
| QA strategy, test planning, quality gates | qa-methodology |
| Verification methodology, evidence trails | verification-methodology |
| Software delivery lifecycle (SDLC) | neckbeard |
Cross-cutting concerns
These capabilities span multiple phases and are loaded on trigger, not by phase:
| Cross-cutting concern | Owning skill | When loaded |
|---|---|---|
| Product governance, decision rights, cadences | product-operations-and-governance | When setting up or changing governance; at phase boundaries where a decision needs formal authority |
| Prioritization (RICE, MoSCoW, Kano, OST) | product-methodology | When a phase produces alternatives that need ranking |
| Privacy and data protection | privacy-engineering | When any phase handles PII, consent, retention, or data flows |
| Security | secure-software-engineering | When any phase touches trust boundaries, auth, or sensitive data |
| Evidence standards and verification | verification-methodology | At every phase gate where evidence is required |