teamwork-config

Name: teamwork-config
Author: JoshLuedeman

Teamwork Configuration Guidelines

by JoshLuedeman(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Instruction file imported from JoshLuedeman/scaffold (.github/instructions/teamwork-config.instructions.md). Copyright stays with the author.

Teamwork Configuration Guidelines

State files (.teamwork/state/) use YAML format with fields: workflow-id, current-step, current-role, status, created, updated.
Handoff artifacts (.teamwork/handoffs/) use Markdown with sections: Context, Decisions Made, Artifacts, Open Questions, Next Steps.
Memory files (.teamwork/memory/) use JSONL format — one JSON object per line with domain, type (pattern/antipattern/decision/feedback), and content fields.
Metrics files (.teamwork/metrics/) are gitignored — do not commit them.
Config file (.teamwork/config.yaml) defines model tier mappings and project-level settings.
Always validate YAML syntax before writing state files.
When updating state files, preserve existing fields and only modify the ones relevant to your step.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml

targets:
  - https://api.opensmartroute.ai/api/v1/registry/joshluedeman-scaffold-teamwork-config-instructions/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

joshluedeman-scaffold-teamwork-config-instructions.ocm.jsonjson

{
  "ocm": "1",
  "id": "joshluedeman-scaffold-teamwork-config-instructions",
  "kind": "skill",
  "name": "teamwork-config",
  "description": "Teamwork Configuration Guidelines",
  "publisher": "JoshLuedeman",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "github-instructions"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Teamwork Configuration Guidelines"
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github-instructions",
      "repository": "https://github.com/JoshLuedeman/scaffold",
      "path": ".github/instructions/teamwork-config.instructions.md",
      "ref": "28e312654716a34363871adf444b3111e5db4a9e",
      "url": "https://github.com/JoshLuedeman/scaffold/blob/28e312654716a34363871adf444b3111e5db4a9e/.github/instructions/teamwork-config.instructions.md",
      "key": "JoshLuedeman/scaffold/.github/instructions/teamwork-config.instructions.md"
    },
    "applies_to": ".teamwork/**"
  },
  "instructions": "# Teamwork Configuration Guidelines\n\n- State files (`.teamwork/state/`) use YAML format with fields: `workflow-id`, `current-step`, `current-role`, `status`, `created`, `updated`.\n- Handoff artifacts (`.teamwork/handoffs/`) use Markdown with sections: Context, Decisions Made, Artifacts, Open Questions, Next Steps.\n- Memory files (`.teamwork/memory/`) use JSONL format — one JSON object per line with `domain`, `type` (pattern/antipattern/decision/feedback), and `content` fields.\n- Metrics files (`.teamwork/metrics/`) are gitignored — do not commit them.\n- Config file (`.teamwork/config.yaml`) de",
  "cost": {
    "context_tokens": 203
  }
}

Fetch it by URL: GET /api/v1/registry/joshluedeman-scaffold-teamwork-config-instructions/manifest?version=1.0.0

About

Teamwork Configuration Guidelines

Use it

Manifest

Reviews