hollandkevint/data-product-operator / skills/team-loop
team-loop
VerifiedFormerly 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.
scaffold/decisions/_SCHEMA.md
View on GitHub# Decision record schema
> Read this before writing a decision file. The validator rejects a record that is missing a required heading or that has an untagged evidence row.
**Pre-save self-check:**
1. Count the rows under `## Evidence` and `## Explicitly NOT doing`. Count the provenance tags in those rows. The numbers match.
2. `## Status` is one of `pending`, `decided`, `superseded`.
3. `## Decider` names one person.
4. `## What would reverse this` is specific and observable: a metric threshold, a named signal, a date.
5. `## Review date` is a real date.
6. Commentary and gaps go under `## Remaining ambiguities`, never under `## Evidence`.
Filename: `YYYY-MM-DD-<slug>.md`
```markdown
# Decision: <one-line statement>
## Status
pending | decided | superseded
## Date
YYYY-MM-DD
## Decider
<named person>
## Context
<!-- Two to four sentences. The fork in the road. -->
## Options considered
1.
2.
## Decision
<!-- What was picked. Empty for pending. -->
## Why
<!-- The reasoning. Specific. -->
## Evidence
- <claim> `<provenance-tag>`
## Explicitly NOT doing
- <not-doing> `<provenance-tag>`
## What would reverse this
<!-- Observable condition. -->
## Review date
YYYY-MM-DD
## Remaining ambiguities
<!-- What is still unknown. -->
## Linked
- Context: `../context/<file>.md`
- Packet: `../packets/<file>.md`
- Gate: `../rules/<file>.md`
```
## Provenance enum
Every row under `## Evidence` and `## Explicitly NOT doing` ends with exactly one of:
- `[source/...](../source/...)` — direct citation of a verbatim input
- `[ingestion/...](../ingestion/...)` — a synthesized note that cites source/
- `(stakeholder-verbal, <name>, <YYYY-MM-DD>)`
- `(intuition, <name>, <YYYY-MM-DD>)`
- `(industry-knowledge)`
- `(chat, no artifact)`
- `(hub, <name>, <YYYY-MM-DD>)` — an engagement hub or shared working document
- `Unknown` — the claim is recorded but has no source yet
A record built from mixed-trust evidence wears that mix on its face.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| 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: 196k | Updated | Claude CodeCodex | Verified | Install |