refactor(openspec): prune template comments to one-liners

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Author: iobuhov

openspec/schemas/tdd/templates/design.md

@@ -1,50 +1,28 @@
 ## Test Cases
 
-<!--
-Define test cases that will verify the fix or refactoring.
-
-For bugs: Start with a reproduction test (currently failing), then edge cases.
-For refactoring: Tests should verify existing behavior is preserved.
--->
+<!-- For bugs: start with reproduction test. For refactoring: verify existing behavior preserved. -->
 
 ### Reproduction Tests
 
-<!--
-For bugs: Tests that reproduce the issue (will fail initially)
--->
-
 - Test name - Description (unit/integration/e2e)
     - **Given**: Setup/preconditions
     - **When**: Action/trigger
     - **Then**: Expected outcome
 
 ### Edge Cases
 
-<!--
-Related edge cases that should also be tested
--->
-
 - Test name - Description (unit/integration/e2e)
     - **Given**: Setup/preconditions
     - **When**: Action/trigger
     - **Then**: Expected outcome
 
 ### Regression Tests
 
-<!--
-Tests to ensure related functionality isn't broken
--->
-
 - Test name - Description (unit/integration/e2e)
     - **Given**: Setup/preconditions
     - **When**: Action/trigger
     - **Then**: Expected outcome
 
 ## Notes
 
-<!--
-Track observations during testing:
-- Unexpected behaviors discovered
-- Additional edge cases found
-- Test failures and resolutions
--->
+<!-- Track unexpected behaviors, additional edge cases found, test failures and resolutions. -->

openspec/schemas/tdd/templates/proposal.md

@@ -1,35 +1,15 @@
 ## Why
 
-<!--
-For bugs: What's broken? What's the observed vs. expected behavior?
-For refactoring: What problem does current code have? Tech debt, maintainability, performance?
-
-This is for FIXES and REFACTORING. For new features, use spec-driven schema instead.
--->
+<!-- For bugs: observed vs expected behavior. For refactoring: tech debt or maintainability issue. -->
 
 ## Root Cause
 
-<!--
-For bugs: Technical reason for the bug (if known).
-For refactoring: What makes the current code problematic?
--->
+<!-- Technical reason for the bug or what makes current code problematic. -->
 
 ## What Changes
 
-<!--
-Be specific about what will be fixed or refactored.
-- Which files/components are affected?
-- What code structure changes?
-- Any behavior changes? (Mark breaking changes with **BREAKING**)
-
-For refactoring: behavior changes should be minimal or zero.
--->
+<!-- Which files/components affected? Mark breaking changes with **BREAKING**. -->
 
 ## Impact
 
-<!--
-Who/what is affected by this change?
-- Affected code, APIs, users, or systems
-- Breaking changes? Migration needed?
-- Test coverage needed?
--->
+<!-- Affected code, APIs, users. Breaking changes? Migration needed? -->

openspec/schemas/tdd/templates/tasks.md

@@ -1,48 +1,33 @@
 ## 1. Test Setup
 
-<!--
-RED phase: Write failing tests first
--->
+<!-- RED: Write failing tests first -->
 
 - [ ] 1.1 Write failing test for main issue
 - [ ] 1.2 Add edge case tests
 - [ ] 1.3 Add regression tests for related functionality
 
 ## 2. Implementation
 
-<!--
-GREEN phase: Make tests pass with minimal code
--->
+<!-- GREEN: Make tests pass with minimal code -->
 
 - [ ] 2.1 Fix core issue (make main test pass)
 - [ ] 2.2 Handle edge cases (make edge tests pass)
 - [ ] 2.3 Verify no regressions
 
 ## 3. Refactoring
 
-<!--
-REFACTOR phase: Clean up while keeping tests green
--->
+<!-- REFACTOR: Clean up while keeping tests green -->
 
 - [ ] 3.1 Clean up implementation
 - [ ] 3.2 Extract common logic/improve structure
 - [ ] 3.3 Remove duplication
 
 ## 4. Verification
 
-<!--
-Final checks before completing
--->
-
 - [ ] 4.1 All tests passing (including new tests)
 - [ ] 4.2 Full test suite passes (no regressions)
 - [ ] 4.3 Code review ready (clean, documented)
 
 ## Notes
 
-<!--
-Track TDD cycle observations:
-- Test failures and what they revealed
-- Refactoring decisions made
-- Blockers encountered and resolutions
--->
+<!-- Track test failures, refactoring decisions, blockers. -->