Name: work
Author: yldio

Imported from yldio/sdlc (skills/work/SKILL.md). Install upstream with npx skills add yldio/sdlc --skill work. Copyright stays with the author.

/yld:work

Execute a planned or well-described piece of work. The goal is a finished change that already meets the YLD bar, not one that passes review on the second try.

As you implement:

Follow what exists. Mirror the codebase's established patterns for this kind of work before inventing your own (skills/standards/references/pattern-consistency.md).
Test as you go. Write a meaningful test for each behaviour when you add it, not at the end — one that fails if the behaviour breaks (skills/standards/references/test-quality.md, coverage.md).
Handle edges and failures. Write the failure path for anything that can fail, and the boundaries of each input (error-handling.md, edge-cases.md).
Keep the change focused. One concern; if it is growing into several, split it (pr-size.md).

When the work is done it should pass /yld:review with nothing to flag. Run that before opening a PR.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Install work and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "yldio-sdlc-work", "kind": "skill", "name": "work", "description": "Implement against a plan or a clear request with YLD discipline — follow the codebase's existing patterns, and write meaningful tests for new behaviour as you go, not after.", "publisher": "yldio", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Implement against a plan or a clear request with YLD discipline — follow the codebase's existing patterns, and write meaningful tests for new behaviour as you go, not after." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/yldio/sdlc", "path": "skills/work/SKILL.md", "ref": "06c11f6440d822497ed2b9bd777e794a532141f0", "url": "https://github.com/yldio/sdlc/blob/06c11f6440d822497ed2b9bd777e794a532141f0/skills/work/SKILL.md", "key": "yldio/sdlc/skills/work/SKILL.md" } }, "instructions": "# /yld:work\n\nExecute a planned or well-described piece of work. The goal is a finished change\nthat already meets the YLD bar, not one that passes review on the second try.\n\nAs you implement:\n\n- **Follow what exists.** Mirror the codebase's established patterns for this kind\n of work before inventing your own\n (`skills/standards/references/pattern-consistency.md`).\n- **Test as you go.** Write a meaningful test for each behaviour when you add it,\n not at the end — one that fails if the behaviour breaks\n (`skills/standards/references/test-quality.md`, `coverage.md`).\n- **Handle edges and fail", "cost": { "context_tokens": 234 } }

work

About

/yld:work

Use it

Install work and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews