#Why IntLoom?

A development task often contains more than a model response: clarify requirements, agree on a design, change files, run checks, and evaluate the evidence. Keeping those activities in an explicit Workflow gives each step an owner, an input, and a route to the next step.

#What IntLoom provides

• Explicit process: stages, steps, and outcomes define how work advances or returns for revision.
• Human decisions: Code asks questions or requests confirmation; answers continue the same Run.
• Declared capabilities: each Agent receives the Tools, Skills, and output Schema assigned to its Step.
• Retained results: Artifacts represent current formal outputs; Records preserve appended business evidence.
• Several interfaces: CMD, TUI, and MCP connect to one project Service.

Intent Workflow applies these mechanisms to software development. Requirements and design are confirmed before implementation, and validation retains findings and evidence.

#When to use it

Use IntLoom when the task benefits from a repeatable process, explicit decisions, local project operations, or results that can be inspected afterward. A short isolated question may need no Workflow.

A completed Run means the Workflow reached its declared end. Assess the saved report and checks to determine whether the delivered work meets your goal. See Intent results.