@mr.dj2u/knowledge 0.1.2 → 0.1.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.
|
@@ -28,4 +28,5 @@ Create a new Expo app with the MDS Super Stack flow, using the published CESS CL
|
|
|
28
28
|
## Verification And Output
|
|
29
29
|
|
|
30
30
|
- Confirm generated app has `project/info.md`, `project/todo.md`, `project/style.md`, and `project/guidelines.md`.
|
|
31
|
+
- Confirm `project/todo.md` includes the auto-derived roadmap generated from normalized `project/info.md`.
|
|
31
32
|
- Output: generated app path, onboarding status, and the handoff to open a fresh agent session inside the new app folder and run `mds continue`.
|
|
@@ -17,10 +17,10 @@ Run generator + onboarding as one guided flow, keep agent-facing wording sourced
|
|
|
17
17
|
|
|
18
18
|
## Preferred structure
|
|
19
19
|
|
|
20
|
-
- Keep startup conversation in plain language and summarize choices before execution.
|
|
21
|
-
- Keep generation details in scripts/flags, but keep user-facing flow conversational.
|
|
22
|
-
- Keep post-generation workflow phase-based using the generated `project/todo.md
|
|
23
|
-
- Prefer shared knowledge content over duplicating long onboarding prose in plugin or MCP wrappers.
|
|
20
|
+
- Keep startup conversation in plain language and summarize choices before execution.
|
|
21
|
+
- Keep generation details in scripts/flags, but keep user-facing flow conversational.
|
|
22
|
+
- Keep post-generation workflow phase-based using the generated `project/todo.md`, and derive that roadmap from normalized `project/info.md` before handoff.
|
|
23
|
+
- Prefer shared knowledge content over duplicating long onboarding prose in plugin or MCP wrappers.
|
|
24
24
|
|
|
25
25
|
## Example fix
|
|
26
26
|
|