Mmcp.market

spec-execution skill

by a5c-ai·a5c-ai/babysitter·1.8k stars·MIT

6-phase iterative specification execution workflow covering implementation, testing, review, improvement, commit, and progress tracking with quality-gated convergence.

A100/100content scan

Is the spec-execution skill safe?

Clean: nothing in its files matched our rules. We read 2 files in the folder on 2026-09-28.

No findings.

Install the spec-execution skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/a5c-ai/babysitter.git /tmp/babysitter
mkdir -p ~/.claude/skills
cp -r /tmp/babysitter/library/methodologies/claudekit/skills/spec-execution ~/.claude/skills/spec-execution
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

  • 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)

More skills from a5c-ai/babysitter

  • Aadversarial-reviewFresh adversarial code review with binary PASS/FAIL verdicts, evidence citations, and anchoring bias prevention via fresh reviewer spawning.
  • Aagent-boosterWASM-based instant code transforms for simple tasks, achieving 352x speedup over LLM inference with zero cost.
  • Aagent-coordinationCoordinate Crew (persistent) and Polecat (transient) agents using Gas Town's hook-based work distribution and GUPP principle.
  • Aagent-dispatch
  • Aanti-driftHierarchical coordination and drift detection with frequent checkpoints, shared memory coherence validation, role specialization enforcement, and short task cycles.
  • Aarchitecture-design
  • Aarchitecture-patternsSystem and API design guidance covering component boundaries, data flow, integration patterns, and scalability considerations.
  • Aassimilate-popular-workflowsThis skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover SKILL.md files in repos", "research external skills", "find workflow patterns", "survey the skill landscape", "what skills exist out there", or wants to investigate public repositories for extractable processes, babysitter plugins, and reusable procedural insights. Searches GitHub for SKILL.md files, classifies repos by archetype, and maintains structured research under docs/reference-repos/.
  • Aaudit-trail
  • AbabysitOrchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
  • Ababysit-babysitter-issuesThis skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.
  • Abehavior-contractBug condition/postcondition formalization as testable Behavior Contracts. Defines invariants that must be preserved across fixes.

All agent skills → · MCP servers