requirements-extractor

To extract structured requirements from unstructured product briefs, the Skill processes raw text using bottom-up context expansion and top-down why-based inference to produce a complete Mission, Goals, Premises, and Constraints specification.

A MGPC specification is a structured requirements document defining Mission, Goals, Premises, and Constraints, which surfaces implicit constraints and includes risk assessments for each identified Premise to guide decisions.

Yes, you can generate risk assessments for premises from a raw meeting transcript by classifying the transcript input type and applying saturation outputs to drive domain disambiguation and risk-aware Premise extraction.

To identify implicit constraints in a repository or specification, apply a bottom-up context expansion method to broaden the solution space, which surfaces hidden limitations and drives the Phase 1 specification process.

The best way to converge on a fixed point for a project Mission is to apply a Phase 1 why-based recursion technique, using iterative top-down questions until the Mission statement reaches a stable, fixed definition.