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.
prompts/post-scaffold.md
View on GitHub# Post-scaffold
Run after the scaffold is copied and populated.
## 1. Validate
Run `python3 scripts/validate.py .` from the instance root. Fix every finding. Re-run until exit 0.
## 2. Walk the links
Open `INDEX.md`, `CLAUDE.md`, and `rules/INDEX.md`. Follow every relative link. The validator already checked resolution; here you confirm the routing reads correctly for a human.
## 3. The three first actions
Lead the handoff with these, in order:
1. **Fill decision rights today.** `context/team-and-decision-rights.md` § Roles. Name the final release decider, the data acceptance owner, and the engineering feasibility owner. Nothing else moves until these are named.
2. **Write the first packet this week.** Copy `packets/_TEMPLATE.md` to `packets/<date>-weekly-packet.md`. Put the one decision that matters most in the first row.
3. **Log the first pending decision.** One row in `decisions/LOG.md` and one record from `decisions/_SCHEMA.md`, status `pending`, with a decider and a review date.
## 4. Contradictions
List one to three contradictions found during migration or the interview, each with the two sources that disagree and where the tension now lives in `context/`. If none were found, say so.
## 5. Gaps
Two or three concrete gaps, no more. Example: "`context/data-contract.md` has no freshness for the claims source."
## 6. Receipt
Run `python3 scripts/validate.py --summary .` and copy its two lines into the receipt as they print. Then print:
```
Self-test receipt:
- Validator: exit 0
- Links walked: N
- <the two --summary lines>
- Contradictions surfaced: N
```
## 7. Hand off
Order: three first actions, contradictions, gaps, one paragraph on what was built. Do not lead with a folder map. Then stop and wait for the operator's first real task.
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 |