Skip to content
Agentmart
Submit a tool

source-work-order-governed

Governed-runtime source adapter that reads Work Orders from planner JSON artifacts and maps them to NormalizedDeliveryContext for implement handoff.

Skill by TribalScale

IndexedApache-2.0★ 2
Write a review

Chalk Labs

Need help deploying source-work-order-governed?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/tribalscale-source-work-order-governed

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Governed-runtime source adapter that reads Work Orders from planner JSON artifacts and maps them to NormalizedDeliveryContext for implement handoff.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/source-work-order-governed

What's inside

Skill name
source-work-order-governed
Description
Governed-runtime source adapter that reads Work Orders from planner JSON artifacts and maps them to NormalizedDeliveryContext for implement handoff.
License
Apache-2.0
Instructions
75 lines in SKILL.md · view on GitHub

Files (2)

  • SKILL.md
  • json-handoff-contract.md

SKILL.md (first lines)

# Source: Work Order (Governed Runtime)

JSON handoff adapter for governed delivery. Reads Work Orders from planner task
output JSON — not from `docs/planner/**` files.

Use the filesystem adapter (`source-work-order`) for local runs with on-disk planner output.

## When to Run

Workflow step: `prepare_work_order_delivery` in `work_orders_from_prd`.

## Inputs

```json
{
  "approved_prd": { "...": "..." },
  "planner_output": { "summary": "...", "artifacts": { ... }, "work_order_ids": [...] },
  "planner_artifacts": {
    "work_orders_markdown": "# WO-001 ...",
    "context_graph_markdown": "# Context Graph ...",
    "execution_phases_markdown": "# Execution Phases ..."
  }
}
```

## Required Reads

1. `input.planner_artifacts.work_orders_markdown`
2. `input.planner_artifacts.context_graph_markdown`
3. `input.planner_artifacts.execution_phases_markdown`
4. `input.planner_output.work_order_ids` if present

If planner artifacts are missing, stop and report in JSON `warnings` — do not look for filesystem paths.

## Output Contract

Return JSON:

```json
{
  "summary": "Prepared WO-001 for implement handoff.",
  "planner_complete": true,
  "work_order_ids": ["WO-001", "WO-002"],
  "next_work_order_id": "WO-001",
  "work_orders_handoff": true,
  "work_order_ref": "WO-001",
  "confidence": "high",
  "warnings": [],
  "follow_up_needed": false
}
```

See `json-handoff-contract.md` for field rules.

## Dependency Gate

From `context_graph_markdown` Depends-on links:

1. Read `input.completed_work_order_ids` if provided (program artifacts).
2. If a dependency WO is not in completed list, set `follow_up_needed: true` and report blockers in `warnings`.
3. Select `next_work_order_id` as the first WO in `execution_phases_markdown` order that is not completed and has satisfied dependencies.

## Mapping Rules

| Planner content | Output field |
|---|---|
| First ready WO id | `next_work_order_id` |
| All WO ids | `work_order_ids` |
| WO id string | `work_order_ref` |
| Handoff ready | `work_orders_handoff: true` |
| Planner done | `planner_complete: true` |

Do not return an action plan. Return the handoff fields above.

From TribalScale/ts-harness, Apache-2.0.

More from TribalScale/ts-harness

Signals

Stars
2
Forks
0
Open issues
0
Last commit (this folder)
Oct 17, 2026 (14 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
Apache-2.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from TribalScale

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get source-work-order-governed running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying source-work-order-governed?

CallGet help
Cite this page

source-work-order-governed skill. Agent Mart. https://agentmart.dev/skills/tribalscale-source-work-order-governed (last updated 2026-10-24)