Files
markitect-main/guides/AUTONOMOUS_WORK_REMINDER.md
2025-10-03 03:39:43 +02:00

2.1 KiB

Autonomous Work Reminder - TDD8 Implementation

🎯 MISSION: Complete Issue #50 - Metaschema Definition

CRITICAL REMINDERS FOR AUTONOMOUS WORK:

📋 TDD8 Workflow - NEVER SKIP STEPS

  1. ISSUE - Understand requirements (Issue #50 already analyzed)
  2. TEST - Write failing tests first (RED state required)
  3. RED - Verify tests fail before implementation
  4. GREEN - Implement minimal code to pass tests
  5. REFACTOR - Clean up code while keeping tests green
  6. DOCUMENT - Update documentation and help
  7. REFINE - Polish and optimize
  8. PUBLISH - Commit and close issue

🚨 AUTONOMOUS WORK PROTOCOLS

DO NOT FORGET TO:

  • Run tests after each change to verify state
  • Commit frequently with descriptive messages
  • Update CLI help when adding new features
  • Maintain backward compatibility
  • Follow existing code patterns and conventions
  • Use proper PYTHONPATH=. for all test runs
  • Close the issue when complete using: make close-issue NUM=50

QUALITY STANDARDS:

  • All tests must pass before moving to next TDD8 step
  • Code must follow existing project conventions
  • Documentation must be comprehensive
  • CLI integration must be complete and tested

ISSUE #50 SPECIFIC REQUIREMENTS:

  • Define JSON Schema metaschema for MarkiTect extensions
  • Support heading text capture
  • Support content field instructions
  • Support outline structure representation
  • Maintain backward compatibility with existing schemas
  • Include validation rules for new features

COMPLETION CRITERIA:

  • Metaschema JSON file created and validated
  • Tests cover all metaschema features
  • Documentation explains structure and usage
  • CLI can validate schemas against metaschema
  • All existing schemas still validate correctly

🔄 WORKFLOW COMMANDS

# Start work
make tdd-start NUM=50

# Run tests
PYTHONPATH=. python3 -m pytest tests/ --tb=short -q

# Commit work
git add . && git commit -m "step: [TDD8_PHASE] description"

# Close issue when complete
make close-issue NUM=50

🎯 SUCCESS = Issue #50 completely implemented, tested, documented, and closed