BytesFromToby
- 9 skills
- 0 followers
- 7 hours ago last updated
- ▌ Adopt · bytesfromtobyBootstrap Plumbline into an existing project — lay the Plumbline/ machinery and Planning/ skeleton non-destructively, detect and fill Stack/Commands from the real code, and record where the project's spec docs live so architect can ingest them. The brownfield counterpart to scaffold. Run once at onboarding.
- ▌ Builder · bytesfromtobyExecutes the blueprint — writes the code, checks off steps, logs deviations, and stops if the blueprint contradicts the spec. Run after foreman; one slice at a time when driven by hand, flowing slice-to-slice under an orchestrator. Also runs in fix mode against an inspector failure report.
- ▌ Foreman · bytesfromtobyReads the spec and produces the blueprint — a step-by-step execution plan for the builder, with a committed test planned for every automated Done-when item. Run after architect, before builder.
- ▌ Scaffold · bytesfromtoby bundleBootstrap a greenfield project — git init, the full convention folder skeleton, and a CLAUDE.md contract. Lays structure only and makes no design decisions; the stack and commands are left as pending fields for architect to fill. Run once at the start.
- ▌ Surveyor · bytesfromtobyStatic check of code against the spec — finds drift, unbuilt features, undocumented code, and automated Done-when items with no backing test. Reads and compares; never runs the software. Run before a feature, after a refactor, or when spec and code feel out of step.
- ▌ Architect · bytesfromtobyDefines a feature or project and writes the spec — by interviewing the user, or in autonomous mode by expanding a written brief and sorting every gap into a low-surprise assumption (non-blocking) or a genuine fork (an Open Question that halts). Also runs in adapt mode to ingest an existing project's docs and code into a Plumbline spec (brownfield onboarding via adopt). Run at the start of any new feature or project, or to update an existing spec. Also flags (does not perform) a restructure when the spec or a single feature grows too large.
- ▌ Homeowner · bytesfromtobyAutonomous build orchestrator — takes a written brief to verified code without a human gate, sequencing scaffold, architect, foreman, builder, and inspector. Halts and surfaces when a spec has Open Questions, a builder gets stuck, or an inspection fails. The build-mode counterpart to walkthrough (maintain mode).
- ▌ Inspector · bytesfromtoby bundleProves a slice or feature is done by running it. Reads the spec's Done when items, runs the tests that encode them (driving the software where no test exists), judges test fidelity, captures evidence, stamps the blueprint, and produces a signed report. Runs with fresh eyes — ideally a separate subagent. Run after builder — on [inspect]-flagged slices and for final sign-off.
- ▌ Walkthrough · bytesfromtobyAutonomous maintenance walkthrough — baseline, spec drift (via surveyor), coverage, docs, and a prioritized recommendations list. Applies safe (Quick-Path) fixes; routes anything bigger to recommendations for review. The maintain-mode counterpart to homeowner (build mode).