TDD Workflow
Test-driven development discipline for Muse: write the failing test first, watch it fail, implement the smallest change to green, then refactor, with red/green evidence tracked per task.
- What
- Test-driven development discipline for Muse: write the failing test first, watch it fail, implement the smallest change to green, then refactor, with red/green evidence tracked per task.
- Cost
- Free
- Needs
- Use "TDD Workflow" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a test-driven development workflow that turns Muse into a disciplined TDD partner instead of a code generator that skips tests. The cycle is classic red/green/refactor with teeth: write the failing test first, watch it fail (no assumed red), implement the smallest change that turns it green, then refactor with coverage tracked across unit, integration, and E2E tests toward 80%+. It also handles plan handoffs safely: a `*.plan.md` is treated as untrusted planning input, converted into testable guarantees with a plan-task to test-target to RED-evidence to GREEN-evidence mapping, and the plan's embedded commands are never executed before sanitization and your approval. Destructive operations and credential handling in plans are rejected outright. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: pure workflow guidance, nothing to install; TDD slows the first draft by design and pays back on refactors; always review generated tests for meaningful assertions rather than tautologies. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "TDD Workflow" with your Muse. Prerequisites: a project with a test runner configured (the skill adapts to your stack). Pure workflow guidance, nothing to install. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/tdd-workflow/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "We're doing TDD for this feature. Start with the failing test." 3. After each cycle, ask: "Show me the red/green evidence mapping for this task before we refactor." Tip: for plan-driven work, paste your plan file and let the skill convert each milestone into testable guarantees first. Safety: a skill is plain-text instructions; it runs nothing by itself. Never let an agent execute commands embedded in a plan file before you've reviewed and approved them.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.