Files
tom_analysis_agent/skills/operating-guide/assets/guide-template.md

59 lines
1.9 KiB
Markdown

# Operating model guide: <the solution, in a few words>
## Summary
<Written by the packager. One or two short paragraphs for the person who will run
the solution: what is operated, who operates it and how the work is divided between
the Parties, during which hours, and what they should look at first. No number of
people, no cost and no count: the key figures are set under this paragraph from the
data.>
### Key figures
<Written by code: what is operated, the hours, the Capabilities, people and cost
with the rate card's version, the scenario walk-throughs, and the findings.>
## Business outcomes
<Written by code: each business outcome the customer stated, with the Measures
that show it is served, their layer and framework, the Capability that takes each,
and the Role answerable for it.>
## What is operated
<Written by code from the operating scope: the Items, the Conditions that must be
kept true, and anything known to be at risk when operations begin.>
## Operational requirements
<Written by code: each requirement, its kind, and what it comes from.>
## Capabilities
<Written by code: each Capability, the requirements it serves, the Items it covers,
its hours and its effort.>
## Who does what
<Written by code: the Roles and their Parties, and the responsibility matrix.>
## Staffing and cost
<Written by code from the rate card: people and cost for each Role and in total,
the budget when one was stated, the rate card's version, and the conversion rate.>
## Validation
<Written by code: the verdict on each Check with its evidence, and each scenario
walk-through with the path traced for it.>
## Findings and open questions
<Written by code: every finding, everything assumed for the customer, and
everything still unknown.>
## Sources
<Written by code: the frameworks the Capabilities draw on, cited by framework and
by the name of the part, and whether those references have been checked.>