Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
The mandatory decision tree at `content/06-decision-tree.xml` Decides whether to plot the chart weekly (graph + ≥3 teams + weekly cadence + PM), block (no graph), or skip (single team / sparse cadence
Imported from faionfaion/faion-network (skills/faion/knowledge/pm/program-dependency-aging-chart-recipe/AGENTS.md). Install upstream with npx skills add faionfaion/faion-network --skill program-dependency-aging-chart-recipe. Copyright stays with the author.
Program Dependency Aging Chart Recipe
Summary
One-sentence: Builds a program-dependency aging chart (count-of-blocked-tasks vs days-since-dependency-opened) so program managers spot dependency rot before milestones slip.
One-paragraph: Builds a program-dependency aging chart (count-of-blocked-tasks vs days-since-dependency-opened) so program managers spot dependency rot before milestones slip. The methodology is anchored to a single named consumer (a PM, EM, portfolio owner, or downstream agent) and a fixed-shape artefact that downstream review can sign off without re-deriving reasoning. Inputs are explicit, evidence is anchored, and the artefact carries version, owner, and last_reviewed so it remains a living operating tool rather than folklore. Outputs that fail the contract are rejected at validation time, not at executive review.
Ефективно для: Програмному PM-у — щоб залежність, яка 'тихо лежить' три тижні, не зривала milestone у 6-му.
Applies If (ALL must hold)
Program involves ≥3 teams with documented cross-team dependencies.
A typed dependency graph exists (or the dependency-graph-reasoning methodology runs).
Weekly checkpoint cadence is in place.
A named program PM owns the chart.
Skip If (ANY kills it)
Single-team project — aging chart adds no signal.
No dependency graph — chart has nothing to age.
Cadence is less than monthly — aging signal will be too late.
Aging chart artefact skeleton: chart image link + table of edges by age band + remediation actions per band.
templates/skeleton.md
Aging chart artefact skeleton: chart image link + table of edges by age band + remediation actions per band. Generated from templates/skeleton.md.j2 by tpl-jinja --migrate; do not hand-edit.
templates/header.yaml
Frontmatter contract: owner, version, last_reviewed for the produced artefact.
Validate produced artefact against the JSON Schema in 02-output-contract.xml.
Pre-merge and on every artefact refresh.
Related
[[dependency-graph-reasoning]]
[[okr-cascade-team-to-company]]
[[portfolio-evm-rollup-method]]
Decision tree
The mandatory decision tree at content/06-decision-tree.xml Decides whether to plot the chart weekly (graph + ≥3 teams + weekly cadence + PM), block (no graph), or skip (single team / sparse cadence). Run before the chart is added to the program ritual.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
yaml
targets:
- https://api.opensmartroute.ai/api/v1/registry/faionfaion-faion-network-program-dependency-aging-chart-recipe/manifest # or paste the manifest below
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
{
"ocm": "1",
"id": "faionfaion-faion-network-program-dependency-aging-chart-recipe",
"kind": "skill",
"name": "program-dependency-aging-chart-recipe",
"description": "The mandatory decision tree at `content/06-decision-tree.xml` Decides whether to plot the chart weekly (graph + ≥3 teams + weekly cadence + PM), block (no graph), or skip (single team / sparse cadence). Run before the chart is added to the program ritual.",
"publisher": "faionfaion",
"version": "1.0.0",
"capabilities": {
"domains": [
"data_analysis",
"creative"
],
"tags": [
"skill-md",
"github-agents"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"The mandatory decision tree at `content/06-decision-tree.xml` Decides whether to plot the chart weekly (graph + ≥3 teams + weekly cadence + PM), block (no graph), or skip (single team / sparse cadence). Run before the chart is added to the program ritual."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-agents",
"repository": "https://github.com/faionfaion/faion-network",
"path": "skills/faion/knowledge/pm/program-dependency-aging-chart-recipe/AGENTS.md",
"ref": "8e31684537e64d45c75264b1e0a2384f9b024a34",
"url": "https://github.com/faionfaion/faion-network/blob/8e31684537e64d45c75264b1e0a2384f9b024a34/skills/faion/knowledge/pm/program-dependency-aging-chart-recipe/AGENTS.md",
"key": "faionfaion/faion-network/skills/faion/knowledge/pm/program-dependency-aging-chart-recipe/AGENTS.md"
}
},
"instructions": "# Program Dependency Aging Chart Recipe\n\n## Summary\n\n**One-sentence:** Builds a program-dependency aging chart (count-of-blocked-tasks vs days-since-dependency-opened) so program managers spot dependency rot before milestones slip.\n\n**One-paragraph:** Builds a program-dependency aging chart (count-of-blocked-tasks vs days-since-dependency-opened) so program managers spot dependency rot before milestones slip. The methodology is anchored to a single named consumer (a PM, EM, portfolio owner, or downstream agent) and a fixed-shape artefact that downstream review can sign off without re-deriving ",
"cost": {
"context_tokens": 1039
}
}
Fetch it by URL: GET /api/v1/registry/faionfaion-faion-network-program-dependency-aging-chart-recipe/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.
