Framework
When the default sprint is not your process
The default sprint, think, plan, build, review, security, QA, ship, fits most product work. But your team's definition of done probably has clauses ours does not: a license check, a privacy review, a release sign-off. The question is whether your process gets the same machinery as the built-in one.
Custom phases are not scripts taped to the side
The usual fate of team-specific process in AI workflows is a paragraph in a prompt file: "always check licenses before release". Advice again, and advice degrades. In Nanostack a custom phase is a first-class citizen: a skill folder with a SKILL.md, registered in .nanostack/config.json, wired into the order with phase_graph.
First-class means it inherits everything the built-in phases get without extra work: it saves a structured artifact with integrity, downstream phases can read it, the conductor schedules it, read-only phases stay write-blocked while it runs, and gates can require its evidence before release.
A real one: the compliance-release stack
The repo ships a working example with three custom phases wired in front of ship:
- /license-audit walks third-party dependencies against an allowlist and records the verdict.
- /privacy-check reviews what personal data the change touches and where it flows.
- /release-readiness reads both upstream artifacts and produces a single release decision, with the rationale written down.
The interesting part is the third phase: it does not re-do the work, it composes the evidence. That is your release meeting, turned into a phase that cannot be skipped and leaves a record.
Declared, validated, scheduled
Building one is deliberately boring. bin/create-skill.sh scaffolds the folder. bin/check-custom-skill.sh validates it against the framework contract before it can run. The graph declaration says what depends on what, and the same scheduler that orders the default sprint orders yours, including running independent phases in parallel.
None of this requires forking Nanostack or asking us. The framework layer is the product as much as the default sprint is: the default shows what the machinery can hold, and the machinery is yours to point at your own process.
The framework guide → · Open the compliance-release example →