Orchestrate an enforced TDD cycle with phase validation and independent verification.
npx skills add https://github.com/ForgePlan/marketplace --skill tdd-forgeplan
Please help me install this Agent Skill. Skill: tdd Source: https://github.com/ForgePlan/marketplace/tree/main/plugins/agents-tdd/skills/tdd Command: npx skills add https://github.com/ForgePlan/marketplace --skill tdd-forgeplan
This Skill streamlines and enforces the Test-Driven Development (TDD) process, ensuring that developers adhere to the TDD methodology, from writing tests before code to certifying tests with a verifiable oracle.
To initiate an enforced TDD cycle for a feature, type /tdd.
High-intent search queries and answers about installing and using this skill.
You can automate test-driven development cycles by orchestrating phase-by-phase validation across planning, coding, testing, and verification. This enforces the TDD methodology by coordinating task dispatches for each phase, ensuring tests are written before code and certified with a verifiable oracle.
To enforce a TDD workflow, you need active PRD and SPEC documents containing at least one '#### Scenario' block. These preconditions ensure the test-driven development cycle has defined scenarios to validate against before coding begins.
Independent verification in test-driven development ensures tests are thorough and meet all specified scenarios. Once tests are certified, the SPEC becomes immutable through a frozen 'spec_hash', preventing further changes and guaranteeing that subsequent code adheres to the validated specification.
No, you cannot modify the SPEC after tests are certified in a TDD cycle. The system requires a frozen 'spec_hash' for SPEC immutability, which prevents changes once the independent verification phase confirms that tests meet all scenarios.
The best way to ensure developers follow TDD methodology is through enforced phased execution. By guiding the cycle through plan, code, test, validate, and code phases with precise validation, the workflow standardizes testing and prevents skipping the test-first approach.
Your TDD workflow requires a frozen spec hash to guarantee SPEC immutability during independent verification. This ensures the test-driven development cycle remains standardized, preventing specification changes after tests are certified against the defined scenarios.
stellarlinkcoGenerate test cases from PRD documents covering functional, edge, error, and state transition scenarios.
48Nauts-OperatorImplement a Test-Driven Development workflow with RED-GREEN-REFACTOR cycles.
softmgCoordinate multi-agent software development workflows with test-first implementation.
sighupAutomate end-to-end testing and bug-fix cycles for spec-driven workflows.
