* feat(skill): cross-pollinate the new tool wave into catalog routing
Wire the recent tool skill wave into the two-layer routing graph so the
new tool skills are reachable from the methodology skills that own their
domains, and vice versa:
- methodology -> tool down-routes: platform-engineering -> kubernetes,
terraform, telemetry, postgres, grafana; site-reliability-engineering ->
telemetry, grafana; data-engineering and backend-engineering -> postgres;
frontend-engineering -> mobile-development; verification-methodology ->
playwright, documents; technical-documentation -> documents
- neckbeard: add mobile-development and documents routing rows plus
change-surface coverage entries, and cross-link the lightweight
test-hardening path to qa-methodology's bounded mutation-review material
- collaboration layer: chief-of-staff-methodology -> slack/notion/email,
go-to-market -> crm, conditional-customer-success -> crm; fix the dead
seo-content-optimization reference in go-to-market (now seo-audit)
- references/skill-triggers.md: add trigger rows for the 14 new skills
- bring go-to-market's description up to the quality validator's
imperative-verb + negative-boundary requirement and regenerate catalogs
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
* fix(skill): add eval manifest for technical-documentation
The eval-coverage ratchet fails on modified skills without a schema-valid
manifest once coverage passes 50%. technical-documentation was modified by
the routing cross-pollination change and lacked one; add six output-quality
cases covering README authorship, API reference generation, CLI help design,
agent-facing docs, documentation-site IA, and troubleshooting sections.
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
---------
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
2026-08-04 12:46:06 -04:00
Magnus HedemarkGitHubusername <username>factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
Add a conditional skill for products with recurring human relationships.
Covers success plans, health evidence, renewal/expansion signals, QBRs,
handoffs, escalation, and closed-loop Voice of Customer. The skill is
conditional: it declines and routes away when the product has no accounts,
renewals, QBRs, or customer-success team.
Includes:
- SKILL.md with conditional frontmatter, trigger sections, four product-
model adaptations (B2B subscription, transactional, public-service,
internal product), core artifacts, privacy and human-judgment boundaries,
and routing to product-analytics-and-measurement, product-adoption,
product-experimentation, go-to-market, and product-lifecycle-learning.
- README.md with all five required human-facing sections.
- references/discovery-brief.md surveying existing content and defining
ownership boundaries and routing.
- references/privacy-and-human-judgment.md with consent framework,
surveillance-risk guidance, decision-support rules, and data
classification tiers.
- templates/applicability-decision.md, templates/success-plan.md,
templates/health-risk-record.md, and templates/escalation-and-
feedback-closure.md.
- evals/evals.json with 5 output-quality cases covering B2B subscription,
internal-tool decline (negative trigger), public-service routing,
renewal-risk with mixed signals, and conflicting health evidence.
- Updated root README.md catalog section, references/skill-triggers.md,
and regenerated marketplace/Codex/llms.txt catalogs.
Co-authored-by: username <username>
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
