Double dutch
Determine where a new process, branch, validation, or handoff can enter an existing workflow without breaking cadence, ordering, ownership, retries, or completion. Use only when the user explicitly invokes Double Dutch.From its SKILL.md
npx -y skills add jawsublime-byte/simon-says --skill double-dutchAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.2 KB, 195 tokens by cl100k_base, as published. Nobody here has run it
Double Dutch
Study the rhythm before jumping in.
Map the rhythm
- Identify each workflow stage, owner, input, output, timing, retry, timeout, and completion signal.
- Mark state transitions and points where work can safely pause, branch, rejoin, or roll back.
- Identify candidate insertion points.
- Reject any point that duplicates work, breaks ordering, hides failure, loses idempotency, or changes locked behavior.
- Compare remaining points by disruption, observability, recovery, and latency.
- Choose one insertion point and define its entry and exit contract.
- Verify the original workflow still completes with and without the new process.
Do not redesign the full workflow unless the user asks.
Output
Report the current rhythm, chosen insertion point, branch contract, rejoin condition, rollback path, and verification.
Completion
Finish when the new process can enter and exit without changing the established workflow contract.
What ships with it: 1 file
247 B alongside SKILL.md
agents/
- openai.yaml247 B