tacigent-stage-intake

To convert wizard input into a structured intent contract, you provide your initial RunSpec to stabilize and categorize the request. The skill applies method framing to generate a typed contract, interpretation ledgers, and method artifacts without overwriting raw user input.

A typed intent contract is a structured interpretation of natural-language wizard requests that ensures deterministic handoff to downstream processing stages. It stabilizes the RunSpec and captures interpretations in ledgers to guide subsequent actions.

You start stage-based intake workflows by supplying your initial RunSpec directly. The skill processes the request using diff-first interpretation to produce an intake plan and automatically invokes the next stage for continued processing.

Yes, you can use lightweight method framing to prepare your RunSpec for downstream stages. This approach ensures the RunSpec is stabilized and categorized into interpretable artifacts before any further stage invocation occurs.

Downstream stage invocation requires an intake method plan because it ensures deterministic handoff by recording necessary continuations or hard blocks. The plan stabilizes the RunSpec and creates interpretation ledgers to guide subsequent processing.

You should not use diff-first interpretation for intent framing when external constraints create hard blocks that prevent stage progression. The process records these limitations in artifacts to halt downstream invocation when requirements are not met.