# Work Map

> Use when a multi-session effort needs one durable, curated route linking its specification and work items. Not for live status, ownership, dependencies, user gates or session handoffs; use the project's work tracker and session.

- **Type:** Skill
- **Install:** `agentstack add skill-mblauberg-provenant-work-map`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [mblauberg](https://agentstack.voostack.com/s/mblauberg)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [mblauberg](https://github.com/mblauberg)
- **Source:** https://github.com/mblauberg/provenant/tree/main/skills/work-map

## Install

```sh
agentstack add skill-mblauberg-provenant-work-map
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# work-map: the map for multi-session efforts

A `session` handoff carries one session's baton. Across many sessions or agents,
the work map preserves the stable route: one file per effort, read for durable
orientation and changed only when that route changes.

The project's work tracker owns live work state. In Provenant, GitHub issues
own the current owner, dependencies and user gates, while Project Status owns
workflow state. An effort map links those owners and never restates current
status, owner, dependencies or user gates.

## The map file

Use the project's canonical effort file. If no owner exists, propose
`docs/efforts/EFFORT-.md` only when project-write authority allows it;
otherwise return the map without writing. Structure:

```markdown
# EFFORT: 

## Destination
What the route is intended to deliver. Link the owning specification.

## Route
- [Programme issue](https://example.invalid/issues/1)
- [Related delivery](https://example.invalid/pull/2)

## Invariants
- [Governing decision](https://example.invalid/decisions/1)
```

## Rules

- **Link, never restate live work state.** Do not add status fields, task
  checkboxes, completion claims, owner names, dependencies, blockers or user
  gates. Readers follow the linked issue and its Project Status field.
- **Route entries are links, not task summaries.** Stable grouping and ordering
  are allowed; issue and pull-request prose carries changing detail.
- **Resume order:** project state file → issue and Project Status → this map for
  route context → the claimed session handoff only. Never reconstruct the route
  from transcripts or piled-up handoffs.
- **Handoffs stay temporary.** They carry continuity for an active session or
  run, are not linked as route state, and are removed or archived when consumed.
- **One map writer.** Parallel workers write namespaced continuity artifacts;
  one chair updates the shared route after checking the tracker.
- Archive a route map under the project's archival policy only when the
  owning issue records that disposition.
- Validate an authored map with
  `scripts/validate_work_map.py ` before handoff.

## Red flags

- `Status:`, task checkboxes or an "Updated" freshness claim → delete them and
  link the work tracker.
- Map restates a specification, decision or issue → link, don't copy.
- A handoff appears as route state → keep it in the temporary continuity layer.
- Re-planning changes accepted scope → return to `scope`, then update stable
  route links after the owning issue records the decision.

## Adapter-absent path

When GitHub is unavailable, use the project's designated canonical work
tracker; a project with no tracker names one canonical work-state owner in
its state file before any route map links it. Console and Herdr remain
optional. The portable
[effort-map artifact](portable-workflow.v1.json) records curated route links;
it never becomes live task truth.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [mblauberg](https://github.com/mblauberg)
- **Source:** [mblauberg/provenant](https://github.com/mblauberg/provenant)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-mblauberg-provenant-work-map
- Seller: https://agentstack.voostack.com/s/mblauberg
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.