AGENT SKILL

data-team-capability-design

Maps data engineering work to required capabilities, assesses depth and concentration risk, and recommends role, staffing, or upskilling actions. Use when designing a data team, conducting a skills-gap analysis, clarifying roles, or planning capability growth.

License 许可
Apache-2.0
所属仓库
cwik-tech/octopus
最近更新
2026-10-27
Stars
★ 0
Forks
0

01 前言 Front Matter

name
data-team-capability-design
description
Maps data engineering work to required capabilities, assesses depth and concentration risk, and recommends role, staffing, or upskilling actions. Use when designing a data team, conducting a skills-gap analysis, clarifying roles, or planning capability growth.

03 SKILL.md 正文

Data Team Capability Design

Purpose

Assess whether a data engineering function has the capabilities needed to deliver and operate its data products safely. Convert the assessment into clear actions rather than a generic competency list.

Method

1. Define the demand profile

Capture the work the organization must perform now and in the planning horizon:

  • Data-product types: ingestion, transformation, serving, APIs, semantic models, ML features, reporting datasets
  • Processing modes: batch, streaming, near-real-time
  • Reliability needs: criticality, freshness, recovery objectives, support expectations
  • Environment: cloud, hybrid, on-premises, regulated, multi-tenant
  • Consumers: analytics, data science, applications, operations, external partners, business teams

Do not infer advanced capability needs solely from tool names. Tie each capability to an actual use case or foreseeable demand.

2. Build the capability map

Assess the following categories at an appropriate depth for the demand profile:

Capability What good coverage means
Data-product discovery Translates business use cases into usable, bounded data products
Pipeline engineering Builds maintainable ingestion, transformation, orchestration, and delivery flows
Distributed systems and performance Designs for scale, failure, cost, and workload behavior where relevant
Data modeling and schema evolution Defines durable contracts, semantics, compatibility, and lifecycle rules
Data quality and testing Specifies controls, automated tests, monitoring, and remediation ownership
Platform and operations Operates environments, access, deployment, observability, incident response, and recovery
Governance and security Handles lineage, access, sensitive data, retention, auditability, and policy implementation
Analytics and consumption Enables documented, discoverable, fit-for-purpose consumption patterns
Data science collaboration Supports reproducible features, training data, handoffs, and production interfaces
Domain and stakeholder communication Understands operational context and manages expectations, adoption, and feedback
Technical leadership Makes tradeoffs, mentors others, and prevents local optimizations from harming the system

Add domain-specific capabilities only when they materially affect outcomes.

3. Score coverage honestly

For every capability, classify:

  • Absent: No credible coverage.
  • Fragile: One person, external dependency, or unproven coverage.
  • Developing: Some capability exists but cannot reliably own consequential work.
  • Adequate: Demonstrated delivery and support capability with documented practices.
  • Resilient: Multiple practitioners, backup coverage, standards, and repeatable knowledge transfer.

Record evidence: production experience, shipped work, incident ownership, peer review, certifications only as secondary evidence, and stakeholder feedback. Avoid averaging partial skill levels into false assurance.

4. Identify concentration and interface risks

For each critical capability, ask:

  • Is there a named primary and backup?
  • Can the team operate when the primary is unavailable?
  • Are decisions, patterns, and runbooks documented?
  • Does another team own a required dependency without a defined interface?
  • Is ownership split so that failures will be disputed rather than resolved?

5. Select the intervention

Choose the lightest credible response:

Condition Preferred intervention
Temporary, bounded gap Partner, contract, or targeted advisory support
Adjacent skills and time to learn Upskill with supervised production work
Persistent strategic gap Hire or establish a durable internal role
Repeated manual work Automate, standardize, or reduce demand
Low-value capability demand Defer, retire, or narrow the service
Unclear ownership Define boundary, decision right, and escalation path first

Output

Provide:

  1. Demand profile and assumptions.
  2. Capability matrix with coverage rating, evidence, concentration risk, and accountable owner.
  3. Top capability gaps ranked by business impact and urgency.
  4. Recommended interventions, including why hiring, upskilling, partnering, automation, or deferral is appropriate.
  5. A review cadence and observable measures of improved coverage.

Quality Checks

  • Every proposed role maps to accountable work and an interface.
  • Critical capabilities have backup coverage or an explicit mitigation.
  • Recommendations distinguish current needs from future-stage needs.
  • Gaps are stated without stigmatizing individuals.
  • Headcount recommendations state workload and service assumptions.

04 同仓库更多 Skills

cwik-tech
cwik-tech/octopus

twenty-year-land-plan

Apply the Bren discipline of evaluating every land and development decision on a twenty-year horizon, with a comprehensive plan for how the land, the community, and the surrounding public infrastructure evolve together. Deals optimized for a five-year exit are structurally different from deals that compound across generations; insist on knowing which kind you are making. Use when evaluating land, entitlements, master-planned development, or phasing decisions, and when separating five-year exit deals from generational holds.

★ 0
cwik-tech
cwik-tech/octopus

thematic-gut-check

Apply the Gray discipline of identifying the structural theme behind every real estate deal, testing where that theme sits in its capital-flow lifecycle, and insisting that deals without a named theme — or deals late in a crowded theme — clear a higher bar. A mediocre deal in a strong theme usually beats a clever deal in a weak one. Use when naming the structural thesis behind a deal, judging whether that theme is early or crowded, and setting the bar the deal must clear.

★ 0
cwik-tech
cwik-tech/octopus

supply-pipeline-gut-check

Apply the Zell discipline of grounding every real estate thesis in the local supply pipeline. Demand counts over adjectives — units under construction, units permitted, units proposed — and convert them into a forward absorption schedule. A deal that ignores the pipeline is a bet on a market you have not actually studied. Use when validating a market thesis, forecasting absorption and rent growth, or counting units under construction, permitted, and proposed.

★ 0
cwik-tech
cwik-tech/octopus

ruin-scenario-mapping

Apply the Taleb discipline of identifying, for every real estate deal, the specific chain of events that produces ruin — permanent, unrecoverable capital loss — and verifying that no single such chain has non-trivial probability. Deals with any plausible ruin path must be restructured or abandoned. Use when sizing leverage, testing refinancing, covenant, and liquidity risk, or checking whether any single failure chain can permanently wipe out the position.

★ 0
cwik-tech
cwik-tech/octopus

revenue-cost-architecture

Design a venture's revenue streams, pricing logic, cost structure, and unit economics so the business model has a coherent theory of value capture, not just value creation. Use after the value proposition and customer segment are set and before financial projections, when choosing a pricing model, calculating contribution margin or CAC payback, or checking whether the unit economics hold at scale.

★ 0
cwik-tech
cwik-tech/octopus

replacement-cost-stress-test

Apply the Buffett discipline of pricing every real estate asset against the cost to rebuild it from scratch. The ratio of purchase price to replacement cost sets a ceiling on long-run downside: below replacement cost, new supply cannot profitably undercut you; at or above it, you are buying a liability disguised as an asset. Use when setting a purchase price, judging downside protection, or testing how exposed an asset is to newly built competing supply.

★ 0