create-sdd-project 0.16.1 → 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.
|
|
@@ -222,3 +230,9 @@ Completed: 2/3 | Blocked: 1/3 | Remaining: 0
|
|
|
222
230
|
- **Do NOT force-resolve merge conflicts.** Mark as blocked and skip.
|
|
223
231
|
- **Do NOT modify pm-session.md format.** Follow the template structure exactly.
|
|
224
232
|
- **Do NOT continue after post-merge sanity failure.** Stop and report.
|
|
233
|
+
- **Do NOT make architectural decisions without checking first.** Before choosing a new approach, library, or pattern:
|
|
234
|
+
1. Search the existing codebase for similar solutions (other packages, shared modules, existing endpoints).
|
|
235
|
+
2. Check `docs/project_notes/decisions.md` and `docs/project_notes/key_facts.md` for prior decisions.
|
|
236
|
+
3. If the project uses multiple packages/modules, check how they solved the same problem.
|
|
237
|
+
4. If still uncertain, ask the user or consult external AI models (Gemini CLI, Codex CLI) before proceeding.
|
|
238
|
+
5. If the chosen approach creates a dependency on something that doesn't exist yet (e.g., a backend endpoint), create a follow-up task in `product-tracker.md` to track it.
|
|
@@ -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.
|
|
@@ -222,3 +230,9 @@ Completed: 2/3 | Blocked: 1/3 | Remaining: 0
|
|
|
222
230
|
- **Do NOT force-resolve merge conflicts.** Mark as blocked and skip.
|
|
223
231
|
- **Do NOT modify pm-session.md format.** Follow the template structure exactly.
|
|
224
232
|
- **Do NOT continue after post-merge sanity failure.** Stop and report.
|
|
233
|
+
- **Do NOT make architectural decisions without checking first.** Before choosing a new approach, library, or pattern:
|
|
234
|
+
1. Search the existing codebase for similar solutions (other packages, shared modules, existing endpoints).
|
|
235
|
+
2. Check `docs/project_notes/decisions.md` and `docs/project_notes/key_facts.md` for prior decisions.
|
|
236
|
+
3. If the project uses multiple packages/modules, check how they solved the same problem.
|
|
237
|
+
4. Check with external AI models (Gemini CLI, Codex CLI) if uncertain.
|
|
238
|
+
5. If the chosen approach creates a dependency on something that doesn't exist yet (e.g., a backend endpoint), create a follow-up task in `product-tracker.md` to track it.
|