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-jain-verifying-intent/references/

Intent, decision, and evidence packet

This is Tessl's recommended application of Jain's framework. Complete it for one candidate change using actual session and repository evidence. Do not invent a result to fill a field.

Intent and criteria

State why the change is needed, the requested behavior, and the relevant constraints. List each acceptance criterion with its original source. Record any later amendment, the reason, and who made the decision. Distinguish accepted changes from agent proposals.

Decision ledger

DecisionAlternatives and rationaleStatusHuman call or follow-upEvidence

Include choices made during implementation, agent disagreement, review responses, and repairs after verification failures. Preserve settled decisions; they help reviewers understand the system. An agent's “acceptable risk” label is not a human acceptance record.

Scoped invariants

For each reusable rule, provide its wording, applicable change scope, verification method, source review comments, and maintenance owner. Keep opinions specific to this change separate from reusable rules.

If converting a rule to a deterministic pattern, record shadow-mode comparisons, representative matching and nonmatching examples, disagreements, and promotion criteria. A repeatable result can still be wrong.

Evidence matrix

CriterionScenarioEvidence typeCandidate revision and environmentResult or missing evidence

Choose evidence that can establish the actual behavior. Use screenshots for visible state, responses for API contracts, state or network evidence for side effects, and test runs for temporal behavior. A screenshot alone may not prove a backend side effect.

Review and ownership

Summarize settled issues, unresolved decisions, and follow-ups. State what the reviewer needs to understand and which code or artifact they should inspect if the packet is insufficient. Name rule owners and the person responsible for the change. End with the next verification or decision, preserving the team's existing merge authority.

skills

talk-jain-verifying-intent

tile.json