Work Units
Atomic units of work with YAML specs, worktree isolation, and lifecycle tracking. Learn more →
Software Delivery Pack
The Software Delivery Pack is the default domain pack shipped with LumenFlow. It provides everything you need for structured software delivery — from work unit lifecycle to quality gates to agent coordination.
It is also the package that provides initiatives, delivery-flow metrics,
and workflow memory. Use the initiatives, metrics, and memory exports from
@hellmai/lumenflow-packs-software-delivery; the similarly named standalone packages
are deprecated compatibility forwarders pending final v6 removal.
What the Pack Provides
Section titled “What the Pack Provides”Lanes
Scoped work streams with optional WIP limits, lock policies, and path-based access control. Learn more →
Gates
Config-driven quality checks (format, lint, typecheck, test) enforced as kernel policies. Learn more →
Memory Layer
Session tracking, checkpoints, coordination signals, and context recovery for agents. Learn more →
CLI Commands
Section titled “CLI Commands”The pack registers CLI commands grouped into categories. Run pnpm lumenflow:commands
for the full, current list and counts, since they change as commands are added.
| Category | Examples |
|---|---|
| WU Lifecycle | wu:create, wu:claim, wu:prep, wu:done |
| Memory & Sessions | mem:checkpoint, mem:inbox, mem:signal |
| Initiatives | initiative:create, initiative:status |
| Gates & Quality | gates, lane:validate |
| Packs | pack:author, pack:install, pack:validate |
| Metrics & Flow | flow:report, flow:bottlenecks, metrics |
| Orchestration | orchestrate:initiative, orchestrate:monitor, agent:session |
See the CLI Reference for the complete command list.
Secure Template Authoring (No-Code)
Section titled “Secure Template Authoring (No-Code)”The recommended path for new packs is template-first authoring:
Template generation enforces least-privilege defaults and validation catches unsafe scope/network configurations before install or publish.
Install command shape:
Pack Policies
Section titled “Pack Policies”The Software Delivery Pack ships with policies that the kernel evaluates automatically:
- Gate policies — Format, lint, typecheck, and test gates run
on_completionwith deny-wins semantics - Scope policies — Lane-based path restrictions enforced on every tool call
- Constraint policies — Non-negotiable rules like “no edits outside worktrees” and “no force-push”
See the Policy Engine for how these are evaluated.
Why the Software Delivery Pack?
Section titled “Why the Software Delivery Pack?”If you are a software team using AI agents, the Software Delivery Pack replaces ad-hoc methodologies with a structured, evidence-based workflow. Here is how it compares to traditional approaches:
Work Units, Not Stories
Section titled “Work Units, Not Stories”Traditional tickets are vague — “Add user authentication.” Work Units are executable specifications with acceptance criteria, code paths, and test paths. An AI agent can read a WU spec and implement it autonomously. A human can verify completion by checking the criteria.
Lanes, Not Sprints
Section titled “Lanes, Not Sprints”Scrum batches work into time-boxed sprints. The Software Delivery Pack flows work through parallel lanes — each unlimited by default, with an optional wip_limit where you want to cap concurrency. Work flows continuously instead of waiting for sprint boundaries.
Gates and Independent Review
Section titled “Gates and Independent Review”Automated gates run configured checks such as format, lint, typecheck, and tests before completion. They provide repeatable evidence, but do not establish that code is semantically correct. The optional delivery_review gate checks changed paths and delivery evidence; it is disabled by default and does not perform source-level code analysis. A WU can separately require an independent reviewer, whose candidate-bound verdict is evaluated by the lifecycle. Escalation approvals are another configured authority, not a substitute for either check.
Memory, Not Standups
Section titled “Memory, Not Standups”Daily standups exist because humans forget context. The Software Delivery Pack’s memory layer provides checkpointing and context recovery, so both humans and AI agents can resume exactly where they left off.
Stamps, Not Done Columns
Section titled “Stamps, Not Done Columns”Kanban boards have “Done” columns. The Software Delivery Pack creates completion stamps after configured gates and any enforced reviewer or escalation checks pass and the local WU is merged. The stamp records lifecycle completion; it is not proof of semantic correctness for every acceptance criterion.
Comparison Table
Section titled “Comparison Table”| Aspect | Scrum | Kanban | Shape Up | Software Delivery Pack |
|---|---|---|---|---|
| Time unit | 2-week sprints | Continuous | 6-week cycles | Continuous |
| Work item | User story | Card | Pitch | Work Unit (WU) |
| Progress | Story points | Cycle time | Hill charts | Gates + stamps |
| Parallelism | Team velocity | WIP limits | Team per pitch | Lane-based WIP |
| Reviews | Sprint review + PR | PR review | Demo | Gates + optional independent review |
| AI-ready | No | Partially | No | Yes |
| Context | Human memory | Board state | Write-up | Memory layer |
Next Steps
Section titled “Next Steps”- Concepts — Work Units, Lanes, Gates, Memory
- Workflows — A Day with LumenFlow, Solo, Team
- Advanced — Initiatives, Flow Metrics, Custom Skills
- Running multi-WU initiatives — Orchestration (lifecycle, state machine, artifact bundle, capacity + integrity, SDK)
- Build your own — Create a Pack