knot-design

Design idempotent Knot looms and knots for convergent automation workflows.

3|Updated Jun 3, 2026

Search Tags:#automation #workflow #design #idempotency #loop #loom #knot

Ready to run

npx skills add https://github.com/HaydenDekker/knot --skill knot-design

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: knot-design
Source: https://github.com/HaydenDekker/knot/tree/main/.agents/skills/knot-design
Command: npx skills add https://github.com/HaydenDekker/knot --skill knot-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides engineers to design looms and knots for Knot with clear boundaries, idempotent behavior, and robust loop handling, preventing divergent iterations and unclear responsibilities.

Core Features & Use Cases

Idempotent knot design principles that ensure repeated runs produce no additional changes.
Clear naming conventions and domain responsibilities to avoid duplicate work and misrouted data flows.
Step-by-step guidance for planning data flows, naming, goal setting, loom placement, and loop health checks.
Use Case: when planning a new loom or evaluating knot boundaries in a live project.

Quick Start

Draft a new knot design by outlining its data flow, naming, goals, and loom placement using the provided step-by-step guide.

Frequently Asked Questions about knot-design

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

FAQPage Schema

How do I design idempotent automation workflows with safe loop convergence?▼

Idempotent automation workflows are designed by establishing clear knot boundaries, data-flow definitions, and authority semantics so repeated loop iterations produce no additional changes. This ensures safe, convergent behavior by documenting expected loop convergence in tie-off records.

What is a knot loom and when do I need one for workflow automation?▼

A knot loom is an architectural structure for organizing automation workflows with clear domain responsibilities and naming conventions. You need one when planning new automation loops or evaluating knot boundaries to prevent divergent iterations and misrouted data flows.

How do I plan data flows and set goals for a new knot loom?▼

Plan data flows and set goals by following step-by-step guidance to outline naming conventions, domain responsibilities, loom placement, and loop health checks. This process defines data-flow definitions and authority semantics to document expected convergence behavior.

Why does my automation loop diverge and produce duplicate changes on repeated runs?▼

Automation loops diverge when knot boundaries lack idempotent design principles and clear authority semantics. Diagnosing loop behaviour by reviewing data-flow definitions and tie-off records ensures repeated runs converge safely without producing additional changes.

Can I use this approach to review knot boundaries in a live automation project?▼

Reviewing knot boundaries in a live project is supported by diagnosing loop behaviour and checking loop health. The process enforces goals, data-flow definitions, and observation semantics in tie-off records to document expected convergence across planning and architecture domains.