S Skillteca
Receber por email
Explorar Categorias Coleções Newsletter
← Voltar para o catálogo

generator-draft-contract-parallel

Desenvolvimento Autor: redker56

Internal Auto-Harness generator skill for parallel sprint contract drafting. Use only inside the Generator subagent when it is producing or revising the current parallel sprint contract.

13estrelas
Atualizado há 6 meses
Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add redker56/auto-harness

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/generator-draft-contract-parallel/svg)](https://www.skillteca.com.br/skills/generator-draft-contract-parallel)
#test

Skills relacionadas

Ver todas de Desenvolvimento →

claude-api

153.1k

Build, debug, and optimize Claude API / Anthropic SDK apps. Apps built with this skill should include prompt caching. Also handles migrating existing Claude API code between Claude model versions (4.5 → 4.6, 4.6 → 4.7, retired-model replacements). TRIGGER when: code imports `anthropic`/`@anthropic-ai/sdk`; user asks for the Claude API, Anthropic SDK, or Managed Agents; user adds/modifies/tunes a C

Desenvolvimento #ai #api por anthropics

skill-creator

153.1k

Crie novas skills, modifique e aprimore as existentes, e meça seu desempenho. Utilize para desenvolver, editar, otimizar, testar e comparar skills, além de refinar suas descrições para maior precisão de acionamento.

Desenvolvimento #test por anthropics

claude-code-plugin-release

83.4k

Fluxo de trabalho automatizado de versionamento semântico e lançamento para plugins do Claude Code. Gerencia incrementos de versão em manifestos package.json, marketplace.json, plugin.json, publicação npm (para que npx claude-mem@X.Y.Z seja resolvido), verificação de build, marcação git, lançamentos no GitHub e geração de changelog.

Desenvolvimento #ai #git por thedotmack

claude-mem

83.4k

Contexto Persistente Entre Sessões para Cada Agente – Captura tudo o que seu agente faz durante as sessões, comprime com IA e injeta contexto relevante de volta em sessões futuras. Compatível com Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode e mais.

Desenvolvimento #ai por thedotmack

Alerta por categoria

Receba novas skills de Desenvolvimento toda segunda

1 email curto, só com as skills novas de Desenvolvimento. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Generator Draft Contract Parallel

This skill governs Generator contract mode.

At the start of this action, read these harness artifacts from the project:

  • .harness-parallel/status.md
  • .harness-parallel/intake.md
  • .harness-parallel/spec.md
  • .harness-parallel/design-direction.md
  • .harness-parallel/contracts/sprint-XX-contract.md when revising the current sprint contract.
  • .harness-parallel/contracts/sprint-XX-review.md when a prior review exists for the current sprint.

Then inspect the current project implementation relevant to this action:

  • Read the current implementation, architecture, routes, components, services, tests, and config that define the current sprint boundary and feasibility.
  • Use the codebase plus the harness artifacts to draft an implementation-ready contract.

Then read these skill references:

  • references/protocols/file-ownership.md
  • references/templates/sprint-contract.md

Follow these rules:

  • Treat .harness-parallel/intake.md, .harness-parallel/spec.md, the current sprint contract, and any current-sprint review artifact as authoritative inputs.
  • Write only the current sprint contract artifact.
  • If a review file already exists for the sprint, revise the contract directly against it.
  • Do not move the sprint toward implementation while the current sprint review result remains REVISE.
  • Treat an approved review as implementation guidance and cautions, not just a pass/fail stamp.
  • Keep the contract implementation-ready and evaluable from runtime plus named files.
  • Include both a human-readable Parallel Workstreams table and a machine-readable Dependency Graph JSON block.
  • The JSON graph is the source of truth for worktree scheduling.
  • Every node must declare non-overlapping owned_paths, explicit depends_on, and the behavior_ids it owns.
  • If the sprint should stay serial, emit exactly one node and say why in notes instead of omitting the graph.
  • Do not quietly violate locked architecture or stack choices; surface unavoidable deviations explicitly in the contract.
  • Do not modify status, review, QA, retest, or final artifacts.
Compartilhar X LinkedIn