Project dashboard and lifecycle management. Shows project status, open work, and recommends next actions. Handles transitions between explore, build, open, and closed with automation wizards (CI/CD setup, test scaffolding, branch protection). Use when user says "status", "what's next", "where am I", "move to build", "go to open", or "/lo:status".
Project dashboard and lifecycle management. Two modes: dashboard (no args) shows where you are and what to do next; transition (with status name) moves the project through its lifecycle with automation wizards.
.lo/project.yml before making any changes.last_feature / last_task counters from BACKLOG.md frontmatter when adding backlog items. Never scan entries for the next ID..lo/ does not exist, stop and tell the user: "Run /lo:setup first."Detect from arguments:
/lo:status (no args) → Dashboard mode/lo:status build → Transition to build (complex wizard)/lo:status open → Transition to open (complex wizard)/lo:status exploreclosed/lo:status public or private → Visibility toggle (direct set)/lo:status state → Visibility toggle (prompted)Follow ONLY the section matching the detected mode.
When invoked with no arguments, show a project dashboard.
.lo/project.yml for title, status, state.lo/BACKLOG.md for open items.lo/work/ for active work directories.lo/park/ for parked capture filesCategorize each BACKLOG.md item:
[active] status line pointing to .lo/work/[parked] status line pointing to .lo/park/For active items, read plan files to determine progress (e.g., "phase 2 of 3").
Display:
Project: <title>
Status: <status> | State: <state>
Active:
f009 Image Generation — phase 2 of 3
Parked:
f010 Real-time Collab — .lo/park/f010-collab.md
Backlog:
t015 Fix button color
Suggested next:
Continue f009? → /lo:work f009
Pick up f010? → /lo:plan f010
Suggested-next: prioritize active items (suggest /lo:work), then parked (suggest /lo:plan), then backlog features (suggest /lo:plan) or tasks (suggest /lo:work).
If every section is empty:
Project: <title>
Status: <status> | State: <state>
Nothing in the backlog. Add ideas with /lo:park or start planning with /lo:plan.
The major transition — the project is becoming real.
.lo/project.yml, note current statusbuild, report and stopopen or closed, backward transition — require explicit confirmationstatus: "build" in project.ymlStatus changed: <old-status> → build
The project is now in build phase. This unlocks:
- Test coverage planning
- CI/CD pipeline setup
- Branch protection + auto-merge
- Public documentation
Ask two questions first: "Does this project use a database?" and "Does this project have an API server?" — answers control which optional steps appear.
Present the menu:
What do you want to configure?
1. All of the below (recommended)
2. Scan codebase and create a test coverage plan
3. Reconcile GitHub automation (CodeRabbit, CI, branch protection, auto-merge)
4. Create README and public docs (if missing)
5. Verify database backups and migrations ← only if database
6. Add health check endpoint ← only if API server
7. Skip all — just change the status
Items 5-6 are conditionally visible. Omit from the menu if the user said no. Adjust numbering accordingly.
Allow multiple selections. Run selected steps in order.
Scan the project for testable logic:
For each testable file/function, note: file path, what to test, priority (high/medium/low).
last_feature from .lo/BACKLOG.md frontmatter, increment by 1- [ ] f{NNN} Test Coverage
Retroactive test coverage for core project logic. Generated during explore → build transition.
[active](.lo/work/f{NNN}-test-coverage/)
last_feature counter in frontmatter.lo/work/f{NNN}-test-coverage/001-test-coverage.md:---