CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

ainativedev/aidevcon-2026-nyc

AI Native DevCon 2026 New York — practical agent skills grounded in conference talks

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

application-template.mdskills/talk-debois-concurrent-delivery/references/

Shared-factory concurrency worksheet

This is Tessl's recommended application of Debois's talk. Fill it for two or more real requests that may interact. Do not assume that a clean Git merge makes them compatible.

Concurrent work map

Request and intentInitiatorClaimed code or domainShared stateExpected completion

Record contradictions in desired behavior separately from overlapping files. Include maintenance work and incident fixes in the queue. Identify whether the pressure is active execution, waiting, repeated testing, or human review.

Isolation contract

State the code revision, test definitions, data snapshot, API assumptions, configuration, and external context for each run. Mark what remains live and can change. Explain how a changed assumption invalidates earlier evidence. A worktree alone does not freeze the wider environment.

Coordination and integration

Describe the signal when an agent expands its scope and the response to overlap: wait, transfer, renegotiate, or revise the plan. Name the authority for resolving incompatible product intent.

Define a combined-state behavior check. For example, if one request changes monetary units while another adds invoice arithmetic, verify the agreed units across the complete calculation. This example follows the talk's semantic-conflict discussion; use the team's real invariant.

If proposing grouped or speculative merges, record the exact combination tested, conditions that invalidate it, and a fallback when the group fails. Keep the final change understandable to its reviewer.

Human decisions and recovery

List information the agent can retrieve and decisions it must surface. Provide concise options with consequences. Record accepted decisions with rationale and scope in the team's chosen location; the talk does not settle one universal storage system.

State the consequence of a bad change, required checks, release routing, and how code, data, and external side effects could be recovered. Finish with factory ownership, role-appropriate status updates, and one bottleneck measure to compare before and after the proposed change.

skills

talk-debois-concurrent-delivery

tile.json