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/mode-detection.md
View on GitHub# Mode detection
Inspect the current working directory. Be conservative. If anything looks unsafe, pause and ask.
## Greenfield
Effectively empty. A `.git/`, a stray `README.md`, or empty folders do not count. Announce: "Greenfield mode. Running the full interview."
## Migration
Pre-existing product artifacts: briefs, requirements, decks, interview notes, strategy docs, data dictionaries. Announce with a one-line inventory: "Migration mode. Found N product artifacts. I will copy them into `source/` (originals stay put) and ask only the gaps." Load `migration.md` before the interview.
## Active-repo
A working software repository: build manifests (`package.json`, `pyproject.toml`, `go.mod`, and the like), `src/`, `lib/`, `tests/`, CI config, a `Dockerfile`, or substantial source code. Do not scaffold without confirmation. Ask:
> "This looks like an active working repository (detected: <signals>). I can (a) scaffold the team loop here alongside the code, skipping any file that already exists, or (b) stop so you can run this in a different directory. Which one?"
Wait for the answer. On (a), run migration on any product artifacts mixed in with the code, ignoring code and build directories, and apply the no-overwrite rule strictly: existing `CLAUDE.md`, `INDEX.md`, `README.md`, `.gitignore`, and `.claude/settings.json` are kept, and the scaffold versions are skipped or merged per `SKILL.md` step 4.
## Edge cases
- Artifacts belong to someone else's project (a web app with no product docs): treat as active-repo and ask.
- The operator pasted artifacts but the directory is empty: treat the paste as migration input and confirm before writing anything into `source/`.
- Ambiguous: ask one question. Mode choice changes the whole flow.
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 |