Receber por email
← Voltar para o catálogo

spec-execution

Fluxo de trabalho de execução de especificação iterativo de 6 fases, cobrindo implementação, teste, revisão, melhoria, commit e acompanhamento de progresso, com convergência controlada por qualidade.

1.4kestrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add a5c-ai/babysitter

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

Skills relacionadas

Ver todas de Automação →

Alerta por categoria

Receba novas skills de Automação toda segunda

1 email curto, só com as skills novas de Automação. 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

Spec Execution

Overview

Executes a feature specification through 6 iterative phases with quality-gated convergence. Each phase builds on the previous, with improvement cycles triggered when quality falls below threshold.

Six Phases

Phase 1: Implementation

  • Read specification for requirements and architecture
  • Implement each requirement following project conventions
  • Add type definitions and JSDoc documentation
  • Implement error handling for all failure modes

Phase 2: Test Writing

  • Write unit tests for each module/function
  • Write integration tests for API boundaries
  • Cover all acceptance criteria from the specification
  • Test edge cases and error paths

Phase 3: Code Review

  • Verify all requirements are implemented
  • Check acceptance criteria are tested
  • Review architecture adherence
  • Assess code quality

Phase 4: Iterative Improvement

  • Address review findings
  • Fix failing tests
  • Resolve architecture deviations
  • Re-verify quality (convergence loop, max 3 cycles)

Phase 5: Atomic Commit

  • Group changes into logical atomic commits
  • Descriptive messages following project conventions
  • Separate production, test, and config changes
  • Include specification reference

Phase 6: Progress Tracking

  • Requirement completion percentage
  • Test coverage summary
  • Quality score report
  • Remaining work identification

Quality Gate

Quality threshold defaults to 80. If not met after max improvement cycles, a human breakpoint is triggered for review.

When to Use

  • /spec:execute [file] slash command
  • After spec creation when ready to implement

Processes Used By

  • claudekit-spec-workflow (execute mode)
Compartilhar X LinkedIn