What's New
Redesigned SDD workflow around confirmed requirements (#5)
The Spec-Driven Development workflow is now anchored on an authoritative, persistent record of confirmed requirements, with end-to-end traceability from requirements → spec → plan → tasks.
- Persist confirmed requirement discussions in an authoritative
requirements.mdrecord with stable IDs and confirmation history - Enforce requirements-to-spec-to-plan-to-tasks traceability, deterministic feature resolution, and bounded auto-review loops
- Standardize on
YYYY-MMDD-HHMMxx-feature-nameas the only supported feature ID format across Bash, PowerShell, templates, tests, and docs - Replace fixed review-template deductions with evidence-backed findings, four-state outcomes, compatibility scoring, and separate non-scoring advisories
claude-auto-responder for unattended sessions (#3)
New standalone Python script (scripts/python/claude_auto_responder.py) that monitors Claude Code's jsonl session file and auto-responds to tool-permission prompts via tmux — enabling fully autonomous long-running sessions behind a configurable safety policy engine.
SafetyPolicyEngine,BashClassifier,TmuxSender, and health-check support- Bilingual docs (en / zh-CN) and a real-world demo report
Other
- Standardized command templates with improved clarity and added code review features
- Full pre-commit suite passing (Ruff, mypy, Bandit, Markdownlint, ShellCheck, pip-audit);
774 passed, 35 skippedon pytest
Full Changelog: v0.5.20...v0.6.0