Skip to content

Analysis pages from the map ​

This page is for: advisors and forward-deployed engineers.

Planned

This page describes an idea

The parts under "What exists today" are built. The playbook that makes pages is not. It is written down here so the design is clear before it is built.

The idea ​

An advisor says to their AI: "Make me a Five Forces page for this client." The AI reads the company's files through the CLI, builds one small web page with the chart on it, and opens it. Ten minutes later the advisor has something to put in front of the sponsor.

The pattern is a skill: a short set of instructions the AI follows, plus the CLI to fetch the data. The skill decides what to read, what to draw and what it must never invent.

What exists today ​

PartStatus
The company's map as Markdown files (dutygraph repo pull)Built
16 framework canvases that fill from those files, with the source files shown per box (dutygraph frameworks run)Built
Counts over time: answers, Task Cards, gaps (dutygraph stats --json)Built
Who has cards, hours per task, who holds what alone (dutygraph coverage, dutygraph gaps list)Built
A skill pack for Claude Code, installed by repo pullBuilt
A skill that turns these into a pagePlanned

Pages worth making ​

PageDrawn fromHonest limit
Porter's Five ForcesThe Five Forces canvas: research, the business model, the industry mapEach force cites its files. A force with no evidence says so.
SWOT, PESTLE, VRIOThe same canvasesAs above
Where the hours goHours per week on each Task Card, by role and teamOnly as good as the cards. Show how many people are covered.
Key-person riskTasks with one holder, weighted by hours and by how many tasks depend on themA ranking, not a prediction
Goal treeVision, goals, departments, roles and the Task Cards that serve each goalShows gaps where a goal has no work under it
Time back with agentsTask Cards marked as a fit for AI, with their hoursA range, with the assumptions on the page
Forecasts and scenariosTask Card times and how often they runNeeds low, likely and high times on the cards. Until then, label it as a sketch.

Rules for the skill ​

  1. Read before you draw. Pull the Repo and run the framework. Do not write a chart from memory of the company.
  2. Every number has a source. Each figure on the page names the file or the count it came from.
  3. Missing is shown as missing. An empty box says "not stated yet". It is never filled with a likely answer.
  4. Label what is modelled. A forecast states its assumptions on the page.
  5. One page, one question. A page answers one thing the sponsor asked.
  6. The advisor dashboardroves before the client sees it. The page is a draft until then.
  7. Client data stays local. The page is a file on the advisor's machine. Publishing it is a separate decision.

How it would be built ​

  1. Add a make-analysis-page playbook to the skill pack in cli/src/templates/dutygraph-fde/.
  2. It calls dutygraph frameworks show, dutygraph stats and dutygraph coverage for its data.
  3. It writes a single HTML file from a small set of chart templates in DutyGraph's style.
  4. It writes a sources.md beside the page that lists every file and count used.

DutyGraph. Pages label each feature Built, In review or Planned.