Start with the job, then find an open-source answer

authz-architect maps protected resources, actors, roles, and tenancy before choosing RBAC, ABAC, or ReBAC and an enforcement layer. A policy matrix drives consistent object-level checks and coverage tests, while adversarial probes target IDOR, privilege escalation, and cross-tenant leaks. The workflow requires previously failing cases to pass after remediation before authorization is attested.

docs-product-orchestrator treats documentation as a product: it defines audiences and information architecture, separates tutorials, how-to guides, explanations, and reference, and uses Diataxis with docs-as-code. It can generate API reference from source, check links and examples in CI, detect drift, and verify the published site. The focus is a coherent, maintainable documentation experience rather than a single page.

content-localization-orchestrator localizes marketing pages, docs, and product copy rather than only extracting code strings. It sets locale strategy, maintains glossaries and translation memory, supports transcreation, checks cultural and legal fit, and accounts for RTL direction and layout length. The result is prepared for coordinated publishing across multiple locales.

newsletter-program-engine treats a newsletter as a recurring program rather than a one-off email. It helps define positioning and cadence, plan repeatable issues, segment the list, test subject lines, and design growth loops. Performance from each issue feeds the next planning cycle, giving the program state and a way to improve over time.

pro-se-dispute-resolver turns a consumer or tenant problem into a dated fact record, demand letter, and route to the appropriate complaint forum. It helps check jurisdiction, citations, addresses, and deadlines, but it does not file anything, provide legal representation, or guarantee an outcome. Every fact and date must be verified before sending, with complex matters escalated to a licensed attorney.

raise-room-orchestrator runs the fundraise beyond a pitch deck: it coordinates the narrative and financial model, audits gaps in the data room, tracks investors, and prepares diligence Q&A from the company’s actual materials. The workflow is designed for rounds from pre-seed through Series B and keeps missing documents and follow-up work visible as the process moves forward.

This skill designs source-to-warehouse data ingestion with contracts, idempotency, duplicate protection, schema-drift checks, data-quality gates, lineage, backfills, freshness monitoring, and runbooks. It covers ETL, ELT, and CDC through ordered phases and blocks unsafe progression when a dependency or validation fails. The result is a recoverable workflow with clearer failure handling rather than a brittle one-off load.

learning-experience-architect applies backward design to turn source material into measurable objectives, a module map, lessons, and aligned assessments. Its completion check requires every objective to be taught and assessed without orphaned goals, then it can export the course to Markdown, SCORM, or an LMS-ready structure. The result is a learnable sequence rather than a flat outline.

agent-system-designer starts with a capability specification and routes the design among a skill, subagent, MCP server, or workflow. It defines tool contracts, context and state strategies, least-privilege permissions, safety boundaries, and a runnable test harness before implementation. The process is intended to catch overlapping schemas, context failures, and destructive access early, when architectural changes are still reversible.

medical-bill-and-claim-appeal-navigator turns a denial notice, itemized bill, and explanation of benefits into an error log, appeal materials, and a negotiation script. It can organize checks for duplicate charges, coding issues, unbundling, balance billing, and medical-necessity support, but never invents codes, statutes, or deadlines. It is not legal or medical advice; dates and citations must be confirmed for the plan and state.

extraction-automation-architect takes a web-extraction idea through legality and terms checks, source selection, API versus browser strategy, anti-bot constraints, typed schemas, selector healing, scheduling, validation, and monitoring. It produces durable configuration and run records instead of a single fetch. Rate limits, robots.txt, and site changes remain explicit operating constraints, so recurring jobs can be checked when data becomes stale.

api-contract-governor governs REST, GraphQL, and protobuf/gRPC contract changes through a checked-in registry. It classifies deltas, discovers affected consumers, blocks unregistered breaking changes, and tracks versioned deprecation, migrations, and the final sunset gate before retirement.

upgrade-pilot sequences major framework or dependency upgrades by dependency order, applies codemods before hand fixes, and isolates the work in a worktree. A resumable ledger records checkpoints, while install, typecheck, build, and test gates block the next step until the current one is green.

perf-optimization-loop refuses to edit code before a measured baseline exists. It isolates one experiment at a time, re-runs the same benchmark to decide KEEP, REVERT, or INCONCLUSIVE, records both wins and negatives, and generates a CI performance budget to catch regressions.

monetization-architect carries pricing work from value-metric discovery and willingness-to-pay studies through tiers, revenue scenarios, and a safe live migration. It defines grandfathering, cohorts, churn guardrails, rollback triggers, and modeled-versus-actual reconciliation from user-supplied data, rather than reading a billing system.

talk-and-keynote-architect builds the spoken narrative before slides: one through-line, a timed beat sheet, an ear-friendly script, hostile Q&A preparation, and iterative rehearsal cuts. It measures the real runtime and produces a day-of kit, while routing the actual deck to a separate design layer.

eval-harness-architect starts from the decision an evaluation must support, then builds versioned datasets, holdouts, dimension-specific scorers, and a calibrated judge. It measures significance, wires regression gates and PR scorecards into CI, and adds drift and production-feedback loops without fabricating labels or benchmark numbers.

single-source-content-factory turns one transcript, draft, talk, or document into a canonical asset with addressable content atoms. It adapts those atoms for blogs, newsletters, LinkedIn, X, video scripts, and email, checks voice and claim consistency, emits a traceability matrix, and identifies only the outputs affected by source changes; it plans cadence but does not post or schedule.