evolving-requirements-orchestration

Name: evolving-requirements-orchestration
Availability: InStock
Author: spiral-app-labs

Reconcile new asks against active epics and update canonical briefs before task edits.

Updated Apr 8, 2026

Search Tags:#planning #requirements #orchestration #epics #governance #process #task-management

Ready to run

npx skills add https://github.com/spiral-app-labs/skills --skill evolving-requirements-orchestration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: evolving-requirements-orchestration
Source: https://github.com/spiral-app-labs/skills/tree/main/evolving-requirements-orchestration
Command: npx skills add https://github.com/spiral-app-labs/skills --skill evolving-requirements-orchestration

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about evolving-requirements-orchestration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I manage evolving requirements without creating task sprawl?▼

To manage evolving requirements without task sprawl, reconcile new asks against the active epic by updating the source-of-truth brief before mutating any execution tasks, applying supersession precedence for newer approved changes.

What is the best way to handle ambiguous founder requests during epic planning?▼

Handling ambiguous founder requests requires a decision-first decomposition loop that breaks vagueness into concrete questions, resolving what changed and what must be true before updating the canonical brief and routing tasks.

How do I update active epics when project scope changes?▼

Updating active epics when scope changes involves reconciling the new ask against the approved spec, updating the source-of-truth brief first, and then deciding whether to edit, split, or create net-new tasks while preserving provenance.

When should I edit an existing task versus creating a net-new task?▼

You should edit an existing task versus creating a net-new task by applying supersession precedence to newer approved requirements, evaluating the change against the canonical brief to prevent duplicate tasks and minimize task churn.

Does this requirements orchestration process integrate with Notion and Mission Control?▼

Yes, this requirements orchestration process routes canonical briefs to Notion and execution tasks to Mission Control, applying supersession-aware routing to maintain alignment between the source-of-truth and active task tree.