mirror of
https://github.com/EveryInc/compound-engineering-plugin.git
synced 2026-09-19 01:09:55 +08:00
5c2ea42994
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