Work across your whole ProvenMap workspace — explore the board graph, review insights, and author work items from Claude Cowork, Claude Code, or Codex. Connects to the ProvenMap MCP server; writes gather in your working copy, and committing generates a reviewable plan (one work item per governed app).
Plugin pmap-workspace in provenmap/pmap-codex. Commands read from the repo's manifest — today.
This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.
adr-adoptionHow to adopt an architecture decision (ADR) into ProvenMap and measure the estate against it — the /adopt-adr arc. Use when the org has made a decision, standard, or policy that boards should be governed by and checked against. Key capabilities: ADR normalization, blast-radius sweep per aspect famil
app-readinessTake a new app from placed to build-ready — the readiness bar, the spec grill that lands sequenced work items, and skill selection. Use when a convert_node_to_app ran with observationType 'new_app', when /prepare-app runs, or when the architect asks to "prepare/spec the app", "get it ready to build"
architect-coreThe architect workbench identity — how to work over the ProvenMap MCP server as the board orchestrator brain. Use in every architect session, before any board, work item, or insight work. Key capabilities: role and capabilities, the token scope model and write fence, board taxonomy and routing rules
board-initBootstrap an existing-but-empty board below root into an implementable app design. Use when /board meets an empty app board (bound governing/reference, pre-first-push, or unbound with an app-archetype owner node) or an empty plain layer, or when /start routes a "shape/prepare/initialize this empty b
board-readingHow to orient on and evolve a ProvenMap board over MCP — read the layered graph, analyze it, and make governed diagram edits. Use when exploring a board, answering architecture questions, assessing quality, or adding/updating/removing nodes and edges. Key capabilities: orientation sequence, board-cl
board-stylingHow to style a ProvenMap board so it reads professionally — composition, size hierarchy and icons first, semantic tokens sparingly. Use when authoring or beautifying any board (inline in setup/new-app/board writes, or via /style-board). Covers the signals→plan→validate→apply pipeline and the three a
discover-authoringHow /discover turns a scored graph reading into insights and context boards worth showing — the plan and its menu, the recommended set, the briefs, the authoring agents, the push order and the report. Use when running /discover, when authoring one discover brief, or when reading a discover plan or l
insight-writingHow to write the words of a ProvenMap insight or context board — the one contract for every flow that authors them. Use whenever you fill an InsightDraft's name, insight, impact, advice or trail notes, a push's info line, or a context board's name, description and node notes (/insights, /discover, a
insights-reviewHow to review ProvenMap insight batches and turn insights into work, how to run a structured assessment (/assess), and how to record a session analysis as a draft batch. Use when listing or reading insights, deciding what to promote to work items, running a periodic review, or capturing an architect
landscape-modelingHow to model an org's digital estate on the ProvenMap root landscape — the inception doctrine, archetype selection, and the binding handoff. Use when bootstrapping an empty workspace (/setup), placing a new system (/new-app), or editing the root landscape in a /board session. Key capabilities: the m
outcomeHow every ProvenMap command closes — the Outcome you write from the script's brief. Use at the last step of any command or routed workflow, when the step says "Done · Left · Next" or names --brief. Covers the fixed shape, the eight writing rules with examples, how to read a brief (state, gates, cand
playbook-authoringHow to author a ProvenMap playbook — an org-level guided track for one job, composed from steps the platform already watches. Use when the architect wants to turn a job ("replace the stale doc", "run our ADR process", "onboard a new team to the map") into a playbook others in the org can start, or w
playbook-runningHow to RUN a ProvenMap playbook from the terminal — pull the playbook's compiled skill file, work its steps in order through the platform's MCP tools, and let the server prove each one. Use when the architect wants a playbook done rather than authored ("run the migration playbook", "walk me through
report-bugHow to draft a ProvenMap bug report that describes the problem without naming the user's project. Use at /report-bug's drafting step. Covers what to keep (the scenario), what never goes in (the user's names and content), the report template, and how to generalise a failure.
work-items-authoringHow to author, anchor, and manage ProvenMap work items — the living specs that connect architecture decisions to delivery. Use when creating work items, authoring requirements against a board, managing the work item queue (transition, assign, delete), or turning insights and board changes into work.
/pmap-workspace:adopt-adrAuthor · WRITE-CAPABLE: Adopt an architecture decision — normalize it, measure the estate against it, land the decision record plus per-app remediation work items
/pmap-workspace:adrAuthor · WRITE-CAPABLE: Write an architecture decision (ADR) — grill the context, options and consequences, anchor it where it applies, land it as a Decision work item and propose it
/pmap-workspace:archetypesAuthor · WRITE-CAPABLE: Review the archetype catalogue for a board kind, scan shared documents for gaps, and submit proposals for admin review
/pmap-workspace:ask-boardExplore · Ask the architecture a question — get a slug-grounded answer, or a drawn context board when the answer is a subgraph
/pmap-workspace:assessReview · WRITE-CAPABLE: Run a structured architecture review — frame, sweep, defend the insights, record the batch
/pmap-workspace:author-playbookAuthor · WRITE-CAPABLE: Author a playbook — interview the job, compose steps the platform can watch, draft it for the org
/pmap-workspace:author-work-itemAuthor · WRITE-CAPABLE: Guided work item authoring — pull the surrounding context, grill the gaps, land a well-grounded draft work item
/pmap-workspace:boardExplore · Orient on a ProvenMap board and work it — explore, analyze, and make governed edits
/pmap-workspace:configureAccount · Manual MCP token setup — generate a token in ProvenMap and wire it into this host
/pmap-workspace:discoverExplore · WRITE-CAPABLE: Discover the insights and context boards worth showing across the workspace — ranked by the graph, read closely, picked by you or chosen for you, authored in parallel, recorded and drawn on the platform
/pmap-workspace:helpAccount · List all pmap-workspace commands with descriptions and the plugin version
/pmap-workspace:hubExplore · The command center, attention-first — what needs the architect, then the portfolio
/pmap-workspace:insightsReview · Review insight batches and promote reviewed insights into draft work items
/pmap-workspace:loginAccount · Sign in to ProvenMap in the browser and generate an MCP access token (no copy-paste)
/pmap-workspace:logoutAccount · Disconnect from ProvenMap — remove the stored MCP access token from this machine
/pmap-workspace:new-appAuthor · WRITE-CAPABLE: Plan a new system on the existing landscape — grill, place it, sketch its target architecture, draft its founding work item
/pmap-workspace:prepare-appAuthor · WRITE-CAPABLE: Take a new app from placed to build-ready — grill the spec into sequenced work items, choose its skills
/pmap-workspace:report-bugAccount · Draft a bug report with your project details removed, to post in the ProvenMap community or send to support
/pmap-workspace:run-playbookOperate · WRITE-CAPABLE: Run a playbook — pull its compiled skill, work its steps, let the server prove each one
/pmap-workspace:setupAuthor · WRITE-CAPABLE: Bootstrap an empty workspace — map what exists, or found a new product line: system landscape, app boards, binding handoff
/pmap-workspace:startStart here · Reads your real state and tells you what to run next — or routes any open-ended ask to the right workflow
/pmap-workspace:statusAccount · Check the ProvenMap MCP connection: endpoint, token, live probe, scope, and your working copy
/pmap-workspace:style-boardAuthor · WRITE-CAPABLE: Beautify a board — deterministic signals, a styling plan you approve, validated and applied as journaled writes
/pmap-workspace:updateAccount · Update this plugin to the latest published version
/pmap-workspace:work-itemsAuthor · WRITE-CAPABLE: List, author, and manage board work items; drafts land for in-platform review
insight-authorAuthors ONE /discover brief into its pushable payload — an insight push (evidence prose around a script-chosen trail) or a context-board payload (name, question, description and per-node notes around a script-drawn board). Dispatched by /discover, one agent per brief, in waves; never invoked for ope
provenmapconnects to: https://platform.provenmap.com/api/mcp
node "${PLUGIN_ROOT}/scripts/pmap-architect.js" --session-start --host codex
Real-time codebase architecture analysis and visualization for ProvenMap Portal. Analyzes codebases across multiple languages, detects tech stacks, identifies component relationships, and syncs to ProvenMap for collaborative architecture boards. Supports server-defined insight analysis skills.
22 skills · 25 commands · 5 agents · hooks
Renamed — this plugin is ProvenMap Workspace (pmap-workspace) now. Install pmap-workspace; your login carries over.
3 commands · hooks
Retired — grounding moved into ProvenMap Code. Install pmap-code and run /ground in this repo; its .provenmap/ state is picked up as is.
3 commands
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
1 command · 3 agents
AI-powered codebase understanding — analyze, visualize, and explain any project
9 skills · 10 agents · hooks
ADR lifecycle management — create, index, supersede, and link Architecture Decision Records to code
5 skills · 1 command · 1 agent
Editorial diagrams in your brand, as self-contained HTML and SVG. Architecture, flowcharts, sequence, state machines, ER and database schemas, timelines, swimlanes, org charts, Gantt, Wardley maps, user journeys, service blueprints, UML class, lifecycle phase maps, and charts from bar, line and scatter to Sankey, treemap and heatmap, plus many more. Redraws draw.io, Mermaid, Excalidraw and PlantUML files. Exports SVG and PNG.
1 skill · 7 commands
53 marketing skills for technical marketers and founders: CRO, copywriting, cold email, prospecting, SEO, AI SEO, paid ads, SMS, ad creative, video production, image generation, co-marketing, churn prevention, pricing, referrals, revenue operations, sales enablement, customer research, site architecture, comprehensive AARRR-structured marketing plans, public relations and earned media, offer design, event marketing and webinars, and more
53 skills
Perform AI code review on Git diffs — supports workspace changes, branch ranges, and single commits with concurrent per-file analysis, codebase search, and deep context-aware review.
2 commands
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.