Skip to content

hollandkevint/data-product-operator / skills/team-loop

team-loop

Verified

Formerly dpm_os. Initialize a Team Loop workspace, a markdown workspace for one data product operator to move one data product decision from discovery to controlled release with three manual gates, a weekly decision packet, and an append-only decision log. Detects greenfield, migration, or active-repo mode, asks only for missing load-bearing context, copies the deterministic scaffold without overwriting, populates fields with provenance tags, runs the validator, and hands off the first three actions. Use when invoked as `/team-loop` (formerly `/dpm-os`) or when asked to set up a Team Loop in a directory.

prompts/interview.md

View on GitHub
# Interview

Ask in batches of three or four questions. Short and direct. In migration mode, skip what the sources already answer.

## Batch A — Product and decision
1. Product line, one-line description, accountable owner.
2. The first user, and the decision they make today that this product should improve.
3. The buyer, if different from the user.
4. The current alternative and what it costs.

## Batch B — Owners and decision rights
1. Executive sponsor, final release decider, working owner.
2. Data acceptance owner and engineering feasibility owner.
3. The weekly cadence: packet day, session day, review window.
4. Who resolves a scope or authority conflict.

## Batch C — Data and contract
1. Data sources, and who owns each.
2. Grain, coverage, freshness, and the known gaps.
3. The one outcome metric, with grain and window.
4. Quality thresholds the release must meet, and who accepts them.

## Batch D — Access, claims, and boundaries
1. What the team can claim now, and what it cannot claim yet.
2. Licensing, privacy, and naming rules (partners that stay unnamed, regulated data).
3. The delivery surface and what it may not do.
4. Anything off-limits beyond the defaults in `CLAUDE.md`.

## After the interview

Summarize back in six to ten bullets. Surface contradictions. Confirm before scaffolding.

## What the answers feed

| Batch | Question | Populates |
| --- | --- | --- |
| A | 1 | `context/product.md` § Product line and owner; `README.md` |
| A | 2, 3, 4 | `context/consumers.md` |
| B | 1, 2 | `context/team-and-decision-rights.md` § Roles |
| B | 3 | `context/team-and-decision-rights.md` § Cadence |
| B | 4 | `context/team-and-decision-rights.md` § Escalation path |
| C | 1, 2 | `context/data-contract.md` |
| C | 3, 4 | `context/metrics-and-quality.md` |
| D | 1 | `context/commercial-and-access-boundaries.md` § Claims |
| D | 2, 3 | `context/commercial-and-access-boundaries.md` § Access and § Delivery surface |
| D | 4 | `CLAUDE.md` § Off-limits |

Claims born in this interview carry `(stakeholder-verbal, <name>, <date>)`. Never fabricate a source.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 196kUpdated Claude CodeCodexVerifiedInstall