create-sdd-project 0.9.7 → 0.9.8
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/lib/config.js
CHANGED
package/package.json
CHANGED
|
@@ -0,0 +1,44 @@
|
|
|
1
|
+
Generate a complete context recovery prompt to paste after /compact or at the start of a new session.
|
|
2
|
+
|
|
3
|
+
## What to include
|
|
4
|
+
|
|
5
|
+
The prompt must contain EVERYTHING needed for a new session (or post-compact) to continue work without information loss:
|
|
6
|
+
|
|
7
|
+
1. **Project state**: current branch, last commit, working tree status, SDD version
|
|
8
|
+
2. **Workflow**: SDD development workflow, autonomy level, branching strategy
|
|
9
|
+
3. **Active feature**: current step in the 6-step workflow, what has been done, what remains
|
|
10
|
+
4. **Epics and progress**: table with status of each epic
|
|
11
|
+
5. **Backlog**: pending features with priorities and dependencies
|
|
12
|
+
6. **Infrastructure**: key modules, endpoints, schemas, with exact file paths
|
|
13
|
+
7. **Tests**: total count, files, lint/build/tsc status
|
|
14
|
+
8. **Key files to read**: list of files the new session must read first
|
|
15
|
+
9. **Next action**: the specific next thing to do, with context
|
|
16
|
+
10. **User notes**: any decisions or constraints communicated by the user
|
|
17
|
+
|
|
18
|
+
### Workflow Recovery (CRITICAL)
|
|
19
|
+
|
|
20
|
+
This section prevents the agent from losing track of the development process after /compact:
|
|
21
|
+
|
|
22
|
+
11. **Current workflow step**: Which of the 6 steps (Spec, Setup, Plan, Implement, Finalize, Review) is active
|
|
23
|
+
12. **Pending checkpoints**: Which approvals remain (Spec, Ticket, Plan, Commit, Merge)
|
|
24
|
+
13. **Merge checklist reminder**: If at Step 5 or later, explicitly state: "Before requesting merge approval, you MUST read `references/merge-checklist.md` and execute ALL actions (0-8). Fill the `## Merge Checklist Evidence` table in the ticket with real evidence for each action."
|
|
25
|
+
14. **Step order reminder**: "After commit+PR, run code-review-specialist and qa-engineer (Step 5), then execute merge-checklist actions. Do NOT request merge approval without completing the checklist."
|
|
26
|
+
|
|
27
|
+
## How to generate
|
|
28
|
+
|
|
29
|
+
- Read `docs/project_notes/product-tracker.md` (Active Session + Features tables + Completion Log)
|
|
30
|
+
- Read `docs/project_notes/decisions.md` (recent ADRs)
|
|
31
|
+
- Read `docs/project_notes/key_facts.md` (stack, components)
|
|
32
|
+
- Read the current ticket in `docs/tickets/` if a feature is active
|
|
33
|
+
- Run `git log --oneline -5` and `git status` for current state
|
|
34
|
+
- Read `.sdd-version` for SDD DevFlow version
|
|
35
|
+
|
|
36
|
+
## Output format
|
|
37
|
+
|
|
38
|
+
Structured markdown with tables, ready to paste directly as the first message of a new session. The prompt should be self-contained — the receiving agent should not need to ask clarifying questions.
|
|
39
|
+
|
|
40
|
+
## Context
|
|
41
|
+
|
|
42
|
+
- Users work remotely with long sessions — interruptions are costly
|
|
43
|
+
- After /review-plan + plan approval, context is typically at 50%+ usage, making /compact necessary before implementation
|
|
44
|
+
- The workflow recovery section is essential: without it, the agent may skip merge checklist actions after /compact
|
|
@@ -0,0 +1,46 @@
|
|
|
1
|
+
## Context Prompt — Instructions
|
|
2
|
+
|
|
3
|
+
Generate a complete context recovery prompt to paste after compaction or at the start of a new session.
|
|
4
|
+
|
|
5
|
+
### What to include
|
|
6
|
+
|
|
7
|
+
The prompt must contain EVERYTHING needed for a new session (or post-compact) to continue work without information loss:
|
|
8
|
+
|
|
9
|
+
1. **Project state**: current branch, last commit, working tree status, SDD version
|
|
10
|
+
2. **Workflow**: SDD development workflow, autonomy level, branching strategy
|
|
11
|
+
3. **Active feature**: current step in the 6-step workflow, what has been done, what remains
|
|
12
|
+
4. **Epics and progress**: table with status of each epic
|
|
13
|
+
5. **Backlog**: pending features with priorities and dependencies
|
|
14
|
+
6. **Infrastructure**: key modules, endpoints, schemas, with exact file paths
|
|
15
|
+
7. **Tests**: total count, files, lint/build/tsc status
|
|
16
|
+
8. **Key files to read**: list of files the new session must read first
|
|
17
|
+
9. **Next action**: the specific next thing to do, with context
|
|
18
|
+
10. **User notes**: any decisions or constraints communicated by the user
|
|
19
|
+
|
|
20
|
+
#### Workflow Recovery (CRITICAL)
|
|
21
|
+
|
|
22
|
+
This section prevents the agent from losing track of the development process after compaction:
|
|
23
|
+
|
|
24
|
+
11. **Current workflow step**: Which of the 6 steps (Spec, Setup, Plan, Implement, Finalize, Review) is active
|
|
25
|
+
12. **Pending checkpoints**: Which approvals remain (Spec, Ticket, Plan, Commit, Merge)
|
|
26
|
+
13. **Merge checklist reminder**: If at Step 5 or later, explicitly state: "Before requesting merge approval, you MUST read `references/merge-checklist.md` and execute ALL actions (0-8). Fill the `## Merge Checklist Evidence` table in the ticket with real evidence for each action."
|
|
27
|
+
14. **Step order reminder**: "After commit+PR, run code-review-specialist and qa-engineer (Step 5), then execute merge-checklist actions. Do NOT request merge approval without completing the checklist."
|
|
28
|
+
|
|
29
|
+
### How to generate
|
|
30
|
+
|
|
31
|
+
- Read `docs/project_notes/product-tracker.md` (Active Session + Features tables + Completion Log)
|
|
32
|
+
- Read `docs/project_notes/decisions.md` (recent ADRs)
|
|
33
|
+
- Read `docs/project_notes/key_facts.md` (stack, components)
|
|
34
|
+
- Read the current ticket in `docs/tickets/` if a feature is active
|
|
35
|
+
- Run `git log --oneline -5` and `git status` for current state
|
|
36
|
+
- Read `.sdd-version` for SDD DevFlow version
|
|
37
|
+
|
|
38
|
+
### Output format
|
|
39
|
+
|
|
40
|
+
Structured markdown with tables, ready to paste directly as the first message of a new session. The prompt should be self-contained — the receiving agent should not need to ask clarifying questions.
|
|
41
|
+
|
|
42
|
+
### Context
|
|
43
|
+
|
|
44
|
+
- Users work remotely with long sessions — interruptions are costly
|
|
45
|
+
- After plan review + plan approval, context is typically at 50%+ usage, making compaction necessary before implementation
|
|
46
|
+
- The workflow recovery section is essential: without it, the agent may skip merge checklist actions after compaction
|