Skip to content
Portfolio/Capabilities

CAPABILITY 19 / 30

Packaged so it survives you

Skills, agents and guides bundled so a team can install them without a walkthrough call.

IN PRODUCTION

This runs in client systems today. The sample below was regenerated for a fictional company.

A system that only its author can install is a hobby. These are packages: contents, prerequisites, steps, and a version, with dependencies declared so an install order can be computed rather than remembered. The test is whether somebody installs it without asking you anything.

TRY IT / RUNS IN YOUR BROWSER

Use it here.

The mechanism is the production one. The company, the catalogue, and every figure are fictional.

How a team actually gets this

Install packages

Not a demonstration of the system, the thing you hand somebody so they can install it. Twelve packages of skills, agents, templates, guides, and checks, each with its prerequisites, its steps, and how long it takes. Pick what you want and the plan builder works out the order from the dependency graph, flags what is not in place yet, and refuses a selection that cannot be ordered at all.

Loading the package registry.

THE OUTPUT / GENERATED FOR APEX INSTRUMENTS

What comes out.

JSON
The package registry, twelve packagesData · Ten stable packages and two drafts. 110 contained items across five kinds, 61 install steps each with a way to check it worked, 595 minutes of work in total, 22 dependency edges, seven audiences, and eight environment prerequisites with what to do about each. Publishes the one dependency loop it contains rather than hiding it, plus the packaging rule that every package ships at least one skill, one template, and one check.Open the file ↗
MD
The full install guide for Workspace FoundationData · About 2,700 words for the largest package, written for somebody who has never done this and has nobody to ask. What has to be true before starting, the words the guide uses, twelve numbered steps each with a check and a reason, how you know it worked, the five things that usually go wrong with the symptom and the fix for each, what to install next, and how to back out.Open the file ↗
MJS
Registry builderData · Node ESM. Builds packages.json from one table and validates the graph while it does it: every dependency, prerequisite, audience, and content kind must resolve, and the count of cycles must be exactly the one planted on purpose. Run from rebuild/ with node systems/install-packages/build-data.mjs.Open the file ↗

THE MECHANISM / SHOW THE SHAPE, NOT THE SOURCE

How it works.

What a skill is
  1. 01Bundle

    A package names exactly what it contains.

  2. 02Declare

    Prerequisites and dependencies are data, not lore.

  3. 03Order

    An install order is computed from the graph, and a circular selection is refused with a reason.

  4. 04Guide

    One written guide per package, aimed at someone who has never done it.

  5. 05Check

    A checklist comes out of the plan, so the install can be verified rather than assumed.

WHAT IT READS

  • The skills, agents, templates and checks to ship
  • A prerequisite and dependency list per package
  • An audience and a time estimate

WHAT IT CHECKS BEFORE IT SHIPS

  • A missing prerequisite is caught before the install starts
  • The computed order satisfies every dependency
  • Each package states how long it takes
  • A guide assumes no prior knowledge
In production: plugin guides and organisation-wide skill install packages in one company system.

The mechanism runs inside client systems. Everything on this page was regenerated for Apex Instruments, a company that does not exist. Client names, source files, and internal wording stay private.

What it producesWhat is being built next