sf-eval-starter

Orchestrate SpecFormula-driven RED→GREEN→REFACTOR TDD loops with sub-skill delegation and verifier polling.

77|15|Updated May 12, 2026
One-click install
npx skills add https://github.com/Waterball-Software-Academy/aixbdd --skill sf-eval-starter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sf-eval-starter
Source: https://github.com/Waterball-Software-Academy/aixbdd/tree/main/.agents/skills/sf-eval-starter
Command: npx skills add https://github.com/Waterball-Software-Academy/aixbdd --skill sf-eval-starter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the RED→GREEN→REFACTOR evaluation cycle by dispatching SpecFormula MCP jobs, preparing a verifiable test command, and polling for verdicts until completion.

Core Features & Use Cases

  • SF MCP goal orchestration: Fetches the next TDD goal and loops until the evaluator returns the all-done sentinel.
  • Sub-skill delegation by phase: Delegates phase-specific execution to aibdd-red-execute / aibdd-green-execute / aibdd-refactor-execute.
  • Deterministic evaluator-ready evidence: Builds an explicit, non-globbbed test command that includes the current goal feature plus all DONE feature files.
  • Runner launch preflight: Dry-runs the test command locally in the worker context and fails over cleanly when the environment can’t launch the runner.
  • Automated polling cadence: Polls mcp__sf__verify_goal_status using bash sleep 20 until completed=true and records the final verdict.

Quick Start

Ask your agent to run the sf-eval-starter skill with the /sf-eval-starter trigger; it will enter SF full-auto mode and drive the RED→GREEN→REFACTOR loop via SpecFormula MCP until all goals are verified.

Frequently Asked Questions about sf-eval-starter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate the RED GREEN REFACTOR TDD loop end-to-end?

You can automate the RED GREEN REFACTOR TDD loop by orchestrating SpecFormula MCP goals, delegating phase execution to mapped sub-skills, and polling verifier runs every 20 seconds until completion.

What is SpecFormula-driven TDD evaluation and how does it work?

SpecFormula-driven TDD evaluation fetches the next TDD goal, builds a deterministic non-globbed test command covering current and completed feature files, dispatches it via MCP, and polls verify_goal_status until the all-done sentinel is returned.

Can I run automated TDD orchestration with custom test runners and explicit feature scopes?

Yes, automated TDD orchestration works with any compatible test runner capable of executing explicit .feature scopes, requiring correct project routing via project_path and mapped aibdd-red-execute, aibdd-green-execute, and aibdd-refactor-execute sub-skills.

Why does my automated test evaluation fail before dispatching to the verifier?

Automated test evaluation fails cleanly when the local preflight dry-run cannot launch the test runner in the worker context, preventing invalid or environment-incompatible test commands from being dispatched.

Do I need MCP tool availability to run automated TDD evaluation cycles?

Yes, MCP tool availability is strictly required to fetch goals, dispatch SpecFormula jobs, and poll verify_goal_status every 20 seconds until the evaluator returns the completed verdict.

What's the best way to ensure deterministic test evidence during TDD phase execution?

To ensure deterministic test evidence, construct an explicit, non-globbed test command that includes the current goal feature file plus all previously completed DONE feature files before launching the runner.