feat(plugin): add tdd skill for test-driven development workflow#230
feat(plugin): add tdd skill for test-driven development workflow#2300ut5ider wants to merge 2 commits intoEveryInc:mainfrom
Conversation
|
Really excited to have this merged! |
tmchow
left a comment
tmchow
left a comment
There was a problem hiding this comment.
Can you also rebase against main? I want to sit with this a bit to consider how this will work provided we may make changes to ce:plan.
There was a problem hiding this comment.
Drop this, bumping the metadata is part of the release process.
There was a problem hiding this comment.
Drop this, bumping the metadata is part of the release process.
Add opt-in TDD skill that integrates red-green-refactor discipline into implementation plans when triggered by TDD-related keywords. Includes the full cycle (RED/GREEN/REFACTOR), plan augmentation format, test granularity guidance, and anti-patterns reference. Language-agnostic, strongly opinionated on process. Designed as an MVP starting point for public submission. Bumps plugin to 2.39.0 (21 skills).
- Fix internal contradiction: discipline rule EveryInc#2 now scoped to behavioral changes, consistent with 'Skip TDD when' section - Fix 'one assertion' to 'one behavior per test' throughout - Add activation sequence: test runner detection, plan vs no-plan routing - Add characterization test guidance for untested codebases - Expand RED step guidance for when test passes immediately - Declare Classical/Chicago school stance, acknowledge London school - Rename 'Plan Augmentation' to 'Restructuring Plans for TDD' - Merge decomposition heuristic into plan section, remove redundancy - Remove duplicate anti-patterns link - Add 3 AI-specific anti-patterns: over-implementing on GREEN, mirror tests, skipping RED verification - Fix Ruby-biased code examples in anti-patterns for language neutrality - Add code example to 'Ignoring Test Failure Messages' entry - Add Classical school context to 'Mocking Everything' entry
0ut5ider
force-pushed
the
feature/tdd-skill
branch
from
3c67cd2 to
9d30cc3
Compare
@tmchow, rebase against |
|
@tmchow I'm interested in using this. Could this be prioritized to ship? |
…work Bridge the gap between plans that say nothing about execution discipline and plans that micromanage every test cycle. When TDD, test-first, or characterization-first work is clearly warranted, plans now carry a lightweight one-line signal in the relevant implementation units, and ce:work honors it during execution. Motivation: PR #230 introduced a standalone TDD skill, but it operated outside the plan-work pipeline. PR #272 shipped ce:plan-beta with a decision-first planning philosophy that explicitly avoids micro-step choreography. This change completes the circuit — plans can now signal execution posture without becoming execution scripts, and ce:work responds proportionally without becoming a TDD state machine. ce:plan-beta changes: - New principle: carry execution posture lightly when it matters - Step 1.1b: detect posture signals from user, origin doc, or local research - Optional Execution note field on implementation units - Guard rails against RED/GREEN/REFACTOR substep expansion - Final checklist verifies posture is carried forward when warranted ce:work changes: - Phase 1: read Execution note from plan units, carry into tasks - Honor explicit user TDD requests even without plan Execution notes - Subagent dispatch includes Execution note - Post-loop guidance for test-first and characterization-first execution - Guardrails: verify red before green, no combined test+impl steps, skip test-first for trivial renames/config/styling
|
I'm going to close this one as it is in conflict with how we are thinking we want to proceed with the new |
|
@tmchow I like your implementation with /ce:plan-beta. I'm glad this PR provided some ideas worth incorporating into the future of ce! |
|
@tmchow No worries! @0ut5ider Thanks for the inspiration, I've used this to generate an E2E (Cypress specific) and unit (vitest) for a full stack Node.js based app checked into our local repos. Once I get time (likely next week) I'll abstract those and likely generalize them so they use whatever tooling is available (Cypress, Playwright, vitest, jest, etc) and share it with you if you're interested. |
|
@kevinold absolutely I am interested! |
4 participants
Summary
tddskill that integrates red-green-refactor discipline into implementation plans/ce:planWhat's Included
skills/tdd/SKILL.md-- Core skill with:skills/tdd/references/anti-patterns.md-- 10 common TDD mistakes with examples and corrections:Plugin Metadata
2.39.0(MINOR -- new skill)Validation
quick_validate.pypasses clean