Coordinate TDD red-green-refactor cycles from task specs using bmad-commands.
npx skills add https://github.com/AcidicSoil/lms-llmsTxt --skill implement-acidicsoil
Please help me install this Agent Skill. Skill: implement Source: https://github.com/AcidicSoil/lms-llmsTxt/tree/main/.claude/skills/implement-v2 Command: npx skills add https://github.com/AcidicSoil/lms-llmsTxt --skill implement-acidicsoil
Teams implementing new features from task specifications often struggle to enforce a consistent, test-driven workflow that delivers reliable outcomes and traceable verification. This Skill provides a repeatable TDD cycle (RED, GREEN, REFACTOR) orchestrated via deterministic file and test operations using bmad-commands, ensuring acceptance criteria are met and coverage is tracked.
Supply a valid task_id to begin the TDD implementation workflow that loads the task spec, executes the RED-GREEN-REFACTOR cycle, and validates acceptance criteria.
High-intent search queries and answers about installing and using this skill.
To enforce strict TDD cycles, this Skill orchestrates a repeatable RED, GREEN, and REFACTOR workflow using deterministic file and test operations. It guides teams from task spec to green tests while tracking coverage.
Automating test verification for task specifications is achieved by loading the task spec via a task_id and executing the TDD workflow. The Skill validates acceptance criteria and reports telemetry for delivery governance.
The best way to drive feature development with red-green-refactor is using a coordinated workflow that applies automated test scaffolding and validations. This ensures acceptance criteria are met and outcomes are reliable.
Yes, you can use deterministic file operations to scaffold TDD tests. The workflow leverages bmad-commands to execute reliable file and test operations throughout the red-green-refactor cycle.
To track test coverage and telemetry during a TDD workflow, the Skill records telemetry and generates implementation metadata as output. This provides delivery governance and verifies that acceptance criteria are satisfied.
Yes, you need a valid task_id to start the test-driven development workflow. Supplying a task_id loads the specific task specification and initiates the RED-GREEN-REFACTOR cycle for automated validation.
openakitaExecute pre-defined scheduled tasks immediately using a valid task_id.
wsmanVerify development story completion against acceptance criteria and governance artifacts.
adolfoaranaes12Execute BMAD file I/O and test commands with JSON I/O and telemetry.
apakouAutomate test-driven development with RED, GREEN, and REFACTOR cycles.
