Worker Card Template for Delegated Coding Tasks
SEO Slots
| Slot | Value |
|---|---|
| seo_title | Worker Card Template for Delegated Coding Tasks |
| meta_description | Use a worker card template to define scope, allowed files, inputs, constraints, done evidence, and handoff notes before assigning coding work. |
| slug | worker-card-template |
| primary_query | worker card template |
| secondary_queries | worker card template, worker card template checklist, worker card template template |
| search_intent | operational checklist |
| canonical_path | /resources/claude-code-ops-cards-blog/worker-card-template/ |
| og_title | Worker Card Template for Delegated Coding Tasks |
| og_description | Use a worker card template to define scope, allowed files, inputs, constraints, done evidence, and handoff notes before assigning coding work. |
Search Intent
operational checklist. The article must answer the reader's operational question before any commercial route appears.
Reader Artifact
Reusable checklist, table, or runbook from the article body. This artifact is the reason the article can be saved, cited, or reused by an operator.
Internal Links
- Hub: /resources/claude-code-ops-cards-blog/
- Related article: /resources/claude-code-ops-cards-blog/review-card-rubric/
- Related article: /resources/claude-code-ops-cards-blog/pm-integration-handoff/
- Related article: /resources/claude-code-ops-cards-blog/done-evidence-ledger/
- Related article: /resources/claude-code-ops-cards-blog/handoff-patterns-template-pack/
- Tool/service route: /services/diagnostic-sprint/
Structured Data
Recommended schema: Article, BreadcrumbList. Keep BreadcrumbList aligned with /resources/claude-code-ops-cards-blog/worker-card-template/. Do not add Product, Offer, Review, Rating, or FAQPage schema for this wave unless a later approved public page visibly supports it.
CTA Route
Primary route: /services/diagnostic-sprint/.
CTA label: Use the related checklist or diagnostic route.
CTA family: diagnostic_sprint.
Use this route only after the article artifact has clarified the next operational step. Public forms, accounts, and payments are intentionally not part of this resource page.
The CTA stays measured and specific, with no public payment or account route on this page.
Measurement
| Event | Name |
|---|---|
| event_view_article | view_article_claude_code_ops_cards_blog_worker_card_template |
| event_click_artifact | click_artifact_claude_code_ops_cards_blog_worker_card_template |
| event_click_cta | click_cta_claude_code_ops_cards_blog_worker_card_template |
| utm_policy | No UTM on internal links; campaign UTMs only during approved external distribution. |
Public-Preflight NG Items
- Fake client proof, fake metrics, fake awards, or guaranteed outcomes.
- Public account, form, payment, repo, domain, or outreach route before checks pass.
- Unapproved cross-brand, unrelated monetization, or off-topic trust route.
- Unsupported claims about SEO, ranking, revenue, or tool behavior.
- Machine-like slug, broken internal link, missing schema plan, or missing measurement slot.
A loose instruction tells a worker what the requester hopes will happen. A worker card tells the worker what route to follow, which files are safe to touch, what evidence is required, and what not to do.
The difference matters most when multiple people or agents are active. Without a card, a worker may expand the assignment, edit adjacent files, skip required reading, or return a confident summary without proof. A worker card turns the assignment into a reviewable unit.
Worker Card Field Guide
| Field | What to write | Bad version | Good version |
|---|---|---|---|
| Business goal | The operational outcome | Improve docs | Prepare local publish pack for PM review |
| Primary route | The work lane | Content stuff | P03 pack / Implementation Sprint / template product |
| Allowed write scope | Exact folder or file set | This repo | resources/example-pack/ only |
| Read-first files | Required context | Existing examples | Standard type file and three named examples |
| Explicit exclusions | Actions not allowed | Be careful | No public write, no account, no payment, no external sending |
| Done evidence | Proof expected | Tell me when done | File list, checklist pass, slot scan, schema scan |
| Handoff note | Next reviewer action | Done | Ready for PM review; unresolved items: none |
Minimum Card For A Safe Coding Assignment
Use this shorter version when the work is small:
Goal:
Read first:
Write scope:
Do not touch:
Required files:
Acceptance checks:
Report back with:The card should be short enough to use, but strict enough that a reviewer can reject work that crossed scope or skipped evidence.
Reviewable Done Criteria
A worker card is reviewable when it answers these questions:
| Question | Pass condition |
|---|---|
| What is the exact output? | Named files, sections, commands, or artifacts |
| What is off limits? | Public actions and unrelated file areas are excluded |
| What must be read first? | The source of truth is named |
| What counts as done? | Evidence is listed before work starts |
| Who accepts it? | The reviewer or PM route is clear |
Natural CTA
Copy the template before assigning the next delegated coding task. If a team needs the template converted into a repeatable card pack with routes, review states, and evidence slots, the P03 ops card pack route can prepare the assets for an Implementation Sprint when scope and evidence are clear.