Skip to content

Bootstrap Workflow

Triggered by: meta-routing when a user request is greenfield or has an unclear scope.
Intent: Prevent scope creep and vague requirements by forcing a formal extraction and ambiguity detection phase before any code is written.

  • req-analysis — requirements analysis
  • req-scope — scope boundary definition
  • req-ambiguity-detection — ambiguity detection
  • req-acceptance-criteria — acceptance criteria generation
{ rawInput: string; constraints?: string[] }
  • Conflicting or ambiguous requirements → loop back to user for clarification
  • Only tightly scoped, bounded requirements exit the workflow

Before scope analysis: agent-snapshot, agent-session, agent-memory

stateDiagram-v2
    [*] --> RawRequest
    RawRequest --> ScopePerception
    ScopePerception --> RequirementInterpretation
    RequirementInterpretation --> AmbiguityEvaluation
    AmbiguityEvaluation --> ConstraintCommitment
    ConstraintCommitment --> ScopeDeclaration
    ScopeDeclaration --> AcceptanceCriteriaGeneration
    AcceptanceCriteriaGeneration --> ScopeReflection

    ScopeReflection --> ScopePerception: revise scope boundary
    ScopeReflection --> RequirementInterpretation: reinterpret user intent
    ScopeReflection --> ConstraintCommitment: reaffirm boundaries
    ScopeReflection --> [*]: scope locked and verified

design · implement · research · review · plan · debug · refactor · testing · orchestrate · govern · enterprise · physics-analysis