create-sdd-project 0.16.2 → 0.16.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -29,6 +29,14 @@ Before starting:
|
|
|
29
29
|
|
|
30
30
|
## `start pm` — New Autonomous Session
|
|
31
31
|
|
|
32
|
+
### Phase 0: Previous Session Cleanup
|
|
33
|
+
|
|
34
|
+
1. Check if `docs/project_notes/pm-session.md` exists.
|
|
35
|
+
2. If it exists and Status is `completed` or `stopped`:
|
|
36
|
+
- Archive it: rename to `docs/project_notes/pm-session-{session-id}.md` (e.g., `pm-session-pm-c3a.md`).
|
|
37
|
+
- Print: `[PM] Archived previous session {session-id} → pm-session-{session-id}.md`
|
|
38
|
+
3. If it exists and Status is `in-progress`: warn the user that a session is still active — suggest `continue pm` or `stop pm` first.
|
|
39
|
+
|
|
32
40
|
### Phase 1: Batch Selection
|
|
33
41
|
|
|
34
42
|
1. Read `docs/project_notes/product-tracker.md` → collect all features with step < 6/6.
|
|
@@ -151,7 +159,7 @@ Completed: 2/3 | Blocked: 1/3 | Remaining: 0
|
|
|
151
159
|
## `continue pm` — Resume After /compact or Restart
|
|
152
160
|
|
|
153
161
|
1. Read `docs/project_notes/pm-session.md`. If it doesn't exist, inform user there is no active session.
|
|
154
|
-
2. **Validate session Status.** If Status is `completed` or `stopped`, inform user the session has ended. To start a new one,
|
|
162
|
+
2. **Validate session Status.** If Status is `completed` or `stopped`, inform user the session has ended. To start a new one, run `start pm` (it will archive the old session automatically).
|
|
155
163
|
3. **Re-create lock.** If `docs/project_notes/pm-session.lock` is missing (e.g., after terminal crash), re-create it with content: `session resumed at {ISO date}`.
|
|
156
164
|
4. Find the feature with status `in-progress`:
|
|
157
165
|
- Read its ticket file and the product tracker Active Session to determine current step.
|
|
@@ -29,6 +29,14 @@ Before starting:
|
|
|
29
29
|
|
|
30
30
|
## `start pm` — New Autonomous Session
|
|
31
31
|
|
|
32
|
+
### Phase 0: Previous Session Cleanup
|
|
33
|
+
|
|
34
|
+
1. Check if `docs/project_notes/pm-session.md` exists.
|
|
35
|
+
2. If it exists and Status is `completed` or `stopped`:
|
|
36
|
+
- Archive it: rename to `docs/project_notes/pm-session-{session-id}.md` (e.g., `pm-session-pm-c3a.md`).
|
|
37
|
+
- Print: `[PM] Archived previous session {session-id} → pm-session-{session-id}.md`
|
|
38
|
+
3. If it exists and Status is `in-progress`: warn the user that a session is still active — suggest `continue pm` or `stop pm` first.
|
|
39
|
+
|
|
32
40
|
### Phase 1: Batch Selection
|
|
33
41
|
|
|
34
42
|
1. Read `docs/project_notes/product-tracker.md` → collect all features with step < 6/6.
|
|
@@ -151,7 +159,7 @@ Completed: 2/3 | Blocked: 1/3 | Remaining: 0
|
|
|
151
159
|
## `continue pm` — Resume After /compact or Restart
|
|
152
160
|
|
|
153
161
|
1. Read `docs/project_notes/pm-session.md`. If it doesn't exist, inform user there is no active session.
|
|
154
|
-
2. **Validate session Status.** If Status is `completed` or `stopped`, inform user the session has ended. To start a new one,
|
|
162
|
+
2. **Validate session Status.** If Status is `completed` or `stopped`, inform user the session has ended. To start a new one, run `start pm` (it will archive the old session automatically).
|
|
155
163
|
3. **Re-create lock.** If `docs/project_notes/pm-session.lock` is missing (e.g., after terminal crash), re-create it with content: `session resumed at {ISO date}`.
|
|
156
164
|
4. Find the feature with status `in-progress`:
|
|
157
165
|
- Read its ticket file and the product tracker Active Session to determine current step.
|