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-re-ferre-development-platforms/references/

Team workflow and cost-evidence worksheet

This is Tessl's suggested application of Re Ferre's talk. Fill it for one team workflow rather than the whole organization at once.

Signal-to-outcome map

Record the initial signal, triage, design, build, test, release, and observation steps. Identify the owner, input, output, active work time, and waiting time at each step. Mark unmeasured time as unknown. Name the bottleneck that the proposed change will address.

Describe whether work needs to move off a laptop, gain automation, or use an identity distinct from an individual. Explain each choice independently.

Two operating problems

For enablement, describe the task-specific environment a new team member needs: relevant skills, context connections, instructions, and a small first success. Record which setup is distributed centrally and which choices still depend on individual knowledge.

For cost control, connect each run to its deliverable and acceptance evidence. Track configuration, spending, failed attempts, and rework where available. A high token bill or low usage count alone does not establish value.

Model and intent decision

State the required quality bar, candidate model or routing policy, representative evaluation tasks, and an exception condition. Do not copy illustrative costs from the talk. Explain how the team will compare total useful work, including rework, rather than choosing on token price alone.

Write the intended outcome in language that both builder and reviewer can use. List acceptance criteria and supporting evidence. Mark ambiguous product decisions. Define the particular complexity or input gap that requires clarification before implementation.

Bounded rollout

Choose one recurring task, baseline, proposed change, and observation period. Specify the evidence needed to expand it, revise it, or stop. Keep existing release authority explicit. Finish with a short decision: what the team can implement now, what remains unverified, and the smallest next measurement.

skills

talk-re-ferre-development-platforms

tile.json