lulu-workflow

Routes project-level work into a stage skill. Done when init has reported, or the matching sub-SKILL is loaded.

Runtime modules (loaded by sub-skills, not this file):

• _runtime.md — Script Macros + Platform / Session / Execution Mode (all sub-skills)
• _slowpath.md — Feature Resolution Slow Path (loaded on demand)
• _transitions.md — Stage Transitions + Rollback (loaded at delivery)
• _subagent.md — Sub-agent Context (lulu-exec, lulu-tasks, decision)

Stage lines

$CYCLE_TYPE is topic or feature, and each has its own stage dependencies in config/transition-table.json, under the topic and feature keys.

Read the key for the current $CYCLE_TYPE: each entry maps a from stage to the to stages it allows, and a null from lists the stages a cycle can start at.

Routing

Load one sub-SKILL after $CYCLE_ID is confirmed.

1. The sub-SKILL owns drafting, evaluation, and delivery.

Bootstrap

First use in a repo. Read _runtime.md § Script Macros and § Platform Context before the command.

1. When — the repo has no platform hooks, or this is the first run.
2. Run — $CYCLE_CONTROL init-project
3. Done — report success or stderr. Re-run is safe.
4. Next — enter a sub-SKILL. Cycle binding is _runtime.md § Session Foundation.

Script Macros

$CYCLE_CONTROL is defined in _runtime.md § Script Macros. This file invokes init-project only.

1. start, menu, and resolve-token run from _slowpath.md.
2. bind-context runs from _runtime.md § Session Foundation after $CYCLE_ID is confirmed.
3. Subcommands and stdout: cycle_control.py module docstring or --help.
4. Non-zero exit → stop and report stderr.
5. Call $CYCLE_CONTROL only. A bare python3 path or cycle_schema.py is outside this file.