docs: explain lifecycle session handoffs (#513)

This commit is contained in:
DEOWL-kan committed 2026-09-05 11:13:50 +08:00
1 parent 1c760d6434
commit 878d5d4789
2 files changed
+18 -1

No files matched your search

+1 -1
View File
@@ -43,7 +43,7 @@ Run the lifecycle in order for the project's first real feature:
/ship → when going live (shipping-and-launch)
```
`/build auto` is a good fit for greenfield: you approve the plan once and every task still runs test-driven and commits individually. The spec and plan artifacts (`SPEC.md`, `tasks/`) are living documents, keep them in version control while the work is in flight.
`/build auto` is a good fit for greenfield: you approve the plan once and every task still runs test-driven and commits individually. The spec and plan artifacts (`SPEC.md`, `tasks/`) are living documents, keep them in version control while the work is in flight. If the feature spans more than one session, those files are also the handoff, see [working across sessions](getting-started.md#working-across-sessions).
### From the start, treat these as always-on