Why: SpecFact planning now spans two repositories, but issue ownership, parent hierarchy, and active OpenSpec proposal scope are still partly aligned to the old monolithic repo model. This epic owns repo-boundary governance and setup work needed to keep planning coherent across specfact-cli and specfact-cli-modules.
Scope:
- cross-repo issue ownership and reassignment decisions
- hierarchy creation and maintenance across repos
- planning inventory and change-order alignment
- proposal rescoping for lean-core vs modules ownership
- setup and governance work that supports the product backlog without being product implementation itself
Why: SpecFact planning now spans two repositories, but issue ownership, parent hierarchy, and active OpenSpec proposal scope are still partly aligned to the old monolithic repo model. This epic owns repo-boundary governance and setup work needed to keep planning coherent across specfact-cli and specfact-cli-modules.
Scope: