| name | graftline-runner |
| description | Execute the full Graftline pipeline on a Rootstock plan file. Phase Zero → Scaffold → Build → Classify → Validate → Document → Evaluate → Autograft.
|
| version | 0.1.0 |
| author | Jero (LATTICE / MARPA Design Studios) |
| triggers | ["run the graftline","graft this plan","build from rootstock","/graft"] |
| tools | ["Bash","Read","Write","Edit","Glob","Grep"] |
Graftline Runner
USE WHEN the user wants to execute the Graftline pipeline on a Rootstock, build a Graft from a plan file, or run the factory end-to-end.
What It Does
Orchestrates the full Graftline — GRAFTKIT's build pipeline:
- Phase Zero — Gap analysis: review Rootstock, research referenced repos, rewrite plan if gaps found
- Scaffold — Clone repos, create directory structure, verify dependencies
- Build — LLM-powered code generation from the Rootstock spec
- Classify — Pydantic + Instructor entity extraction (functions, classes, APIs, models)
- Validate — AST checks, file size, CLI smoke test, PEP 723 compliance
- Document — RenderGit HTML+CXML generation, SKILL.md creation
- Evaluate — Check output against GOALS.md, run improvement loop if needed
- Autograft — Drop artifacts to target, register in Engraft (library.yaml), push to GitHub
Usage
/graft frontend.plan.md
/graft tool.plan.md
Inputs
- Rootstock — A
*.plan.md file with YAML frontmatter defining the build spec
- Engraft —
library.yaml providing reference pointers for uses: directives
Outputs
- Graft — The built application or tool
- Documentation — HTML + CXML session records
- Engraft entry — New registration in library.yaml
Error Handling
- If Phase Zero finds critical gaps, halt and report before proceeding
- If Validate fails, loop back to Build with specific fix instructions (max 3 iterations)
- If Evaluate scores below threshold, report but still produce the Graft