joycraft-implement

Automate TDD workflows by parsing specs, writing failing tests, and guiding code changes.

14|1|Updated Mar 23, 2026

Search Tags:#automation #workflow #tdd #implement #specs #tests #joycraft

Ready to run

npx skills add https://github.com/maksutovic/joycraft --skill joycraft-implement

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: joycraft-implement
Source: https://github.com/maksutovic/joycraft/tree/main/.agents/skills/joycraft-implement
Command: npx skills add https://github.com/maksutovic/joycraft --skill joycraft-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end TDD workflow for implementing atomic specs by parsing specs, writing failing tests, and guiding code changes until all tests pass.

Core Features & Use Cases

Coordinates one or more specs through the TDD cycle: red, green, refactor.
Enforces discipline: tests first, verify failures, then implement until green.
Validates spec metadata (Acceptance Criteria, Test Plan, Constraints) and reports progress.

Quick Start

Provide one or more spec paths (e.g., docs/specs/feature-name.md) to start the TDD cycle.

Frequently Asked Questions about joycraft-implement

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

FAQPage Schema

How do I automate TDD workflow for implementing specs?▼

Automating the TDD workflow involves parsing spec paths, writing failing tests, and guiding code changes until all tests pass. This enforces red-green-refactor discipline by validating spec metadata and acceptance criteria.

Can I coordinate multiple specs in a single TDD session?▼

Yes, you can coordinate multiple specs in a single TDD session. The process parses each spec path, enforces test-first discipline across all provided files, and validates progress against individual acceptance criteria and test plans.

What do I need to start test-driven development for atomic specs?▼

To start test-driven development for atomic specs, you need a valid spec path input containing defined Acceptance Criteria, a Test Plan, and Constraints. The workflow validates this metadata before initiating the red-green-refactor cycle.

Does the TDD cycle validate progress against spec acceptance criteria?▼

Yes, the TDD cycle validates progress against spec acceptance criteria. It parses the metadata, writes failing tests first, verifies the failures, and then guides code implementation until all tests reach green status.

What is the best way to enforce red-green-refactor discipline in automated workflows?▼

The best way to enforce red-green-refactor discipline is to automate the end-to-end workflow: parse specs, write failing tests, verify the failures, and guide code changes until all tests pass and acceptance criteria are met.

Why does TDD spec execution require validating spec metadata and constraints?▼

TDD spec execution requires validating spec metadata and constraints to ensure the generated tests align with the Acceptance Criteria and Test Plan. This validation prevents implementation drift and reports accurate progress status.