evolving-requirements-orchestration

What problem does it solve?

Orchestrate changing requirements without task sprawl by reconciling new asks against the active epic/spec, updating the source-of-truth brief before task edits, applying supersession precedence for newer approved requirements, deciding when to edit vs split vs create net-new tasks, and handling ambiguous founder requests with a decision-first decomposition flow.

Core Features & Use Cases

• Decision-first ambiguity loop to decompose vagueness into concrete questions.
• Supersession-aware routing to canonical briefs (Notion) and execution tasks (Mission Control).
• Flexible task mutation: edit, split, or create net-new tasks while preserving provenance.
• Guardrails to prevent sprawl: avoid duplicate tasks, assign clear owners, and link to canonical briefs.
• Use Case: Modify an active epic when a founder request changes scope, updating the source-of-truth and task tree accordingly.

Quick Start

Apply the evolving-requirements-orchestration process to reconcile new asks against the active brief and update the source-of-truth before editing tasks.