Repository navigation
Release: v2.2.5
What's Changed
Workflow changes apply across English, Japanese, and Simplified Chinese.
- Requirements, outcomes, and scope are described by their source instead of as "confirmed".
confirmed_requirement_contextis renamed torequirement_context. - Evidence from the first codebase analysis can reopen a requirement once when the requirements stop did not already present it.
- requirement-analyzer returns scope and cost evidence only.
- Work Plan tasks are limited to repository work. Unset quality levels are selected at the lowest sufficient level and shown at ADR and Design approval.
- Reverse engineering uses the unit inventory as its coverage baseline and records capabilities without routes in
otherEntryPoints. - design-sync reports only incompatible obligations for the same shared entity.
- Fixed counts, size thresholds, and the Rule of Three are replaced by decision-relevance rules and review signals.
- Skill optimization checks that required context is available where it is used, that applying or checking a rule keeps its treatment of missing evidence, and that a modification review covers the sources and uses of changed information. skill-creator's BP-001 exception now matches skill-optimization.