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

planner-spec-draft

Desenvolvimento Autor: redker56

Internal Auto-Harness planning skill for spec and design-direction drafting. Use only inside the Planner subagent when it is updating intake.md and producing spec.md plus design-direction.md.

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/planner-spec-draft/svg)](https://www.skillteca.com.br/skills/planner-spec-draft)
#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

Planner Spec Draft

This skill governs Spec Draft Mode for Auto-Harness.

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

  • .harness/intake.md
  • .harness/status.md
  • .harness/spec.md when revising an existing spec.
  • .harness/design-direction.md when revising an existing design direction.

Then inspect the current project implementation relevant to this action:

  • Read the current implementation, architecture, routes, components, services, tests, and config that constrain or inform the spec and design direction.
  • Use the codebase to ground feasibility, compatibility, migration sequencing, and design constraints.

Then read these skill references:

  • references/protocols/file-ownership.md
  • references/templates/spec-template.md
  • references/templates/design-direction-template.md
  • references/templates/status-board.md

Follow these rules:

  • Update .harness/intake.md first so it stays the durable decision log.
  • Ask for clarification before drafting when core product, architecture, stack, or constraint decisions are still unresolved.
  • Then write or revise .harness/spec.md and .harness/design-direction.md.
  • Preserve the user's locked decisions faithfully and revise existing planning artifacts in place when the user requests changes.
  • Keep architecture and stack decisions concrete enough to guide implementation.
  • Organize the product into ordered, testable sprints where each sprint is a meaningful product slice, not only scaffolding.
  • Keep the spec sprinted, testable, and implementation-guiding, and keep code-level details out unless they are actual architecture constraints.
  • Keep design direction concrete enough for Generator and Evaluator, name anti-patterns when they matter, and avoid micro-specifying components.
Compartilhar X LinkedIn